Gigabyte z170x-gaming 7 auto boots without reason

Ask Fedora
,
1

After what appears a successful shut-down (power LED is off) my z170x-gaming 7 starts again after about a minute or so. Ultra Fast-boot is disabled. In the UEFI all settings regarding to boot on timer, USB activity is switched off.

Apart from switching off power completely what could cause these involuntary boots?

2

Wake On Lan perhaps.

3

Thanks no

Thanks no that can be ruled out on the broadcast domain

4
  • Does this happen every time?
  • Is there a timeframe (i.e, it’ll always be 30 seconds after powering off)
  • What devices are allowed to wake the BIOS to initiate a full power on? (cat /proc/acpi/wakeup)
  • What’s the version of the BIOS - fully up-to-date?
5

I have a suspision that this is caused by turning from sleep to hibernate. This fails and than the system returns to fully awake. As sleep, suspend, hibernate or hybrid-sleep is not very well documentted (and most are missing from the KDE-Plasma menu) it is quite hard to pin-point this. I have discovered /etc/systemd/sleep.conf so I could experiment a bit.

[Sleep]
AllowSuspend=yes
AllowSuspendThenHibernate=no
AllowHibernate=no
AllowHybridSleep=yes

With these settings my pc does not wake up randomly anymore.

Again it is all a bit guesswork what will do what (there are no man-pages for either sleepconf of sleep.conf or power nor powersettings for that matter.

Also I found this which explains some of these but I’m not sure if these are applicable to Fedora, KDE, my mobo or at all (nowedays, history is killing GNU-Linux support).

  • halt or systemctl halt is halting the system

  • poweroff or systemctl poweroff or the good old shutdown now is powering off completely
    Great!

  • systemctl suspend does indeed suspend the system and seems to come back after hitting the power button but sound is garbled and Bluetooth is not working, so cannot use that.

  • systemctl hibernate much the same thing, albeit it indeed does do a hibernation although it is impossible to tell :person_shrugging:

  • systemctl hybrid-sleep seems to do the same thing. but show quite some storage activity before that.

6

man systemd-sleep and man systemd-sleep.conf have some information.

7

Yeah thanks! I haven´t thought of that. :folded_hands:

Searching in man systemctl did as well:

       sleep
           Put the system to sleep, through suspend, hibernate, hybrid-sleep, or suspend-then-hibernate. The sleep operation to use is automatically selected by systemd-
           logind.service(8). By default, suspend-then-hibernate is used, and falls back to suspend and then hibernate if not supported. Refer to SleepOperation= setting
           in logind.conf(5) for more details. This command is asynchronous, and will return after the sleep operation is successfully enqueued. It will not wait for the
           sleep/resume cycle to complete.

           Added in version 256.

       suspend
           Suspend the system. This will trigger activation of the special target unit suspend.target. This command is asynchronous, and will return after the suspend
           operation is successfully enqueued. It will not wait for the suspend/resume cycle to complete.

           If --force is specified, and systemd-logind returned error for the operation, the error will be ignored and the operation will be tried again directly through
           starting the target unit.

       hibernate
           Hibernate the system. This will trigger activation of the special target unit hibernate.target. This command is asynchronous, and will return after the
           hibernation operation is successfully enqueued. It will not wait for the hibernate/thaw cycle to complete.

           This command honors --force in the same way as suspend.

       hybrid-sleep
           Hibernate and suspend the system. This will trigger activation of the special target unit hybrid-sleep.target. This command is asynchronous, and will return
           after the hybrid sleep operation is successfully enqueued. It will not wait for the sleep/wake-up cycle to complete.

           This command honors --force in the same way as suspend.

           Added in version 196.

       suspend-then-hibernate
           Suspend the system and hibernate it when the battery is low, or when the delay specified in systemd-sleep.conf elapsed. This will trigger activation of the
           special target unit suspend-then-hibernate.target. This command is asynchronous, and will return after the hybrid sleep operation is successfully enqueued. It
           will not wait for the sleep/wake-up or hibernate/thaw cycle to complete.

           This command honors --force in the same way as suspend.

           Added in version 240.