No reboot or poweroff after upgrade to 5.0.x kernel

English Install/Boot/Login
#1

No reboot or poweroff after upgrade to 5.0.x kernel: systemd passes all the steps before reboot or poweroff, however no actual reboot or poweroff happen:

апр 04 02:06:41 localhost.localdomain systemd[1]: Reached target Unmount All Filesystems.
...
апр 04 02:06:41 localhost.localdomain systemd[1]: Stopped target Local File Systems (Pre).
апр 04 02:06:41 localhost.localdomain systemd[1]: systemd-remount-fs.service: Succeeded.
апр 04 02:06:41 localhost.localdomain systemd[1]: Stopped Remount Root and Kernel File Systems.
апр 04 02:06:41 localhost.localdomain systemd[1]: systemd-fsck-root.service: Succeeded.
апр 04 02:06:41 localhost.localdomain systemd[1]: Stopped File System Check on Root Device.
апр 04 02:06:41 localhost.localdomain systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
апр 04 02:06:41 localhost.localdomain systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
апр 04 02:06:41 localhost.localdomain systemd[1]: Stopped Create Static Device Nodes in /dev.
апр 04 02:06:41 localhost.localdomain systemd[1]: Reached target Shutdown.
апр 04 02:06:41 localhost.localdomain systemd[1]: Reached target Final Step.
апр 04 02:06:41 localhost.localdomain systemd[1]: systemd-poweroff.service: Succeeded.
апр 04 02:06:41 localhost.localdomain systemd[1]: Started Power-Off.
апр 04 02:06:41 localhost.localdomain systemd[1]: Reached target Power-Off.
апр 04 02:06:41 localhost.localdomain systemd[1]: Shutting down.

How to fix?

Could be the same issue as mentioned here: https://forums.opensuse.org/showthread.php/535454-help-finding-the-cause-why-a-computer-never-shuts-down

#2

What comes after “Shutting down” on a machine that does shutdown:

erlangen:~ # journalctl -b -1 | tail
Apr 05 06:05:54 erlangen systemd[1]: Shutting down.
Apr 05 06:05:54 erlangen systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Apr 05 06:05:54 erlangen systemd[1]: Set hardware watchdog to 10min.
Apr 05 06:05:54 erlangen kernel: watchdog: watchdog0: watchdog did not stop!
Apr 05 06:05:54 erlangen kernel: printk: systemd-shutdow: 68 output lines suppressed due to ratelimiting
Apr 05 06:05:54 erlangen systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 05 06:05:54 erlangen systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 05 06:05:54 erlangen haveged[528]: haveged: Stopping due to signal 15
Apr 05 06:05:54 erlangen haveged[528]: haveged starting up
Apr 05 06:05:54 erlangen systemd-journald[529]: Journal stopped
erlangen:~ #
#3

Nothing: power still ON on the machine - it does not switch power-OFF on the PC.

#4

You may run “sync” in a root shell and only then run “reboot”.

#5

And how this will solve the problem as I run reboot or power-off from KDE 5 menu?! Problem happen every day on power-off.

#6

It will not solve the problem. It may help to diagnose the problem. Does it sync or doesn’t it?

#7

When it gets to that point, it should be safe to manually power off.

#8

Of course :slight_smile: However I’d like to do this automatically as before. Why it is broken?!

#9

I don’t know. But I’ve lived through that with a previous computer. Then, it started working again with a later release of openSUSE.

I think it has to do with compile time options for the kernel. But it never seemed worth the effort of investigating.

#10

It’s the same thing that’s happening to one of my computers!

Sometimes after the “Shutting down” message I get messages about:

  • watchdog0 failing to stop
  • usb3 cable being bad

I’v tried waiting 8 hours and the computer never reboots or shutdown. On rare occasions reboot or shutdown has worked, maybe 5% of the time.

#11

Tried: does not help. Any other ideas?

#12

