Bug 768503

Jun 23 00:35:19 karl umount[5081]: umount: /var/lib/nfs/rpc_pipefs: device is busy.
Jun 23 00:35:19 karl umount[5081]: (In some cases useful info about processes that use
Jun 23 00:35:19 karl umount[5081]: the device is found by lsof(8) or fuser(1))
Jun 23 00:35:19 karl umount[5082]: umount: /home: device is busy.
Jun 23 00:35:19 karl umount[5082]: (In some cases useful info about processes that use
Jun 23 00:35:19 karl umount[5082]: the device is found by lsof(8) or fuser(1))

Thus, the (encrypted) /home partition is not unmounted. Since this may corrupt data, I raise the Importance to critical.

Sorry, these are the missing lines until the next boot:
Jun 23 00:35:20 karl kernel: Kernel logging (proc) stopped.
Jun 23 00:35:20 karl rsyslogd: [origin software="rsyslogd" swVersion="5.8.5" x-pid="1057" x-info="http://www.rsyslog.com"] exiting on signal 15.

Same issue here.
My system is a dual 6128 Opteron AMD with openSuSE 12.1 x86_64.
After updating kernel to the new version, it stop to properly power off.
I don't have strange messages in the system log.
The messages at shutdown, after and before the update, are pretty the same.

same problem after updating the kernel.
The system will not shut properly.
For you must shut it down correctly, as root on the console, giving init 0

Hi, Riccardo.
I've tryed to give init 0 as root.
I logged out from my graphical session and I've terminated it with rcxdm stop, then I give init 0 from console, but my system continue to not power off properly.
Neither the Magic SysRQ keys works.
However, the shutdown process is executed correctly and I can hear my HDDs go off, but the system remain on and I have to power it off manually, pressing the power button for at least 5 seconds.

There seems to be three different problems here.

The original report seems to be about the pre-halt conditions not being met WRT file systems being mounted.

Comment #4 seems to refer to a problem with GUI shutdown.
Comment #5 seems to be an ACPI issue.


Please file separate issues for those. This report will focus on the report described in the summary.

If I had to guess, it sounds as if something isn't shutting down properly and systemd is refusing to continue.

@Jeff: Honestly, Comment #5 might be the same issue: everything seems to go fine but the actual "power off" does not work. Even the power on led of my T410s turns off. But at least, neither the back light nor the fan turn off. Sorry, if I was not clear enough in my initial report!
Furthermore, the messages about busy "/home" might(!) be a red herring, since the system does not seem to complain about dirty file systems on the next boot. However, I do not know whether the detection is that reliable.

BTW, after the kernel update, I do suffer from Bug #764864 (s2ram is broken), too.

After today's updates the system seems to close regular

Same bug. Machine:

OS: openSUSE 12.1
CPU: AMD Phenom(tm) II X4 955 Processor
Motherboard: ASUS M4A785TD-V EVO
RAM: 4GB (minus some MB for motherboard graphic)

Problem appeared with kernel "3.1.10-1.13-desktop". Disappeared after returning to 3.1.10-1.9-desktop.

Strange:
Error disappeared immediately on the shutdown after returning to kernel "3.1.10-1.9-desktop" using commandline YaST (system was bootet to runlevel 2 - no Xorg - no network services). So the new kernel wasn't already loaded at that time.
Maybe the problem only appears when using Xorg or some OpenGL-Graphic before???



Sorry, until mid of July no more time for debugging.

I'm not maintainer of systemd nor of the kernel

The subject says it all

For me, the new kernel that fixed Bug #764864 fixed this one, too.