FS#30763 - System can't shutdown

Attached to Project: Arch Linux
Opened by Marcin (s4ncho) - Thursday, 19 July 2012, 19:51 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 25 July 2012, 06:57 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
after last update ("The /lib directory becomes a symlink") system can't shutdown (via "sudo halt" or "sudo poweroff").
It does nothing after "deactivating encrypted volumes [done]" and just keep... waiting(?).
it doesn't freeze, because I can for example swith from plymouth to console via Ctrl+f1.

I've tried to reboot using Ctrl+alt+del then it showed message like "rebooting system" (can't remenber the msg) but nothing happend. after hard reboot (via restart button on pc) arch got wrong time (and date).

After step "deactivating encrypted volumes [done]" nothing happends I've been waiting about 10minuts and it still hasn't go off. It happens all the time afert "/lib symlink" upgrade.


Additional info:
* package version(s)
* config and/or log files etc.
[quote]$ lscpu
Architektura: i686
Tryb(y) pracy CPU: 32-bit, 64-bit
Kolejność bajtów: Little Endian
CPU: 1
Lista aktywnych CPU: 0
Wątków na rdzeń: 1
Rdzeni na gniazdo: 1
Gniazd: 1
ID producenta: GenuineIntel
Rodzina CPU: 6
Model: 22
Wersja: 1
CPU MHz: 1600.079
BogoMIPS: 3201.49
Cache L1d: 32K
Cache L1i: 32K
Cache L2: 512K
[/quote]

Steps to reproduce:
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 25 July 2012, 06:57 GMT
Reason for closing:  Not a bug
Comment by Jasper den Ouden (Jasper1984) - Friday, 20 July 2012, 18:44 GMT
I cant restart either, after a recent update. It *seems* to be due to a `mount` with a low PID not shutting down(and using a core 100%) (`kill` doesn't work on it.) [Havent really been able to figure out why..](http://www.reddit.com/r/linuxquestions/comments/wvbvq/archlinuxmount_wont_stop_running/) Anyway that might not be your problem, but do `top |grep mount` or something to check? Edit: _if_ it is that, the solution might be an udev rule gone awry (see link)
Comment by Tom Gundersen (tomegun) - Friday, 20 July 2012, 22:38 GMT
Just checking: do you have /usr on a separate partition?
Comment by Dave Reisner (falconindy) - Friday, 20 July 2012, 22:40 GMT
Please try to reproduce this with maxcpus=1 on your kernel cmdline.
Comment by Jan (next-play) - Sunday, 22 July 2012, 10:00 GMT
I've the same problem since I updated my system
Comment by Marcin (s4ncho) - Sunday, 22 July 2012, 20:22 GMT
@Jasper1984 strage but I can't see "mount" in top, "$top |grep mount" gives no output neither "$ps -A |grep mount".
can you tell me what rule I should add to udev?

@tomegun I've /usr on the same partition as rest of the system
"$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1292044k,nr_inodes=218084,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/sda6 on /media/Pliki type ext4 (rw,relatime,data=ordered)
binfmt on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
gvfs-fuse-daemon on /media/Pliki/.home/marcin/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=500)"

only /home is a symlink to /media/Pliki/.home and /opt -> /media/Pliki/.opt (They're both on /dev/sda6)
and nowadays /lib is a symlink to /usr/lib. there aren't other links on root ("/") filesystem directory.

@falconindy I've added " maxcpus=1 " at the end of command line for "linux" entry in grub2, and started the system.
But there were no changes while testing the rebooting. I havn't tried to do "halt" or "poweroff" but I guest it'll be the same.
Comment by David (thegritche) - Tuesday, 24 July 2012, 08:09 GMT
I had the same problem. Then I realised that (silly me!) I had systemd packages installed but I forgot to put the kernel commandline argument after migrating to grub2.
After adding the "init=/bin/systemd" argument, my laptop's shutdown completes.
Maybe there is another bug there (I'm not sure) : systemd packages installed but no systemd services running => shutdown hangs.
Comment by Marcin (s4ncho) - Tuesday, 24 July 2012, 19:21 GMT
@thegritche Thank you:)

Adding "init=/bin/systemd" to linux options (in grub) solved my problem:)

Loading...