My Leap 15.4 system restarts on shutdown

I have a new install of Leap 15.4 and when I try to shutdown either from the KDE menu or doing a shutdown -h now command from a console the system shuts down and immediately powers back on again. The BIOS is set for power off after a power failure. This system is fully up to date. The only way to get it to stay off is to hold the power button for 4 seconds, then it does not restart.

Any ideas please? What do I need to check on this system?

Stuart

Hi Stuart
What about systemctl poweroff does that work? No changes to /etc/systemd/logind.conf?

I have also noticed that my leap 15.4a qemu vm guest running on a leap 15.3 host restarts after being shutdown through the dektop menu. It also restarts after being shutdown additionally through the vm manager menu.

VM manager shows it shutdown prior to being closed. Upon restarting vm manager at a later time, leap 15.4a is running. The other vms in vm manager do not exhibit this behavior.

tom kosvic

Malcolm the logind.conf has every line apart from [Login] commented out, also systemctl poweroff works in that it powers down but then it turns back on again a few moments later. I suppose it wold be more correct to say they all power down the PC that is the power light goes out but it then it comes back on again.

Stuart

You say it is a new install, but is that also on new hardware. or had it an earlier operating system that did not do this.

I had this once, long ago, on a system and can remember there was once (also some time ago) a thread about this from someone else.

I guess this is a firmware thing. Restarting after power outage or so. Try to experiment with those BIOS settings.

It is a second user Gigabyte Brix PC which had a different OS on it, however I replaced the hdd with an empty one and re-partitioned it and installed 15.4. Prior to this I also installed the latest available BIOS and went through the somewhat limited BIOS settings and made sure the option after a power outage was set to not power up. It is accessed via a KVM switch so it has no mouse or monitor of its own and the KVM is switched via a keyboard hot key. I’ll do some more testing.

Stuart

BIOS may be set to wake up on some events (mouse, keyboard, etc) and KVM activity may be interpreted as wake-up trigger.

Sadly on this BIOS there are no options for waking up from any USB devices, mouse/kybd are USB connected.

Stuart

When encountering strange behaviour related to hardware I always load UEFI optimized defaults.

Well this BIOS does not have any option like that just Restore Defaults. There are no USB or keyboard options to allow or prevent a restart in BIOS either. The latest available BIOS F9 is installed from Gigabyte.

I have done some more testing and found that any keyboard operation will restart this PC, so the answer is to switch away from it before it completes shutdown. The other issue is that it does not like the keyboard on power up so cannot enter BIOS, this is where the System Settings option comes in handy to force a reboot to BIOS so I can get into it that way.

Stuart

Installed when, before 15.4? Installed why?

Does it have a defective CMOS battery? Does it do the same thing if you boot some live Linux media, DVD or USB, other than 15.4?

I’ve recently, and longer ago, encountered same behavior, but ignored it, flipping the PS switch to off (or pulled the plug if no PS switch). Which OS did that recently I don’t remember, but it was on a PC with legacy BIOS only. IIRC, this can be repeatable if the CMOS battery is dead, too weak, or not installed.

One of my machines exhibited severe problems with power management which occurred with openSUSE only. Did you ever try a system of another vendor? You may show your journal by running “journalctl --dmesg -g acpi” and posting the output here or at susepaste if too long.

So far this is the only Linux vendor I’ve used. Listing as requested https://paste.opensuse.org/79274647.

Stuart

I installed the latest BIOS because I have two of these (one with Windows on) and it was needed on one so I installed on the second one just in case. I’ll try a USB stick and see. The CMOS battery was replaced when I got the PC and was installing the hdd.

Stuart

Great. But this is boot only. No events logged so far. You may try to paste the whole kernel journal by omitting -g acpi, see the following fragment:

