[SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

aurelieng · 2014-09-12 05:03:39

Hi all,

End of August, the new kernel 3.16.1-1 landed on my laptop (Dell Precision M6400) and broke resume from suspend to RAM. I identified the problem, downgraded to 3.15.8-1 (which works fine), and started to look for the next kernel update with the hope of a fix. A few dependencies (nvidia, nvidia-libgl, nvidia-utils virtualbox-host-modules) were downgraded as well.

Now that 3.16.2-1 is out, I tried it but unfortunately my laptop still cannot resume. Here's the journalctl output:

Sep 12 06:14:09 XXXXXXXX polkitd[854]: Registered Authentication Agent for unix-process:1579:24935 (system bus name :1.30 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Sep 12 06:14:09 XXXXXXXX polkitd[854]: Unregistered Authentication Agent for unix-process:1579:24935 (system bus name :1.30, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Sep 12 06:14:09 XXXXXXXX systemd-sleep[1583]: Suspending system...
Sep 12 06:14:09 XXXXXXXX kernel: PM: Syncing filesystems ... done.
Sep 12 06:14:09 XXXXXXXX kernel: PM: Preparing system for mem sleep
Sep 12 06:14:10 XXXXXXXX kernel: dell_wmi: Received unknown WMI event (0x11)
Sep 12 06:14:12 XXXXXXXX kernel: dell_wmi: Received unknown WMI event (0x11)
Sep 12 06:14:36 XXXXXXXX kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Sep 12 06:14:36 XXXXXXXX kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep 12 06:14:36 XXXXXXXX kernel: PM: Entering mem sleep
Sep 12 06:14:36 XXXXXXXX kernel: Suspending console(s) (use no_console_suspend to debug)
Sep 12 06:14:36 XXXXXXXX kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
Sep 12 06:14:36 XXXXXXXX kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Sep 12 06:14:36 XXXXXXXX kernel: sd 4:0:0:0: [sdb] Stopping disk
Sep 12 06:14:36 XXXXXXXX kernel: sd 0:0:0:0: [sda] Stopping disk
Sep 12 06:14:36 XXXXXXXX kernel: PM: suspend of devices complete after 366.115 msecs
Sep 12 06:14:36 XXXXXXXX kernel: PM: late suspend of devices complete after 0.616 msecs
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.1: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.2: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.0: System wakeup enabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: PM: noirq suspend of devices complete after 46.179 msecs
Sep 12 06:14:36 XXXXXXXX kernel: ACPI: Preparing to enter system sleep state S3
Sep 12 06:14:36 XXXXXXXX kernel: PM: Saving platform NVS memory
Sep 12 06:14:36 XXXXXXXX kernel: Disabling non-boot CPUs ...
Sep 12 06:14:36 XXXXXXXX kernel: kvm: disabling virtualization on CPU1
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: CPU 1 is now offline
Sep 12 06:14:36 XXXXXXXX kernel: kvm: disabling virtualization on CPU2
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: CPU 2 is now offline
Sep 12 06:14:36 XXXXXXXX kernel: kvm: disabling virtualization on CPU3
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: CPU 3 is now offline
Sep 12 06:14:36 XXXXXXXX kernel: ACPI: Low-level resume complete
Sep 12 06:14:36 XXXXXXXX kernel: PM: Restoring platform NVS memory
Sep 12 06:14:36 XXXXXXXX kernel: Enabling non-boot CPUs ...
Sep 12 06:14:36 XXXXXXXX kernel: x86: Booting SMP configuration:
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Sep 12 06:14:36 XXXXXXXX kernel: kvm: enabling virtualization on CPU1
Sep 12 06:14:36 XXXXXXXX kernel: CPU1 is up
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Sep 12 06:14:36 XXXXXXXX kernel: kvm: enabling virtualization on CPU2
Sep 12 06:14:36 XXXXXXXX kernel: CPU2 is up
Sep 12 06:14:36 XXXXXXXX kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Sep 12 06:14:36 XXXXXXXX kernel: kvm: enabling virtualization on CPU3
Sep 12 06:14:36 XXXXXXXX kernel: CPU3 is up
Sep 12 06:14:36 XXXXXXXX kernel: ACPI: Waking up from system sleep state S3
Sep 12 06:14:36 XXXXXXXX kernel: yenta_cardbus 0000:03:01.0: proprietary Ricoh MMC controller disabled (via cardbus function)
Sep 12 06:14:36 XXXXXXXX kernel: yenta_cardbus 0000:03:01.0: MMC cards are now supported by standard SDHCI controller
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.0: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.1: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1a.2: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
Sep 12 06:14:36 XXXXXXXX kernel: PM: noirq resume of devices complete after 41.710 msecs
Sep 12 06:14:36 XXXXXXXX kernel: PM: early resume of devices complete after 0.636 msecs
Sep 12 06:14:36 XXXXXXXX kernel: usb usb3: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: tg3 0000:09:00.0 eth0: Link is down
Sep 12 06:14:36 XXXXXXXX kernel: usb usb4: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: usb usb5: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: snd_hda_intel 0000:00:1b.0: irq 48 for MSI/MSI-X
Sep 12 06:14:36 XXXXXXXX kernel: usb usb6: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: usb usb7: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: usb usb8: root hub lost power or was reset
Sep 12 06:14:36 XXXXXXXX kernel: sd 0:0:0:0: [sda] Starting disk
Sep 12 06:14:36 XXXXXXXX kernel: sd 4:0:0:0: [sdb] Starting disk
Sep 12 06:14:36 XXXXXXXX kernel: iwlwifi 0000:0c:00.0: RF_KILL bit toggled to disable radio.
Sep 12 06:14:36 XXXXXXXX kernel: usb 1-6: reset high-speed USB device number 3 using ehci-pci
Sep 12 06:14:36 XXXXXXXX kernel: usb 5-1: reset full-speed USB device number 2 using uhci_hcd
Sep 12 06:14:36 XXXXXXXX kernel: usb 7-1: reset full-speed USB device number 2 using uhci_hcd
Sep 12 06:14:36 XXXXXXXX kernel: ata6: SATA link down (SStatus 0 SControl 300)
Sep 12 06:14:36 XXXXXXXX kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 12 06:14:36 XXXXXXXX kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 12 06:14:36 XXXXXXXX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 12 06:14:36 XXXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 12 06:14:36 XXXXXXXX kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Sep 12 06:14:36 XXXXXXXX kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 12 06:14:36 XXXXXXXX kernel: ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Sep 12 06:14:36 XXXXXXXX kernel: ata1.00: configured for UDMA/133
Sep 12 06:14:36 XXXXXXXX kernel: ata2.00: configured for UDMA/133
Sep 12 06:14:36 XXXXXXXX kernel: ata5.00: configured for UDMA/133
Sep 12 06:14:36 XXXXXXXX kernel: dell_wmi: Received unknown WMI event (0x11)
Sep 12 06:14:36 XXXXXXXX kernel: dell_wmi: Received unknown WMI event (0x11)
Sep 12 06:14:36 XXXXXXXX kernel: PM: resume of devices complete after 2049.843 msecs
Sep 12 06:14:36 XXXXXXXX kernel: PM: Finishing wakeup.
Sep 12 06:14:36 XXXXXXXX kernel: Restarting tasks ... 
Sep 12 06:14:36 XXXXXXXX kernel: BUG: unable to handle kernel 
Sep 12 06:14:36 XXXXXXXX kernel: NULL pointer dereference at 0000000000000000
Sep 12 06:14:36 XXXXXXXX kernel: IP: [<ffffffff81321a1e>] acpi_device_hotplug+0x191/0x403
Sep 12 06:14:36 XXXXXXXX kernel: PGD 0 
Sep 12 06:14:36 XXXXXXXX kernel: Oops: 0000 [#1] PREEMPT SMP 
Sep 12 06:14:36 XXXXXXXX kernel: Modules linked in: fuse i8k dm_crypt xts gf128mul algif_skcipher af_alg uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev nvidia(PO) media
Sep 12 06:14:36 XXXXXXXX kernel: done.
Sep 12 06:14:36 XXXXXXXX kernel: video LNXVIDEO:00: Restoring backlight state
Sep 12 06:14:36 XXXXXXXX kernel:  dell_wmi
Sep 12 06:14:36 XXXXXXXX kernel:  gpio_ich sparse_keymap iTCO_wdt iTCO_vendor_support ppdev joydev mousedev dm_mod pcmcia dell_laptop dcdbas ipt_REJECT xt_LOG xt_recent coretemp kvm_intel xt_limit kvm arc4 xt_tcpudp xt_addrtype evdev microcode mac_hid psmouse serio_raw r852 nf_conntrack_ipv4 nf_defrag_ipv4 sm_common xt_conntrack iwldvm nand i2c_i801 nand_ecc mac80211 nand_ids r592 mtd lpc_ich memstick iwlwifi tg3 yenta_socket pcmcia_rsrc pcmcia_core ptp pps_core cfg80211 libphy drm hwmon i2c_core rfkill video thermal parport_pc parport intel_agp tpm_tis shpchp intel_gtt ac tpm wmi button battery ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables snd_hda_codec_idt snd_hda_codec_generic tun snd_hda_intel snd_hda_controller
Sep 12 06:14:36 XXXXXXXX kernel:  snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore loop cpufreq_powersave acpi_cpufreq processor ext4 crc16 mbcache jbd2 sd_mod sr_mod cdrom crc_t10dif crct10dif_common hid_generic usbhid hid atkbd libps2 sdhci_pci sdhci led_class mmc_core ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common i8042 serio
Sep 12 06:14:36 XXXXXXXX kernel: CPU: 1 PID: 1659 Comm: kworker/u8:79 Tainted: P           O  3.16.2-1-ARCH #1
Sep 12 06:14:36 XXXXXXXX kernel: Hardware name: Dell Inc. Precision M6400                 /0D138P, BIOS A12 12/11/2011
Sep 12 06:14:36 XXXXXXXX kernel: Workqueue: kacpi_hotplug acpi_hotplug_work_fn
Sep 12 06:14:36 XXXXXXXX kernel: task: ffff880408149460 ti: ffff8803c444c000 task.ti: ffff8803c444c000
Sep 12 06:14:36 XXXXXXXX kernel: RIP: 0010:[<ffffffff81321a1e>]  [<ffffffff81321a1e>] acpi_device_hotplug+0x191/0x403
Sep 12 06:14:36 XXXXXXXX kernel: RSP: 0000:ffff8803c444fdc0  EFLAGS: 00010246
Sep 12 06:14:36 XXXXXXXX kernel: RAX: 0000000000000000 RBX: ffff8803e0b96500 RCX: 0000000000000000
Sep 12 06:14:36 XXXXXXXX kernel: RDX: 00000000009c0701 RSI: ffff88041fc973c0 RDI: ffff88040f001a00
Sep 12 06:14:36 XXXXXXXX kernel: RBP: ffff8803c444fdf8 R08: 00000000000173c0 R09: ffffea0010010fc0
Sep 12 06:14:36 XXXXXXXX kernel: R10: ffffffff8133d7f1 R11: ffffea0003263040 R12: ffff880409111800
Sep 12 06:14:36 XXXXXXXX kernel: R13: 0000000000000000 R14: ffff8804091119f8 R15: ffff88040f023988
Sep 12 06:14:36 XXXXXXXX kernel: FS:  0000000000000000(0000) GS:ffff88041fc80000(0000) knlGS:0000000000000000
Sep 12 06:14:36 XXXXXXXX kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Sep 12 06:14:36 XXXXXXXX kernel: CR2: 0000000000000000 CR3: 0000000000000000 CR4: 00000000000407e0
Sep 12 06:14:36 XXXXXXXX kernel: Stack:
Sep 12 06:14:36 XXXXXXXX kernel:  ffff8803e0b96500 00000000cd60648f ffff8803e0b96500 ffff88040f00cc00
Sep 12 06:14:36 XXXXXXXX kernel:  ffff8803e0b96500 ffff880409072600 0ffff88040907260 ffff8803c444fe10
Sep 12 06:14:36 XXXXXXXX kernel:  ffffffff8131b352 ffff8803da78e780 ffff8803c444fe50 ffffffff8108afa8
Sep 12 06:14:36 XXXXXXXX kernel: Call Trace:
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff8131b352>] acpi_hotplug_work_fn+0x1e/0x29
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff8108afa8>] process_one_work+0x168/0x450
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff8108b5db>] worker_thread+0x6b/0x550
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff8108b570>] ? init_pwq.part.22+0x10/0x10
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff81091cea>] kthread+0xea/0x100
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff81091c00>] ? kthread_create_on_node+0x1b0/0x1b0
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff81530cbc>] ret_from_fork+0x7c/0xb0
Sep 12 06:14:36 XXXXXXXX kernel:  [<ffffffff81091c00>] ? kthread_create_on_node+0x1b0/0x1b0
Sep 12 06:14:36 XXXXXXXX kernel: Code: f8 07 00 ba 80 00 00 00 e9 45 02 00 00 31 c9 ba 84 00 00 00 be 03 00 00 00 e8 ec 9f ff ff 49 8b 84 24 d8 01 00 00 4d 8b 7c 24 08 <f6> 00 00 00 00 00 00 00 00 80 3d 4a 66 7e 00 00 75 47 be 01 00 
Sep 12 06:14:36 XXXXXXXX kernel: RIP  [<ffffffff81321a1e>] acpi_device_hotplug+0x191/0x403
Sep 12 06:14:36 XXXXXXXX kernel:  RSP <ffff8803c444fdc0>
Sep 12 06:14:36 XXXXXXXX kernel: CR2: 0000000000000000
Sep 12 06:14:36 XXXXXXXX kernel: ---[ end trace 8ea404f429f451fd ]---
Sep 12 06:14:36 XXXXXXXX kernel: BUG: unable to handle kernel paging request at ffffffffffffffd8
Sep 12 06:14:36 XXXXXXXX kernel: IP: [<ffffffff810923a0>] kthread_data+0x10/0x20

