https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c1 Jan Ritzerfeld changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical --- Comment #1 from Jan Ritzerfeld 2012-06-23 11:16:49 UTC --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c3 Alessandro Sturniolo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alessandro.sturniolo@gmail. | |com --- Comment #3 from Alessandro Sturniolo 2012-06-24 08:49:03 UTC --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c5 --- Comment #5 from Alessandro Sturniolo 2012-06-24 09:59:53 UTC --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c7 --- Comment #7 from Jan Ritzerfeld 2012-06-25 18:50:11 UTC --- @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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c9 Moritz Duge changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colAflash@gmx.net --- Comment #9 from Moritz Duge 2012-06-26 09:38:00 UTC --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #10 from Dr. Werner Fink 2012-07-02 06:37:42 UTC --- I'm not maintainer of systemd nor of the kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=768503 https://bugzilla.novell.com/show_bug.cgi?id=768503#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel AssignedTo|fcrozat@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #11 from Dr. Werner Fink 2012-07-05 06:35:10 UTC --- The subject says it all -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.