[systemd-bugs] [Bug 63134] New: shutdown/reboot hangs on new arch install

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=63134

          Priority: medium
            Bug ID: 63134
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: shutdown/reboot hangs on new arch install
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: client.alive at gmx.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 77444
  --> https://bugs.freedesktop.org/attachment.cgi?id=77444&action=edit
What is printed to screen when the shutdown process hangs AND lines from
journalctl that caught my eye

First of all, I appologize if I go off track or if this isn't the right place
to come. This is my first time doing one of these.

Some system information:

It is a uefi install using the kernels boot stub loader with an efibootmgr
entry
root is in a logical volume on raid 5

The modules line in /etc/mkinitcpio.conf is:

MODULES="efivars dm_mod raid456 ext4"

The hooks line in /etc/mkinitcpio.conf is:

HOOKS="base udev autodetect modconf block filesystems keyboard fsck mdadm_udev
lvm2 timestamp shutdown"

Symptoms:

When attempting to reboot or shutdown the system it hangs during the shutdown
process and will not shut down.

Testing:

In 5 tries with systemctl reboot: failed on the 4th run (all other runs
successful)
In 5 tries with systemctl shutdown: failed on the 4th and 5th runs

Last night I did...

[code]
boot with the debug options: 

systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0

    save the following script as /lib/systemd/system-shutdown/debug.sh and make
it executable: 

#!/bin/sh
mount -o remount,rw /
dmesg > /shutdown-log.txt
mount -o remount,ro /

    reboot 

reference:
http://freedesktop.org/wiki/Software/systemd/Debugging#Shutdown_Completes_Eventually
[/code]

 ...then went to bed. When I awoke the sytem was still hung up in the shutdown
process. (That there be no shadow of a doubt it will not eventually complete).

After resetting the machine using the button on the front of the box I
discoverd there was no shutdown-log.txt file on the sytem (the script was made
executable).

Reproduce:

On a command line, type one of the folowing then press < enter > :

reboot
shutdown
shutdown -h now
shutdown -r now
poweroff

What does work:

halt (iirc)
sync && poweroff -f

Comment:

Attached are some data that may (or may not) be helpful. Again, this is my
first time here. Please let me know if any other iformation is required.

The bottom line for me is I don't know what to test for or what command(s) to
run to make that happen. I can only imagine that I should want to know what
that next line is that would have been printed to the sceen when shutdown
hangs, but how to get that data I don't know. Is there someone who can supply
the command(s) to run to determine the problem's source? I'm unable to use my
system properly and I need help. I have a thread on the arch forum and I ask on
their irc chanel but I'm not getting the help I need and days are beginning to
pass.

Thanks
Jake

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130404/80ffc820/attachment.html>