Interrupt grub booting and add the kernel parameter “acpi=force” and then see if the machine powers off OK at shutdown. It’s quite safe to try, either works or it doesn’t, if it does then you can add it permanently as a kernel parameter.

If you’re certain this was caused by the 5.x kernel then I’d file a bug report at: https://bugzilla.opensuse.org against the kernel.

#13

“acpi=force” does not help. Will report to bugzilla as I’d changed nothing in system settings, only do regular updates periodically: zypper dup.
https://bugzilla.opensuse.org/show_bug.cgi?id=1131757

#14

I am unsure about the exact meaning of your answer. Therefore I am asking: What is the result of running sync: does it terminate normally and return to the shell prompt?

On a successful reboot the log reads:

erlangen:~ # journalctl -b -1 -o short-monotonic 
....
[65676.764010] erlangen systemd[1]: Stopped target Local File Systems.
[65676.764280] erlangen systemd[1]: Unmounting /home-SSD...
[65676.764624] erlangen systemd[1]: Unmounting /home...
[65676.764984] erlangen systemd[1]: Unmounting /home-HDD...
[65676.083994] erlangen kernel: kauditd_printk_skb: 22 callbacks suppressed
[65676.083995] erlangen kernel: audit: type=1305 audit(1554437152.627:117): audit_pid=0 old=975 auid=4294967295 ses=4294967295 subj==unconfined res=1
[65676.765429] erlangen systemd[1]: Unmounting /boot/efi...
[65676.765859] erlangen systemd[1]: Unmounting /Tumbleweed-SSD...
[65676.769729] erlangen systemd[1]: boot-efi.mount: Succeeded.
[65676.770125] erlangen systemd[1]: Unmounted /boot/efi.
[65676.801768] erlangen systemd[1]: dev-disk-by\x2did-scsi\x2d0ATA_WDC_WD40EZRX\x2d22S_WD\x2dWCC4E2FYXSNV\x2dpart3.swap: Succeeded.
[65676.802040] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/scsi-0ATA_WDC_WD40EZRX-22S_WD-WCC4E2FYXSNV-part3.
[65676.802176] erlangen systemd[1]: dev-disk-by\x2did-scsi\x2d350014ee262d2e71e\x2dpart3.swap: Succeeded.
[65676.802501] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/scsi-350014ee262d2e71e-part3.
[65676.803150] erlangen systemd[1]: dev-disk-by\x2did-scsi\x2d1ATA_WDC_WD40EZRX\x2d22SPEB0_WD\x2dWCC4E2FYXSNV\x2dpart3.swap: Succeeded.
[65676.803478] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/scsi-1ATA_WDC_WD40EZRX-22SPEB0_WD-WCC4E2FYXSNV-part3.
[65676.804188] erlangen systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2dscsi\x2d0:0:0:0\x2dpart3.swap: Succeeded.
[65676.804543] erlangen systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:17.0-scsi-0:0:0:0-part3.
[65676.805112] erlangen systemd[1]: dev-disk-by\x2dpartlabel-primary.swap: Succeeded.
[65676.805455] erlangen systemd[1]: Deactivated swap /dev/disk/by-partlabel/primary.
[65676.806246] erlangen systemd[1]: dev-disk-by\x2did-wwn\x2d0x50014ee262d2e71e\x2dpart3.swap: Succeeded.
[65676.806607] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x50014ee262d2e71e-part3.
[65676.807304] erlangen systemd[1]: dev-disk-by\x2did-scsi\x2dSATA_WDC_WD40EZRX\x2d22S_WD\x2dWCC4E2FYXSNV\x2dpart3.swap: Succeeded.
[65676.807646] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/scsi-SATA_WDC_WD40EZRX-22S_WD-WCC4E2FYXSNV-part3.
[65676.808278] erlangen systemd[1]: dev-disk-by\x2did-ata\x2dWDC_WD40EZRX\x2d22SPEB0_WD\x2dWCC4E2FYXSNV\x2dpart3.swap: Succeeded.
[65676.808600] erlangen systemd[1]: Deactivated swap /dev/disk/by-id/ata-WDC_WD40EZRX-22SPEB0_WD-WCC4E2FYXSNV-part3.
[65676.809216] erlangen systemd[1]: dev-disk-by\x2dlabel-Swap.swap: Succeeded.
[65676.809561] erlangen systemd[1]: Deactivated swap /dev/disk/by-label/Swap.
[65676.810158] erlangen systemd[1]: dev-disk-by\x2dpartuuid-abcabcc6\x2d4c37\x2d4cdb\x2daa4b\x2da450e5e7585f.swap: Succeeded.
[65676.810514] erlangen systemd[1]: Deactivated swap /dev/disk/by-partuuid/abcabcc6-4c37-4cdb-aa4b-a450e5e7585f.
[65676.811108] erlangen systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1\x2dpart3.swap: Succeeded.
[65676.811432] erlangen systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:17.0-ata-1-part3.
[65676.812034] erlangen systemd[1]: dev-sda3.swap: Succeeded.
[65676.812367] erlangen systemd[1]: Deactivated swap /dev/sda3.
[65676.813582] erlangen systemd[1]: dev-disk-by\x2duuid-699eabfd\x2d107e\x2d488a\x2d9d9d\x2d9e5a280084bd.swap: Succeeded.
[65676.813921] erlangen systemd[1]: Deactivated swap /dev/disk/by-uuid/699eabfd-107e-488a-9d9d-9e5a280084bd.
[65676.814060] erlangen systemd[1]: home\x2dSSD.mount: Succeeded.
[65676.814360] erlangen systemd[1]: Unmounted /home-SSD.
[65676.833175] erlangen systemd[1]: Tumbleweed\x2dSSD.mount: Succeeded.
[65676.833521] erlangen systemd[1]: Unmounted /Tumbleweed-SSD.
[65677.804555] erlangen systemd[1]: home.mount: Succeeded.
[65677.804837] erlangen systemd[1]: Unmounted /home.
[65678.234583] erlangen systemd[1]: home\x2dHDD.mount: Succeeded.
[65678.234844] erlangen systemd[1]: Unmounted /home-HDD.
[65678.234965] erlangen systemd[1]: Reached target Unmount All Filesystems.
[65678.235862] erlangen systemd[1]: Stopped target Local File Systems (Pre).
[65678.235943] erlangen systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
[65678.236233] erlangen systemd[1]: Stopped Create Static Device Nodes in /dev.
[65678.236919] erlangen systemd[1]: systemd-remount-fs.service: Succeeded.
[65678.237161] erlangen systemd[1]: Stopped Remount Root and Kernel File Systems.
[65678.237815] erlangen systemd[1]: Reached target Shutdown.
[65678.238754] erlangen systemd[1]: Reached target Final Step.
[65678.238905] erlangen systemd[1]: systemd-reboot.service: Succeeded.
[65678.238967] erlangen systemd[1]: Started Reboot.
[65678.239760] erlangen systemd[1]: Reached target Reboot.
[65678.240649] erlangen systemd[1]: Shutting down.
[65678.297779] erlangen systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
[65678.298116] erlangen systemd[1]: Set hardware watchdog to 10min.
[65677.618966] erlangen kernel: watchdog: watchdog0: watchdog did not stop!
[65677.623431] erlangen kernel: printk: systemd-shutdow: 68 output lines suppressed due to ratelimiting
[65677.635807] erlangen systemd-shutdown[1]: Syncing filesystems and block devices.
[65677.649997] erlangen systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[65678.342868] erlangen haveged[528]: haveged: Stopping due to signal 15
[65678.344117] erlangen haveged[528]: haveged starting up
[65678.344393] erlangen systemd-journald[529]: Journal stopped

