You are not logged in.
I know I can submit a bug in https://bugs.archlinux.org/, but wanted to touch base here first.
I've found a reproducible system crash related to suspending the system. I was having issues with my laptop (HP Envy 17t) suspending and then freezing upon waking up. Went through the logs and found this:
Mar 26 12:36:09 xxx kernel: ACPI: Waking up from system sleep state S3
Mar 26 12:36:09 xxx kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
Mar 26 12:36:09 xxx kernel: PM: noirq resume of devices complete after 13.503 msecs
Mar 26 12:36:09 xxx kernel: PM: early resume of devices complete after 5.760 msecs
Mar 26 12:36:09 xxx kernel: r8169 0000:07:00.0: System wakeup disabled by ACPI
Mar 26 12:36:09 xxx kernel: sd 1:0:0:0: [sda] Starting disk
Mar 26 12:36:09 xxx kernel: xhci_hcd 0000:00:14.0: port 8 resume PLC timeout
Mar 26 12:36:09 xxx kernel: xhci_hcd 0000:00:14.0: port 6 resume PLC timeout
Mar 26 12:36:09 xxx kernel: ------------[ cut here ]------------
Mar 26 12:36:09 xxx kernel: WARNING: CPU: 0 PID: 751 at drivers/misc/lis3lv02d/lis3lv02d.c:238 lis3lv02d_get_pwron_wait+0xa0/0xc0 [lis3lv02d]()
Mar 26 12:36:09 xxx kernel: device returned spurious data
Mar 26 12:36:09 xxx kernel: Modules linked in: bbswitch(O) nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 uvcvideo intel_rapl videobuf2
Mar 26 12:36:09 xxx kernel: video ac intel_lpss soundcore drm intel_gtt i2c_hid btintel thermal shpchp hid bluetooth rfkill fjes mei syscopyarea sysfillrect sysimgblt fb_sys_fops button i2
Mar 26 12:36:09 xxx kernel: CPU: 0 PID: 751 Comm: systemd-sleep Tainted: G O 4.4.5-1-ARCH #1
Mar 26 12:36:09 xxx kernel: Hardware name: HP HP ENVY Notebook/80EE, BIOS F.31 12/17/2015
Mar 26 12:36:09 xxx kernel: 0000000000000286 000000007cb3d74a ffff88042f53fb28 ffffffff812cb391
Mar 26 12:36:09 xxx kernel: ffff88042f53fb70 ffffffffa015c1c8 ffff88042f53fb60 ffffffff810776e2
Mar 26 12:36:09 xxx kernel: ffffffffa015d160 0000000000000010 ffffffffa0241070 0000000000000010
Mar 26 12:36:09 xxx kernel: Call Trace:
Mar 26 12:36:09 xxx kernel: [<ffffffff812cb391>] dump_stack+0x63/0x82
Mar 26 12:36:09 xxx kernel: [<ffffffff810776e2>] warn_slowpath_common+0x82/0xc0
Mar 26 12:36:09 xxx kernel: [<ffffffffa0241070>] ? lis3lv02d_get_resource+0x20/0x20 [hp_accel]
Mar 26 12:36:09 xxx kernel: [<ffffffff8107777c>] warn_slowpath_fmt+0x5c/0x80
Mar 26 12:36:09 xxx kernel: [<ffffffff81370430>] ? acpi_evaluate_object+0x280/0x2a6
Mar 26 12:36:09 xxx kernel: [<ffffffffa015a470>] lis3lv02d_get_pwron_wait+0xa0/0xc0 [lis3lv02d]
Mar 26 12:36:09 xxx kernel: [<ffffffffa015a504>] lis3lv02d_poweron+0x74/0x110 [lis3lv02d]
Mar 26 12:36:09 xxx kernel: [<ffffffffa0241085>] lis3lv02d_resume+0x15/0x20 [hp_accel]
Mar 26 12:36:09 xxx kernel: [<ffffffff813fb470>] dpm_run_callback+0x50/0x170
Mar 26 12:36:09 xxx kernel: [<ffffffff813fba43>] device_resume+0xd3/0x1f0
Mar 26 12:36:09 xxx kernel: [<ffffffff813fd0a8>] dpm_resume+0xf8/0x300
Mar 26 12:36:09 xxx kernel: [<ffffffff813fd6c1>] dpm_resume_end+0x11/0x20
Mar 26 12:36:09 xxx kernel: [<ffffffff810c35f5>] suspend_devices_and_enter+0x175/0x860
Mar 26 12:36:09 xxx kernel: [<ffffffff810c40de>] pm_suspend+0x3fe/0x580
Mar 26 12:36:09 xxx kernel: [<ffffffff810c283a>] state_store+0x8a/0x90
Mar 26 12:36:09 xxx kernel: [<ffffffff812cd50f>] kobj_attr_store+0xf/0x20
Mar 26 12:36:09 xxx kernel: [<ffffffff8125c547>] sysfs_kf_write+0x37/0x40
Mar 26 12:36:09 xxx kernel: [<ffffffff8125bb0a>] kernfs_fop_write+0x11a/0x170
Mar 26 12:36:09 xxx kernel: [<ffffffff811e0ca7>] __vfs_write+0x37/0x100
Mar 26 12:36:09 xxx kernel: [<ffffffff811e15b7>] vfs_write+0xa7/0x1a0
Mar 26 12:36:09 xxx kernel: [<ffffffff811e2295>] SyS_write+0x55/0xc0
Mar 26 12:36:09 xxx kernel: [<ffffffff815970ee>] entry_SYSCALL_64_fastpath+0x12/0x6d
Mar 26 12:36:09 xxx kernel: ---[ end trace 731734ce182d6fff ]---
Mar 26 12:36:09 xxx kernel: rtc_cmos 00:04: System wakeup disabled by ACPI
Mar 26 12:36:09 xxx kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Mar 26 12:36:09 xxx kernel: ata1: SATA link down (SStatus 4 SControl 300)
Mar 26 12:36:09 xxx kernel: ata3.00: configured for UDMA/133
Mar 26 12:36:09 xxx kernel: usb 1-9: reset full-speed USB device number 3 using xhci_hcd
Mar 26 12:36:09 xxx kernel: ata4: SATA link down (SStatus 4 SControl 300)
Mar 26 12:36:09 xxx kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Mar 26 12:36:09 xxx kernel: usb 1-7: reset full-speed USB device number 2 using xhci_hcd
Mar 26 12:36:09 xxx kernel: psmouse serio1: synaptics: queried max coordinates: x [..5636], y [..4634]
Mar 26 12:36:09 xxx kernel: psmouse serio1: synaptics: queried min coordinates: x [1360..], y [1298..]
Mar 26 12:36:09 xxx kernel: PM: resume of devices complete after 1269.735 msecs
Mar 26 12:36:09 xxx kernel: PM: Finishing wakeup.You can notice the tracecall informs that the live CPU0 has returned spurious data when attempting to wake the system up. This happened every time I close my laptop, wait for it to suspend, the wake it up. Crash, need to reboot.
I solved the issue by adding
PMMethod=bbswitchto /etc/bumblebee/bumblebee.conf. and after rebooting the machine wakes up properly.
HOWEVER: If I modify any of the power management settings (anything from increasing screen brightness to modifying deeper parameters under system setting), and then close my laptop, wait, and wake it up, it crashes again and have to reboot. If I DON'T move any of these settings, everything wakes up nicely as it should.
Anyone else seen this?
EDIT: Tried removing bumblebee, primus, bbswitch or nvidia to see if problem was related but persists. The weird thing is that when I remove / reinstall these packages the computer wakes up after suspend fine. If I change ANYTHING (I tried changing system fonts, changing volume, even starting wifi) the laptop will crash again upon suspension/waking up, and this behavior will persist after rebooting, until I reinstall/remove these packages.
Last edited by honeyplease (2016-03-26 17:50:32)
Offline