[Bug 810456] New: shutdown does not work
https://bugzilla.novell.com/show_bug.cgi?id=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c0 Summary: shutdown does not work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat@suse.com ReportedBy: wolfgang@rosenauer.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- On my Thinkpad X200s shutdown does not work anymore after updating to 12.3. I've already performed some debugging as explained here http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_P... - reboot -f and poweroff -f works w/o issues - shutdown never finishes - usually I still get the "System powered off" (or similar; do not remember the exact wording) message on the console but there it stays - tried to enable the debug shell to check what's going on but couldn't enter the tty9 after shutdown was almost complete. The splash screen didn't go away and I couldn't switch ttys at all At that point I'm pretty much lost what to debug. -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c1 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |wolfgang@rosenauer.org --- Comment #1 from Frederic Crozat <fcrozat@suse.com> 2013-03-20 09:38:39 UTC --- try booting with "plymouth.enable=0" to ensure splash never start, it will help you to debug this. Try to get the trace according to http://freedesktop.org/wiki/Software/systemd/Debugging#Shutdown_Completes_Ev... : after some time, just power off the system and see if you have a trace and attach it here. -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c2 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|wolfgang@rosenauer.org | --- Comment #2 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2013-03-20 21:59:27 UTC --- Meanwhile I found that it's absolutely erratic behaviour. Sometimes it shuts down (even if it takes quite some time) sometimes it doesn't just hanging at "Powered off". When it _seems_ like it's doing nothing I see with list-jobs that it's running with acpid and block device stuff. Last time it was hanging after the "Powered off" line where I couldn't get to tty9 anymore and also there was no /shutdown-log.txt written. Anything else I could try? -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c3 --- Comment #3 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2013-05-29 20:33:38 UTC --- Meanwhile with all updates applied. Shutdown seems to work all the time but it takes 9 out of 10 cases ages to shut down. Several minutes that is and every time I checked it was a timeout when closing down my crypto home partition. -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c4 --- Comment #4 from Frederic Crozat <fcrozat@suse.com> 2013-05-30 11:30:07 UTC --- Hmm, if you have journal on disk enabled, it could be useful to get journalctl output for the crypto home partition, after such failure.. -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c5 --- Comment #5 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2013-05-30 17:49:43 UTC --- May 29 16:32:32 ox.rosenauer.org systemd-logind[573]: System is powering down. [...] May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-mapper-cr_sda7.device/stop timed out. May 29 16:34:02 ox.rosenauer.org systemd[1]: Timed out stoppping /dev/mapper/cr_sda7. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-mapper-cr_sda7.device/stop failed with result 'timeout'. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2duuid-ffce8c04\x2d9298\x2d460b\x2d969f\x2dd41df37688ef.device/stop timed out. May 29 16:34:02 ox.rosenauer.org systemd[1]: Timed out stoppping /dev/disk/by-uuid/ffce8c04-9298-460b-969f-d41df37688ef. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2duuid-ffce8c04\x2d9298\x2d460b\x2d969f\x2dd41df37688ef.device/stop failed with result 'timeout'. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dLUKS1\x2d13058ed64bd143069946108705751b17\x2dcr_sda7.device/stop timed out. May 29 16:34:02 ox.rosenauer.org systemd[1]: Timed out stoppping /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-13058ed64bd143069946108705751b17-cr_sda7. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dLUKS1\x2d13058ed64bd143069946108705751b17\x2dcr_sda7.device/stop failed with result 'timeout'. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2did-dm\x2dname\x2dcr_sda7.device/stop timed out. May 29 16:34:02 ox.rosenauer.org systemd[1]: Timed out stoppping /dev/disk/by-id/dm-name-cr_sda7. May 29 16:34:02 ox.rosenauer.org systemd[1]: Job dev-disk-by\x2did-dm\x2dname\x2dcr_sda7.device/stop failed with result 'timeout'. May 29 16:34:03 ox.rosenauer.org systemd[1]: Job dev-dm\x2d0.device/stop timed out. May 29 16:34:03 ox.rosenauer.org systemd[1]: Job dev-dm\x2d0.device/stop failed with result 'timeout'. May 29 16:34:03 ox.rosenauer.org systemd[1]: Job sys-devices-virtual-block-dm\x2d0.device/stop timed out. May 29 16:34:03 ox.rosenauer.org systemd[1]: Job sys-devices-virtual-block-dm\x2d0.device/stop failed with result 'timeout'. May 29 16:34:05 ox.rosenauer.org systemd[1]: acpid.service stopping timed out. Killing. May 29 16:34:05 ox.rosenauer.org systemd[1]: acpid.service: main process exited, code=killed, status=9/KILL May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopped ACPI Event Daemon. May 29 16:34:05 ox.rosenauer.org systemd[1]: Unit acpid.service entered failed state May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping Basic System. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopped target Basic System. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping Daily Cleanup of Temporary Directories. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopped Daily Cleanup of Temporary Directories. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping Sockets. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopped target Sockets. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping PC/SC Smart Card Daemon Activation Socket. May 29 16:34:05 ox.rosenauer.org systemd[1]: Closed PC/SC Smart Card Daemon Activation Socket. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping Avahi mDNS/DNS-SD Stack Activation Socket. May 29 16:34:05 ox.rosenauer.org systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping System Initialization. May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping LSB: iSCSI initiator daemon root-fs support... May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopping Apply Kernel Variables... May 29 16:34:05 ox.rosenauer.org systemd[1]: Stopped LSB: iSCSI initiator daemon root-fs support. May 29 16:34:05 ox.rosenauer.org systemd[1]: Started Save Random Seed. May 29 16:34:05 ox.rosenauer.org systemd[1]: Started Update UTMP about System Shutdown. May 29 16:34:10 ox.rosenauer.org systemd-cryptsetup[25682]: Failed to deactivate: Invalid argument May 29 16:34:10 ox.rosenauer.org systemd[1]: systemd-cryptsetup@cr_sda7.service: control process exited, code=exited status=1 May 29 16:34:10 ox.rosenauer.org systemd[1]: Stopped Cryptography Setup for cr_sda7. May 29 16:34:10 ox.rosenauer.org systemd[1]: Unit systemd-cryptsetup@cr_sda7.service entered failed state May 29 16:34:10 ox.rosenauer.org systemd[1]: Starting Unmount All Filesystems. May 29 16:34:10 ox.rosenauer.org systemd[1]: Reached target Unmount All Filesystems. May 29 16:34:10 ox.rosenauer.org systemd[1]: Stopping Replay Read-Ahead Data... May 29 16:34:10 ox.rosenauer.org systemd[1]: Stopped Replay Read-Ahead Data. May 29 16:34:10 ox.rosenauer.org systemd[1]: Stopping Collect Read-Ahead Data... May 29 16:34:10 ox.rosenauer.org systemd[1]: Stopped Collect Read-Ahead Data. May 29 16:34:10 ox.rosenauer.org systemd[1]: Starting Shutdown. May 29 16:34:10 ox.rosenauer.org systemd[1]: Reached target Shutdown. May 29 16:34:10 ox.rosenauer.org systemd[1]: Shutting down. May 29 16:34:10 ox.rosenauer.org systemd-journal[249]: Journal stopped Is that something you had in mind? Otherwise please tell me what to do since I'm still no systemd/journal expert and have no idea how to debug that stuff. -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c6 systemd maintainers <systemd-maintainers@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |wolfgang@rosenauer.org --- Comment #6 from systemd maintainers <systemd-maintainers@suse.de> 2014-01-17 13:00:03 UTC --- Is this bug still valid or a duplicate of a bug for openSUSE 13.1 in the meanwhile? -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c7 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|wolfgang@rosenauer.org | --- Comment #7 from Wolfgang Rosenauer <wolfgang@rosenauer.org> 2014-01-17 13:24:49 UTC --- Sorry, I don't know. I don't have the hardware anymore -- 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=810456 https://bugzilla.novell.com/show_bug.cgi?id=810456#c8 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |werner@suse.com Resolution| |WONTFIX --- Comment #8 from Dr. Werner Fink <werner@suse.com> 2014-01-17 13:37:23 UTC --- OK ... then I close it WONTFIX as there is no point CANNOTVERIFY :(( I'm pretty sure that this bug is valid that is there is IMHO a dependency race and/or is related to journaling onto the disk somehow but how should we proceed without testing and verification. I'd really like to fix this as I'm pretty sure we will see such a bug again :} -- 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.
participants (1)
-
bugzilla_noreply＠novell.com