Page 1 of 4 123 ... LastLast
Results 1 to 10 of 39

Thread: No reboot or poweroff after upgrade to 5.0.x kernel

  1. #1

    Talking No reboot or poweroff after upgrade to 5.0.x kernel

    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:

    Code:
    апр 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/showthre...ver-shuts-down

  2. #2
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    774

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    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:

    Code:
    апр 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/showthre...ver-shuts-down
    What comes after "Shutting down" on a machine that does shutdown:

    Code:
    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:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  3. #3

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by karlmistelberger View Post
    What comes after "Shutting down" on a machine that does shutdown:
    Nothing: power still ON on the machine - it does not switch power-OFF on the PC.

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    774

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    Nothing: power still ON on the machine - it does not switch power-OFF on the PC.
    You may run "sync" in a root shell and only then run "reboot".
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  5. #5

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by karlmistelberger View Post
    You may run "sync" in a root shell and only then run "reboot".
    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. #6
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    774

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    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.
    It will not solve the problem. It may help to diagnose the problem. Does it sync or doesn't it?
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  7. #7
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    11,809
    Blog Entries
    3

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    Code:
    апр 04 02:06:41 localhost.localdomain systemd[1]: Reached target Power-Off.
    апр 04 02:06:41 localhost.localdomain systemd[1]: Shutting down.
    When it gets to that point, it should be safe to manually power off.
    openSUSE Leap 15.1; KDE Plasma 5;

  8. #8

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by nrickert View Post
    When it gets to that point, it should be safe to manually power off.
    Of course However I'd like to do this automatically as before. Why it is broken?!

  9. #9
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    11,809
    Blog Entries
    3

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    Why it is broken?!
    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.
    openSUSE Leap 15.1; KDE Plasma 5;

  10. #10

    Default Re: No reboot or poweroff after upgrade to 5.0.x kernel

    Quote Originally Posted by akontsevich View Post
    Could be the same issue as mentioned here: https://forums.opensuse.org/showthre...ver-shuts-down
    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.

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •