Random reboots when resuming from disk (aka hibernation)

nvteighen · 2014-10-27 12:15:46

Hi,
I've noticed that since the Linux 3.17.1-1 upgrade, my laptop frequently fails to resume from disk : after I turn the system on, GRUB kicks in and the system immediately reboots itself (which leads to fsck checking the filesystem). The weird thing is that it seems to be a completely random behavior, as at least half of the time resuming from disk works as it always had.
Of course, the logs don't show anything about it as the failure occurs before the kernel is loaded. However, there's a couple of ACPI-related warnings that I wonder whether they're trying to tell me something:

[    0.174166] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    0.174557] ACPI: Dynamic OEM Table Load:
[    0.174565] ACPI: SSDT 0xFFFF880118886000 000853 (v01 PmRef  Cpu0Cst  00003001 INTL 20051117)
[    0.184302] ACPI: Dynamic OEM Table Load:
[    0.184308] ACPI: SSDT 0xFFFF880118A47800 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)
[    0.197523] ACPI: Dynamic OEM Table Load:
[    0.197528] ACPI: SSDT 0xFFFF880118A70800 000119 (v01 PmRef  ApCst    00003000 INTL 20051117)
[    0.211364] ACPI: Interpreter enabled
[    0.211372] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
[    0.211377] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
[    0.211392] ACPI: (supports S0 S3 S4 S5)
[    0.211394] ACPI: Using IOAPIC for interrupt routing
[    0.211419] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.228928] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.230264] pci 0000:00:14.0: System wakeup disabled by ACPI
[    0.230682] pci 0000:00:1a.0: System wakeup disabled by ACPI
[    0.230879] pci 0000:00:1b.0: System wakeup disabled by ACPI
[    0.231061] pci 0000:00:1c.0: System wakeup disabled by ACPI
[    0.231413] pci 0000:00:1c.3: System wakeup disabled by ACPI
[    0.231628] pci 0000:00:1d.0: System wakeup disabled by ACPI
[    0.232566] pci 0000:02:00.0: System wakeup disabled by ACPI
[    0.237796] pci 0000:03:00.0: System wakeup disabled by ACPI
[    0.244692] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
[    0.244743] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.244792] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.244840] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.244888] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.244937] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.244988] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.245037] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[    0.245197] ACPI: Enabled 4 GPEs in block 00 to 3F
[    0.245273] ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
[    0.245532] PCI: Using ACPI for IRQ routing
[    0.255510] pnp: PnP ACPI init
[    0.255639] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.255784] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.255816] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.255869] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.255919] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.255980] pnp 00:05: Plug and Play ACPI device, IDs ETD0108 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
[    0.256020] pnp 00:06: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
[    0.256221] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.256296] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.256438] system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.256470] pnp: PnP ACPI: found 10 devices
[    0.393967] ACPI: Lid Switch [LID]
[    0.394093] ACPI: Sleep Button [SLPB]
[    0.394201] ACPI: Power Button [PWRF]
[    1.254778] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.337375] asus_wmi: Backlight controlled by ACPI video driver
[    1.362831] ACPI: bus type USB registered
[    1.732186] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.733010] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    1.733040] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    1.733714] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    1.733725] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    1.737970] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    1.737979] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    1.793602] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    1.793992] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    1.794003] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    8.830064] ACPI: Battery Slot [BAT0] (battery present)
[    8.830950] ACPI: AC Adapter [AC0] (off-line)
[    8.919453] ACPI: Thermal Zone [THRM] (37 C)
[    9.007936] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000044f (\GPIS) (20140724/utaddress-258)
[    9.007942] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140724/utaddress-258)
[    9.007946] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.007950] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[    9.007953] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[    9.007956] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.007957] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[    9.007960] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[    9.007963] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.007964] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\GPIO) (20140724/utaddress-258)
[    9.007967] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20140724/utaddress-258)
[    9.007969] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.027976] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\SMB0) (20140724/utaddress-258)
[    9.027985] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
[    9.027991] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

I use the asus_wmi module in this system and, as it is an Intel chipset, I've proceeded to load the intel-ucode as the first initramfs as recommended. Tell me if you need further information.

Thanks in advance!

Last edited by nvteighen (2014-10-27 12:17:34)

giddie · 2014-10-28 12:37:41

You might want to try removing the intel-ucode package (and amending your initrd config so that it won't complain) and see if the problem persists?

nvteighen · 2014-11-03 13:41:23

giddie wrote:

You might want to try removing the intel-ucode package (and amending your initrd config so that it won't complain) and see if the problem persists?

OK, I've made a try by deleting all references to the intel-ucode initrd at /boot/grub/grub.cfg, so that the microcode update is not applied. Afterwards, I rebooted the system so that there is no trace of the microcode update left on the system and proceeded to do some normal usage of the laptop. Then, I've hibernated it, left it like that for a couple of hours and then, turned it on again. The process failed again without warning whatsoever and rebooted to a normal boot sequence.

Looking at all the suspend-to-RAM issues that people are also posting in these forums, I believe this is a bug in Linux 3.17, unrelated to the microcode thing.

AleXoundOS · 2015-07-26 15:39:52

I experience the same issue but with linux-ck-sandybridge kernel starting from 4.0 version.
Do you have any progress?

Arch Linux

#1 2014-10-27 12:15:46

Random reboots when resuming from disk (aka hibernation)

#2 2014-10-28 12:37:41

Re: Random reboots when resuming from disk (aka hibernation)

#3 2014-11-03 13:41:23

Re: Random reboots when resuming from disk (aka hibernation)

#4 2015-07-26 15:39:52

Re: Random reboots when resuming from disk (aka hibernation)

Board footer