**6700K:~ #** journalctl --dmesg --since 18:00 --no-pager  
Jun 21 18:13:15 6700K kernel: Filesystems sync: 0.168 seconds 
Jun 21 18:13:15 6700K kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. 
Jun 21 18:13:15 6700K kernel: OOM killer disabled. 
Jun 21 18:13:15 6700K kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 
Jun 21 18:13:15 6700K kernel: printk: Suspending console(s) (use no_console_suspend to debug) 
Jun 21 18:13:15 6700K kernel: serial 00:02: disabled 
Jun 21 18:13:15 6700K kernel: e1000e: EEE TX LPI TIMER: 00000011 
Jun 21 18:13:15 6700K kernel: **sd 2:0:0:0: [sda] Synchronizing SCSI cache**
Jun 21 18:13:15 6700K kernel: **sd 2:0:0:0: [sda] Stopping disk**
Jun 21 18:13:15 6700K kernel: **sd 3:0:0:0: [sdb] Synchronizing SCSI cache**
Jun 21 18:13:15 6700K kernel: **sd 3:0:0:0: [sdb] Stopping disk**
Jun 21 18:13:15 6700K kernel: ACPI: PM: Preparing to enter system sleep state S3 
Jun 21 18:13:15 6700K kernel: ACPI: PM: Saving platform NVS memory 
Jun 21 18:13:15 6700K kernel: Disabling non-boot CPUs ... 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 1 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 2 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 3 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 4 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 5 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 6 is now offline 
Jun 21 18:13:15 6700K kernel: smpboot: CPU 7 is now offline 
Jun 21 18:13:15 6700K kernel: **[Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -2992681516. Restoring**
Jun 21 18:13:15 6700K kernel: ACPI: PM: Low-level resume complete 
Jun 21 18:13:15 6700K kernel: ACPI: PM: Restoring platform NVS memory 
Jun 21 18:13:15 6700K kernel: Enabling non-boot CPUs ... 
Jun 21 18:13:15 6700K kernel: x86: Booting SMP configuration: 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 
Jun 21 18:13:15 6700K kernel: CPU1 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4 
Jun 21 18:13:15 6700K kernel: CPU2 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6 
Jun 21 18:13:15 6700K kernel: CPU3 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1 
Jun 21 18:13:15 6700K kernel: CPU4 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3 
Jun 21 18:13:15 6700K kernel: CPU5 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5 
Jun 21 18:13:15 6700K kernel: CPU6 is up 
Jun 21 18:13:15 6700K kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7 
Jun 21 18:13:15 6700K kernel: CPU7 is up 
Jun 21 18:13:15 6700K kernel: ACPI: PM: Waking up from system sleep state S3 
Jun 21 18:13:15 6700K kernel: **sd 2:0:0:0: [sda] Starting disk**
Jun 21 18:13:15 6700K kernel: **sd 3:0:0:0: [sdb] Starting disk**
Jun 21 18:13:15 6700K kernel: **i915 0000:00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it**
Jun 21 18:13:15 6700K kernel: **i915 0000:00:02.0: [drm] [ENCODER:110:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it**
Jun 21 18:13:15 6700K kernel: **i915 0000:00:02.0: [drm] [ENCODER:114:DDI D/PHY D] is disabled/in DSI mode with an ungated DDI clock, gate it**
Jun 21 18:13:15 6700K kernel: serial 00:02: activated 
Jun 21 18:13:15 6700K kernel: ata1: SATA link down (SStatus 4 SControl 300) 
Jun 21 18:13:15 6700K kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
Jun 21 18:13:15 6700K kernel: ata6: SATA link down (SStatus 4 SControl 300) 
Jun 21 18:13:15 6700K kernel: ata5: SATA link down (SStatus 4 SControl 300) 
Jun 21 18:13:15 6700K kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 
Jun 21 18:13:15 6700K kernel: ata2: SATA link down (SStatus 4 SControl 300) 
Jun 21 18:13:15 6700K kernel: **ata3.00: supports DRM functions and may not be fully accessible**
Jun 21 18:13:15 6700K kernel: **ata4.00: supports DRM functions and may not be fully accessible**
Jun 21 18:13:15 6700K kernel: **ata4.00: supports DRM functions and may not be fully accessible**
Jun 21 18:13:15 6700K kernel: ata4.00: configured for UDMA/133 
Jun 21 18:13:15 6700K kernel: **ata3.00: supports DRM functions and may not be fully accessible**
Jun 21 18:13:15 6700K kernel: ata3.00: configured for UDMA/133 
Jun 21 18:13:15 6700K kernel: OOM killer enabled. 
Jun 21 18:13:15 6700K kernel: Restarting tasks ... done. 
Jun 21 18:13:15 6700K kernel: video LNXVIDEO:00: Restoring backlight state 
Jun 21 18:13:15 6700K kernel: PM: suspend exit 
**6700K:~ #**