Does anyone have the same bug? Any ideas of what could be wrong? I can investigate, just tell me where to look?

Edit: this is probably similar to the bug 80911 on the kernel bug tracker. It seems it has been fixed, but it's not clear to me in which version of the kernel.

Last edited by aurelieng (2014-09-23 19:07:58)

nostalgix · 2014-09-12 09:10:11

Yes! I have the same issues here. When 3.16.1 appeared resuming after suspend via systemd broke the system. I went back to 3.15 until 3.16.2 came out a few days ago. Hoping that things might have been fixed meanwhile I updated the kernel again, but it's still the same.
I went to tty1 before I hit 'systemctl suspend' and when I resume I see lots of kernel messages, but I haven't been able to redirect them to some file yet.
Laptop is a Dell Latitude E6500 here.

jdoggsc · 2014-09-12 21:06:43

I have the same problem, too. I did a full system update after maybe a month and a half, so there was a ton of stuff that got updated. Ever since, I haven't been able to resume from suspend. My screen just scrolls several screens worth of messages and then the system is completely nonresponsive. I also have a Dell Latitude E6500.

jdoggsc · 2014-09-13 17:25:08

Seeing as how this is on a laptop, I typically suspend by closing the lid, but this time I did a "systemctl suspend" command, and this is the output.
As you can see, the system went down for sleep at 9:28am. At some point, I pressed the power button to resume from sleep. The lights on my computer turned on, but the screen was blank and the computer was completely unresponsive. This event is not captured at all in the systemd journal. The journal only continues after my hard reset at 11:45am.

-- Logs begin at Tue 2013-10-29 22:19:56 EDT, end at Sat 2014-09-13 11:47:00 EDT. --
Sep 13 09:28:18 trogdor sudo[535]: jdoggsc : TTY=tty1 ; PWD=/home/jdoggsc ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Sep 13 09:28:18 trogdor sudo[535]: pam_unix(sudo:session): session opened for user root by jdoggsc(uid=0)
Sep 13 09:28:18 trogdor systemd-sleep[538]: Suspending system...
-- Reboot --
Sep 13 11:45:21 trogdor systemd-journal[124]: Runtime journal is using 8.0M (max allowed 100.3M, trying to leave 150.5M free of 995.9M available → current limit 100.3M).
Sep 13 11:45:21 trogdor systemd-journal[124]: Runtime journal is using 8.0M (max allowed 100.3M, trying to leave 150.5M free of 995.9M available → current limit 100.3M).
Sep 13 11:45:21 trogdor kernel: Initializing cgroup subsys cpuset
Sep 13 11:45:21 trogdor kernel: Initializing cgroup subsys cpu
Sep 13 11:45:21 trogdor kernel: Initializing cgroup subsys cpuacct
Sep 13 11:45:21 trogdor kernel: Linux version 3.16.2-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Sat Sep 6 13:13:35 CEST 2014
Sep 13 11:45:21 trogdor kernel: e820: BIOS-provided physical RAM map:
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f44d3ff] usable
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x000000007f44f400-0x000000007fffffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000fed18000-0x00000000fed1bfff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed8ffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000feda0000-0x00000000feda5fff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee0ffff] reserved
Sep 13 11:45:21 trogdor kernel: BIOS-e820: [mem 0x00000000ffe60000-0x00000000ffffffff] reserved
Sep 13 11:45:21 trogdor kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Sep 13 11:45:21 trogdor kernel: SMBIOS 2.4 present.
Sep 13 11:45:21 trogdor kernel: DMI: Dell Inc. Latitude E6500                  /0F327M, BIOS A27 12/06/2011

The code above was done in init 3 (multi-user.target). When I actually start the graphical interface (xfce or cinnamon on my machine) and then shut the lid, the computer sleeps as desired but when I resume, that's when I get several screens worth of messages scrolling up before my laptop becomes completely nonresponsive.

Checking the systemd journal for this information, I get the following:

As shown, the lid was closed at 12:12:40 and suspend completed by 12:12:43. Again, the lid-open event at 12:53 is not captured by the systemd journal, but the hard reset at 12:56 was.

-- Logs begin at Tue 2013-10-29 22:19:56 EDT, end at Sat 2014-09-13 13:00:26 EDT. --
Sep 13 12:12:40 trogdor systemd-logind[277]: Lid closed.
Sep 13 12:12:41 trogdor kernel: dell_wmi: Received unknown WMI event (0x11)
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> sleep requested (sleeping: no  enabled: yes)
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> sleeping...
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> (wlp12s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> (wlp12s0): deactivating device (reason 'sleeping') [37]
Sep 13 12:12:42 trogdor dhclient[407]: Received signal 15, initiating shutdown.
Sep 13 12:12:42 trogdor NetworkManager[276]: Received signal 15, initiating shutdown.
Sep 13 12:12:42 trogdor dhclient[407]: DHCPRELEASE on wlp12s0 to 192.168.1.1 port 67
Sep 13 12:12:42 trogdor NetworkManager[276]: DHCPRELEASE on wlp12s0 to 192.168.1.1 port 67
Sep 13 12:12:42 trogdor NetworkManager[276]: <warn> (wlp12s0): DHCP client pid 407 didn't exit, will kill it.
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> (wlp12s0): canceled DHCP transaction, DHCP client pid 407
Sep 13 12:12:42 trogdor dhcpcd[283]: wlp12s0: removing IP address 192.168.1.5/24
Sep 13 12:12:42 trogdor avahi-daemon[278]: Withdrawing address record for fe80::222:fbff:fe28:ba22 on wlp12s0.
Sep 13 12:12:42 trogdor avahi-daemon[278]: Withdrawing address record for 192.168.1.5 on wlp12s0.
Sep 13 12:12:42 trogdor avahi-daemon[278]: Leaving mDNS multicast group on interface wlp12s0.IPv4 with address 192.168.1.5.
Sep 13 12:12:42 trogdor dhcpcd[283]: wlp12s0: deleting route to 192.168.1.0/24
Sep 13 12:12:42 trogdor kernel: wlp12s0: deauthenticating from bc:ae:c5:e6:05:64 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 13 12:12:42 trogdor kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp12s0: link becomes ready
Sep 13 12:12:42 trogdor kernel: cfg80211: Calling CRDA for country: DE
Sep 13 12:12:42 trogdor avahi-daemon[278]: Interface wlp12s0.IPv4 no longer relevant for mDNS.
Sep 13 12:12:42 trogdor dhcpcd[283]: wlp12s0: deleting default route via 192.168.1.1
Sep 13 12:12:42 trogdor NetworkManager[276]: <info> Removing DNS information from /usr/bin/resolvconf
Sep 13 12:12:42 trogdor dhcpcd[283]: wlp12s0: carrier lost
Sep 13 12:12:43 trogdor NetworkManager[276]: <info> NetworkManager state is now ASLEEP
Sep 13 12:12:43 trogdor kernel: IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
Sep 13 12:12:43 trogdor dbus[281]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 13 12:12:43 trogdor dbus[281]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 13 12:12:43 trogdor systemd-sleep[876]: Suspending system...
-- Reboot --
Sep 13 12:56:07 trogdor systemd-journal[124]: Runtime journal is using 8.0M (max allowed 100.3M, trying to leave 150.5M free of 995.9M available → current limit 100.3M).
Sep 13 12:56:07 trogdor systemd-journal[124]: Runtime journal is using 8.0M (max allowed 100.3M, trying to leave 150.5M free of 995.9M available → current limit 100.3M).
Sep 13 12:56:07 trogdor kernel: Initializing cgroup subsys cpuset
Sep 13 12:56:07 trogdor kernel: Initializing cgroup subsys cpu
Sep 13 12:56:07 trogdor kernel: Initializing cgroup subsys cpuacct
Sep 13 12:56:07 trogdor kernel: Linux version 3.16.2-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Sat Sep 6 13:13:35 CEST 2014
Sep 13 12:56:07 trogdor kernel: e820: BIOS-provided physical RAM map:
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f44d3ff] usable
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x000000007f44f400-0x000000007fffffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000fed18000-0x00000000fed1bfff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed8ffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000feda0000-0x00000000feda5fff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee0ffff] reserved
Sep 13 12:56:07 trogdor kernel: BIOS-e820: [mem 0x00000000ffe60000-0x00000000ffffffff] reserved
Sep 13 12:56:07 trogdor kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Sep 13 12:56:07 trogdor kernel: SMBIOS 2.4 present.
Sep 13 12:56:07 trogdor kernel: DMI: Dell Inc. Latitude E6500                  /0F327M, BIOS A27 12/06/2011

Because the journal isn't capturing anything during the problem itself, I am having trouble debugging what is causing this.

For what it's worth, my post yesterday was reporting the same problem with kernel 3.16.1.

The information that I am posting today was after an upgrade last night from 3.16.1 to 3.16.2. The problem, obviously, persists.

nostalgix · 2014-09-13 18:31:56

Thank you jdoggsc. Maybe somebody has an idea what to do to get our laptops running fine again. Meanwhile I downgrade to 3.15.7 again.

aurelieng · 2014-09-14 15:53:56

Hi all,

Since I'm not the only one affected by this bug, I create a bug report here.

nostalgix · 2014-09-14 19:30:09

Cool! Let's vote on it.

aurelieng · 2014-09-22 06:34:48

Fixed w/ 3.16.3-1

nostalgix · 2014-09-23 03:47:09

~~That would be nice. I will update later and give it a try. Right now I am already 115 packages behind, because of staying on the 3.15 kernel.~~
Updated my laptop and suspending - and waking up again! - works again. Great!

Last edited by nostalgix (2014-09-23 06:51:09)

aurelieng · 2014-09-23 08:33:59

Btw, you don't have to delay all package updates if you just want to stick with a specific version of the kernel, just add the the following to your /etc/pacman.conf's IgnorePkg :
* linux
* linux-headers

As well as packages that are linked to it, eg for me:
* nvidia
* nvidia-utils
* nvidia-libgl
* virtualbox
* virtualbox-host-modules

After that, pacman will just skip newer versions of these packages, but update others

Last edited by aurelieng (2014-09-23 08:36:05)

nostalgix · 2014-09-23 16:07:43

@aurelieng I know. But because of a newer gcc version which depends on 3.16.x lots of other things have been held back. Not all of course, but I was hoping for a quick fix, so I wanted to wait a bit more.

Arch Linux

#1 2014-09-12 05:03:39

[SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#2 2014-09-12 09:10:11

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#3 2014-09-12 21:06:43

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#4 2014-09-13 17:25:08

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#5 2014-09-13 18:31:56

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#6 2014-09-14 15:53:56

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#7 2014-09-14 19:30:09

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#8 2014-09-22 06:34:48

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#9 2014-09-23 03:47:09

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#10 2014-09-23 08:33:59

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

#11 2014-09-23 16:07:43

Re: [SOLVED] Kernel (3.16.x) crash while resuming from suspend to RAM

Board footer