System journal messages 20:34:13 kernel: OOM killer disabled. 20:34:13 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 20:34:13 kernel: printk: Suspending console(s) (use no_console_suspend to debug) 20:34:13 kernel: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x20 [usbcore] returns -16 20:34:13 kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16 20:34:13 kernel: xhci_hcd 0000:00:14.0: PM: failed to suspend async: error -16 20:34:13 kernel: e1000e 0000:00:1f.6 enp0s31f6: Could not acquire PHY 20:34:13 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:34:13 kernel: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -2 20:34:13 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:34:13 kernel: PM: Some devices failed to suspend, or early wake event detected 20:34:13 kernel: i915 0000:00:02.0: [drm] GuC firmware i915/kbl_guc_62.0.0.bin version 62.0 submission:disabled 20:34:13 kernel: i915 0000:00:02.0: [drm] GuC SLPC: disabled 20:34:13 kernel: i915 0000:00:02.0: [drm] HuC firmware i915/kbl_huc_4.0.0.bin version 4.0 authenticated:yes 20:34:13 kernel: nvme nvme0: Shutdown timeout set to 8 seconds 20:34:13 kernel: nvme nvme0: 4/0/0 default/read/poll queues 20:34:13 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4690] 20:34:13 kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..] 20:34:13 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops __SCT__tp_func_intel_frontbuffer_flush [i915]) 20:34:13 kernel: OOM killer enabled. 20:34:13 kernel: Restarting tasks ... done. Reproducible: Sometimes journalctl -b -4 | grep e1000e 15:58:43 kernel: e1000e: Intel(R) PRO/1000 Network Driver 15:58:43 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. 15:58:43 kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode 15:58:43 kernel: e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock 15:58:43 kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 54:ee:75:e0:28:d6 15:58:43 kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection 15:58:43 kernel: e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF 15:58:43 kernel: e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0 15:59:50 kernel: e1000e: EEE TX LPI TIMER: 00000011 15:59:51 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 16:03:17 kernel: e1000e: EEE TX LPI TIMER: 00000011 16:03:18 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 16:04:58 kernel: e1000e: EEE TX LPI TIMER: 00000011 16:04:59 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 16:20:52 kernel: e1000e: EEE TX LPI TIMER: 00000011 16:20:53 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 19:50:59 kernel: e1000e: EEE TX LPI TIMER: 00000011 19:51:00 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 19:52:11 kernel: e1000e: EEE TX LPI TIMER: 00000011 19:52:11 kernel: e1000e 0000:00:1f.6 enp0s31f6: Failed to disable ULP 19:52:11 kernel: e1000e 0000:00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet 19:52:11 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 19:52:12 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 19:52:12 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 19:52:13 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:34:13 kernel: e1000e 0000:00:1f.6 enp0s31f6: Could not acquire PHY 20:34:13 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:34:13 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:34:15 kernel: e1000e: EEE TX LPI TIMER: 00000011 20:34:15 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:34:15 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:34:16 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:34:17 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 20:34:18 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:34:55 kernel: e1000e: EEE TX LPI TIMER: 00000011 20:34:55 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:34:55 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:34:58 kernel: e1000e: EEE TX LPI TIMER: 00000011 20:34:58 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:34:58 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:34:59 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:35:00 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 20:35:01 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:52:15 kernel: e1000e: EEE TX LPI TIMER: 00000011 20:52:15 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:52:15 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:52:18 kernel: e1000e: EEE TX LPI TIMER: 00000011 20:52:18 kernel: PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0xe20 returns -2 20:52:18 kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 20:52:19 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error 20:52:20 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down 20:52:21 kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error
Why do you think this has anything to do with linux-headers?
(In reply to Mike Gilbert from comment #1) > Why do you think this has anything to do with linux-headers? Thanks for correction. This is kernel regression.
Waking up immediately only if bluetooth hid mouse connected. If mouse is disconnected sleep mode works.
Can you *attach* the output of emerge --info ? Which gentoo-sources is this?
Created attachment 772514 [details] emerge --info gentoo-sources
Created attachment 772547 [details] kernel .config
Created attachment 772550 [details] emerge --info gentoo-sources
Full dmesg attached please after boot
It really looks like a new regression. Can you do a git bisect between your last working kernel and the first non-working one ?
Created attachment 772667 [details] dmesg
(In reply to Михаил from comment #10) > Created attachment 772667 [details] > dmesg Thanks, can you test with Nouveau please? We don't support troubleshooting kernels with out of tree modules.
Created attachment 772757 [details] dmesg (In reply to Mike Pagano from comment #11) > Thanks, can you test with Nouveau please? I've remove out of tree modules and behaviour did not changes.
Created attachment 772760 [details] dmesg suspend fail with connected bluetooth mousee $ lsusb Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface $ lsmod btusb 49152 0 btintel 36864 1 btusb
(In reply to Mike Pagano from comment #9) > It really looks like a new regression. > > Can you do a git bisect between your last working kernel and the first > non-working one ? Did you have a chance to do a git bisect?
(In reply to Mike Pagano from comment #14) > Did you have a chance to do a git bisect? Did not have. I try 5.18 and will do bisect if issue is not gone.
any update on this?
Tnis looks like a usb problem. All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list
This problem look similar: https://lore.kernel.org/all/20200610064231.9454-2-kai.heng.feng@canonical.com/
Is the mouse your only bluetooth device? Can you test suspend without your bluetooth mouse connected?
This is being reported in the upstream bug as fixed in 5.18.16. Can you please test that version and let us know ?
People are reporting in the upstream bug that this issue does not appear in >= 5.19.2 . Can you test with the latest 5.19.X which is 5.19.3 as of this writing.
(In reply to Mike Pagano from comment #21) > People are reporting in the upstream bug that this issue does not appear in > >= 5.19.2 . > > Can you test with the latest 5.19.X which is 5.19.3 as of this writing. Issue is gone in 5.19.2 Suspend and wakeup without problem.
Awesome, thanks !