What is logged on your machine starting from: “Stopped target Local File Systems” and the end of the logs

#15

Just to provide a little more information, it might be advisable to attach the output of “hwinfo” to that bug report.

@karlmistelberger

As the OP’s system did shut down / reboot prior to the upgrade to kernel 5.x this may well be a kernel regression that is only affecting particular hardware. I’ve certainly seen this in the past, with more or less identical symptoms.

#16

Yes, sync returns successfully without any messages.

My variant:

erlangen:~ # journalctl -b -1 -o short-monotonic 
....
  319.173242] localhost systemd[1]: Stopped target Local File Systems.
  319.175047] localhost systemd[1]: Unmounting /windows/e...
  319.176033] localhost systemd[1]: Unmounting /windows/d...
  319.177368] localhost systemd[1]: Unmounting /windows/c...
  319.178564] localhost systemd[1]: Unmounting /boot...
  319.179719] localhost systemd[1]: Unmounting /home...
  319.221405] localhost ntfs-3g[1013]: Unmounting /dev/sdb5 (Distrib)
  319.565760] localhost systemd[1]: windows-e.mount: Succeeded.
  319.566074] localhost ntfs-3g[1008]: Unmounting /dev/sdb1 (System)
  319.566649] localhost systemd[1]: Unmounted /windows/e.
  319.566990] localhost ntfs-3g[992]: Unmounting /dev/sdb6 (Storage)
  319.567209] localhost systemd[1]: windows-d.mount: Succeeded.
  319.567321] localhost systemd[1]: Unmounted /windows/d.
  319.567414] localhost systemd[1]: windows-c.mount: Succeeded.
  319.567505] localhost systemd[1]: Unmounted /windows/c.
  319.567608] localhost systemd[1]: dev-disk-by\x2dpartuuid-000ba470\x2d03.swap: Succeeded.
  319.567718] localhost systemd[1]: Deactivated swap /dev/disk/by-partuuid/000ba470-03.
  319.567825] localhost systemd[1]: dev-disk-by\x2did-scsi\x2d1ATA_ST2000DM001\x2d1CH164_Z1E5Q3CY\x2dpart3.swap: Succeeded.
  319.567933] localhost systemd[1]: Deactivated swap /dev/disk/by-id/scsi-1ATA_ST2000DM001-1CH164_Z1E5Q3CY-part3.
  319.568035] localhost systemd[1]: dev-disk-by\x2did-scsi\x2d0ATA_ST2000DM001\x2d1CH1_Z1E5Q3CY\x2dpart3.swap: Succeeded.
  319.568150] localhost systemd[1]: Deactivated swap /dev/disk/by-id/scsi-0ATA_ST2000DM001-1CH1_Z1E5Q3CY-part3.
  319.568252] localhost systemd[1]: dev-disk-by\x2did-wwn\x2d0x5000c50064fc2f3f\x2dpart3.swap: Succeeded.
  319.568346] localhost systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000c50064fc2f3f-part3.
  319.568456] localhost systemd[1]: dev-disk-by\x2did-scsi\x2dSATA_ST2000DM001\x2d1CH1_Z1E5Q3CY\x2dpart3.swap: Succeeded.
  319.568555] localhost systemd[1]: Deactivated swap /dev/disk/by-id/scsi-SATA_ST2000DM001-1CH1_Z1E5Q3CY-part3.
  319.568664] localhost systemd[1]: dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1E5Q3CY\x2dpart3.swap: Succeeded.
  319.568769] localhost systemd[1]: Deactivated swap /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1E5Q3CY-part3.
  319.568871] localhost systemd[1]: dev-disk-by\x2did-scsi\x2d35000c50064fc2f3f\x2dpart3.swap: Succeeded.
  319.568963] localhost systemd[1]: Deactivated swap /dev/disk/by-id/scsi-35000c50064fc2f3f-part3.
  319.569067] localhost systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:11.0\x2data\x2d1\x2dpart3.swap: Succeeded.
  319.569164] localhost systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:11.0-ata-1-part3.
  319.569264] localhost systemd[1]: dev-sda3.swap: Succeeded.
  319.569373] localhost systemd[1]: Deactivated swap /dev/sda3.
  319.569469] localhost systemd[1]: dev-disk-by\x2duuid-a322fe78\x2df7ec\x2d4e2e\x2db58c\x2db24679f93ea5.swap: Succeeded.
  319.569573] localhost systemd[1]: Deactivated swap /dev/disk/by-uuid/a322fe78-f7ec-4e2e-b58c-b24679f93ea5.
  319.569672] localhost systemd[1]: boot.mount: Succeeded.
  319.569769] localhost systemd[1]: Unmounted /boot.
  319.569870] localhost systemd[1]: systemd-fsck@dev-disk-by\x2duuid-6c5d9d33\x2d74c8\x2d427f\x2da162\x2db03dae26dfa7.service: Succeeded.
  319.569969] localhost systemd[1]: Stopped File System Check on /dev/disk/by-uuid/6c5d9d33-74c8-427f-a162-b03dae26dfa7.
  319.570075] localhost systemd[1]: home.mount: Succeeded.
  319.570171] localhost systemd[1]: Unmounted /home.
  319.570264] localhost systemd[1]: Reached target Unmount All Filesystems.
  319.570406] localhost systemd[1]: systemd-fsck@dev-disk-by\x2duuid-11038e2e\x2dc76e\x2d4e45\x2dbefe\x2db7d1fc5a58e1.service: Succeeded.
  319.570506] localhost systemd[1]: Stopped File System Check on /dev/disk/by-uuid/11038e2e-c76e-4e45-befe-b7d1fc5a58e1.
  319.570614] localhost systemd[1]: Removed slice system-systemd\x2dfsck.slice.
  319.570730] localhost systemd[1]: Stopped target Local File Systems (Pre).
  319.570834] localhost systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
  319.570954] localhost systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
  319.571057] localhost systemd[1]: Stopped Create Static Device Nodes in /dev.
  319.571159] localhost systemd[1]: systemd-remount-fs.service: Succeeded.
  319.571264] localhost systemd[1]: Stopped Remount Root and Kernel File Systems.
  319.571363] localhost systemd[1]: systemd-fsck-root.service: Succeeded.
  319.571472] localhost systemd[1]: Stopped File System Check on Root Device.
  319.571576] localhost systemd[1]: Reached target Shutdown.
  319.571691] localhost systemd[1]: Reached target Final Step.
  319.571802] localhost systemd[1]: systemd-reboot.service: Succeeded.
  319.571900] localhost systemd[1]: Started Reboot.
  319.572013] localhost systemd[1]: Reached target Reboot.
  319.572116] localhost systemd[1]: Shutting down.
  319.614615] localhost systemd[1]: Hardware watchdog 'SP5100 TCO timer', version 0
  319.614830] localhost systemd[1]: Set hardware watchdog to 10min.
  319.617658] localhost kernel: watchdog: watchdog0: watchdog did not stop!
  319.647633] localhost kernel: printk: systemd-shutdow: 38 output lines suppressed due to ratelimiting
  319.716255] localhost systemd-shutdown[1]: Syncing filesystems and block devices.
  320.078423] localhost systemd-shutdown[1]: Sending SIGTERM to remaining processes...
  320.092000] localhost iscsid[1436]: iscsid: iscsid shutting down.
  320.092891] localhost systemd-journald[509]: Journal stopped
#17

hwinfo stopped on usb.2: usb and do not continue.

#18

Looks pretty sane. Might be a firmware or hardware problem accidentally starting to occur with kernel upgrade. Tried to reset UEFI to factory defaults?

#19

In BIOS? I have not changed anything there.

#20

Actually anything can happen upon update: https://forums.opensuse.org/showthread.php/520904-Onboard-LAN-disabled I never tinkered with onboard, but it was gone. Resetting BIOS could eventually fix the problem.