Created attachment 213341 [details] # lsusb -vvv From times to times, when I try to suspend my system, it refuses to do so in the following way: as soon as the screen goes black, it resumes right away. It’s not always reproducible, but once it starts happening, it does 100% of the time until reboot. I don’t remember having this issue with 4.4 (neither do my logs, but don’t have them for more than one month, and while 4.5 came last week, 4.4 was here since early February). Looking at dmesg, I see this (one attempt, despite it looks to be two): [20177.454926] PM: Syncing filesystems ... done. [20178.638227] PM: Preparing system for sleep (mem) [20178.638553] bbswitch: enabling discrete graphics [20179.041282] usb 3-1: USB disconnect, device number 11 [20179.177760] Freezing user space processes ... (elapsed 0.001 seconds) done. [20179.179186] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. [20179.179926] PM: Suspending system (mem) [20179.179934] Suspending console(s) (use no_console_suspend to debug) [20179.180077] wlp6s0: deauthenticating from 00:24:b2:c5:7a:d4 by local choice (Reason: 3=DEAUTH_LEAVING) [20179.180176] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [20179.180183] sd 0:0:0:0: [sda] Synchronizing SCSI cache [20179.181593] sd 0:0:0:0: [sda] Stopping disk [20179.181593] sd 1:0:0:0: [sdb] Stopping disk [20179.353346] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 [20179.353350] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -16 [20179.353352] PM: Device 0000:00:14.0 failed to suspend async: error -16 [20179.746728] PM: Some devices failed to suspend, or early wake event detected [20179.749247] sd 0:0:0:0: [sda] Starting disk [20179.749260] sd 1:0:0:0: [sdb] Starting disk [20179.749286] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20179.749524] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20179.816719] rtc_cmos 00:01: System wakeup disabled by ACPI [20179.960320] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20179.960557] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20179.976453] PM: resume of devices complete after 229.715 msecs [20179.976675] PM: Finishing wakeup. [20179.976676] Restarting tasks ... done. [20180.680097] PM: Syncing filesystems ... [20181.181446] psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4646] [20181.275798] psmouse serio1: synaptics: queried min coordinates: x [1386..], y [1252..] [20181.881736] done. [20181.881740] PM: Preparing system for sleep (freeze) [20181.881890] bbswitch: enabling discrete graphics [20182.420776] Freezing user space processes ... (elapsed 0.001 seconds) done. [20182.422215] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [20182.423339] PM: Suspending system (freeze) [20182.423341] Suspending console(s) (use no_console_suspend to debug) [20182.423605] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [20182.423618] sd 0:0:0:0: [sda] Synchronizing SCSI cache [20182.423712] sd 0:0:0:0: [sda] Stopping disk [20182.424748] sd 1:0:0:0: [sdb] Stopping disk [20182.543457] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 [20182.543461] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -16 [20182.543462] PM: Device 0000:00:14.0 failed to suspend async: error -16 [20182.988158] PM: Some devices failed to suspend, or early wake event detected [20182.989179] sd 0:0:0:0: [sda] Starting disk [20182.989198] sd 1:0:0:0: [sdb] Starting disk [20182.989213] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20182.989450] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20183.056822] rtc_cmos 00:01: System wakeup disabled by ACPI [20183.196258] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20183.196495] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [20184.032398] PM: resume of devices complete after 1044.203 msecs [20184.032575] PM: Finishing wakeup. [20184.032576] Restarting tasks ... done. [20184.033519] wlp6s0: authenticate with 00:24:b2:c5:7a:d4 [20184.035353] wlp6s0: send auth to 00:24:b2:c5:7a:d4 (try 1/3) [20184.037122] wlp6s0: authenticated [20184.040069] wlp6s0: associate with 00:24:b2:c5:7a:d4 (try 1/3) [20184.042688] wlp6s0: RX AssocResp from 00:24:b2:c5:7a:d4 (capab=0x431 status=0 aid=3) [20184.043745] wlp6s0: associated [20185.350722] psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4646] [20185.442899] psmouse serio1: synaptics: queried min coordinates: x [1386..], y [1252..] Especially, these four lines: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -16 PM: Device 0000:00:14.0 failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected More information about the incriminated 0000:00:14.0 device (but probably not very interesting): # lspci -vvv -s 00:14.0 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI]) Subsystem: Dell Device 05fe Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 32 Region 0: Memory at f7a00000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Address: 00000000fee00338 Data: 0000 Kernel driver in use: xhci_hcd Kernel modules: xhci_pci And I’ve attached the lsusb output. Please tell me if you need anything else, or if there is something I should try. This bug is really annoying, not being able to suspend obliges me to shutdown when moving from work to home, thus closing everything I was working on.
Also, on a side note, when suspend works, I’ve got this in my log when resuming: pciehp 0000:00:1c.0:pcie04: link training error: status 0x1001 pciehp 0000:00:1c.0:pcie04: Failed to check link status I’m not sure whether this is worth a bug report, so I’m just letting that here in case you have any opinion on this.
First of all, the suspend failure is indeed caused by the USB failure as you pointed out pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -16 PM: Device 0000:00:14.0 failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected Reassign to our USB expert. For the other problem in comment #1, I'm not sure what the problem is, if you want to raise it, please report to the PCI component. Let's focus on the suspend failure in this bug report.
I will report the other problem separately, thanks. I thought that I should let you know I had a BIOS upgrade last week, with the following changelog: Fixes - Fixed System hang up after Touch Touchpad - Fixed USB Test Fail Enhancements -Update Flash Utility -Update SMBIOS type0 format for Win10 BIOS Requirement I’m not sure this is correlated (that’s why I don’t like non 100%-reproducible bugs), but I’ve never faced this issue again since. Maybe I should wait for something like a month, and then decide that it was a BIOS issue if it has still not happened again by then?
so is there any other problem after upgrading BIOS? If no, I think we can mark this bug as closed.
No indeed, I thank that was it. If it ever happens again, I’ll reopen. Thanks! P.S.: I’ll let you close, not sure what closing reason to choose.
Problem can not be reproduced after BIOS upgrade.
Bad news, happened again right now: [32367.871308] pci_bus 0000:04: Allocating resources [32367.871344] pci_bus 0000:06: Allocating resources [32367.871397] pci_bus 0000:07: Allocating resources [32367.871501] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.871966] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.942052] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.942243] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.942353] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.942874] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.942910] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.943186] pci_bus 0000:02: Allocating resources [32367.943204] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.943316] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32367.943517] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32369.235016] PM: Syncing filesystems ... done. [32370.067432] PM: Preparing system for sleep (mem) [32370.670030] Freezing user space processes ... (elapsed 0.002 seconds) done. [32370.672103] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [32370.673463] PM: Suspending system (mem) [32370.673488] Suspending console(s) (use no_console_suspend to debug) [32370.674199] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [32370.674212] sd 0:0:0:0: [sda] Synchronizing SCSI cache [32370.674378] sd 0:0:0:0: [sda] Stopping disk [32370.675735] sd 1:0:0:0: [sdb] Stopping disk [32370.779002] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 [32370.779012] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 [32370.779016] PM: Device 0000:00:14.0 failed to suspend async: error -16 [32371.239097] PM: Some devices failed to suspend, or early wake event detected [32371.245591] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32371.245606] sd 0:0:0:0: [sda] Starting disk [32371.245631] sd 1:0:0:0: [sdb] Starting disk [32371.245849] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32371.309041] rtc_cmos 00:01: System wakeup disabled by ACPI [32371.455628] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32371.455879] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32373.252168] psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4646] [32373.305845] psmouse serio1: synaptics: queried min coordinates: x [1386..], y [1252..] [32373.842598] pciehp 0000:00:1c.0:pcie04: link training error: status 0x1001 [32373.842601] pciehp 0000:00:1c.0:pcie04: Failed to check link status [32373.842699] PM: resume of devices complete after 2603.180 msecs [32373.843265] PM: Finishing wakeup. [32373.843267] Restarting tasks ... done. [32374.552738] PM: Syncing filesystems ... done. [32375.509783] PM: Preparing system for sleep (freeze) [32375.509946] bbswitch: enabling discrete graphics [32376.051812] Freezing user space processes ... (elapsed 0.001 seconds) done. [32376.053399] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [32376.054571] PM: Suspending system (freeze) [32376.054573] Suspending console(s) (use no_console_suspend to debug) [32376.054848] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [32376.054862] sd 0:0:0:0: [sda] Synchronizing SCSI cache [32376.056169] sd 0:0:0:0: [sda] Stopping disk [32376.058606] sd 1:0:0:0: [sdb] Stopping disk [32376.146361] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 [32376.146365] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 [32376.146366] PM: Device 0000:00:14.0 failed to suspend async: error -16 [32376.620737] PM: Some devices failed to suspend, or early wake event detected [32376.621603] sd 0:0:0:0: [sda] Starting disk [32376.621634] sd 1:0:0:0: [sdb] Starting disk [32376.621639] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32376.621876] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32376.689779] rtc_cmos 00:01: System wakeup disabled by ACPI [32376.829370] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32376.829608] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [32378.650988] psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4646] [32378.704360] psmouse serio1: synaptics: queried min coordinates: x [1386..], y [1252..] [32379.223406] pciehp 0000:00:1c.0:pcie04: link training error: status 0x1001 [32379.223408] pciehp 0000:00:1c.0:pcie04: Failed to check link status [32379.223422] PM: resume of devices complete after 2602.259 msecs [32379.223605] PM: Finishing wakeup. [32379.223606] Restarting tasks ... done. [32407.889638] pci_bus 0000:04: Allocating resources [32407.889675] pci_bus 0000:06: Allocating resources [32407.889732] pci_bus 0000:07: Allocating resources [32407.889834] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.890436] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.961693] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.961880] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.961988] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.962517] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.962552] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.962825] pci_bus 0000:02: Allocating resources [32407.962843] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.962954] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [32407.963162] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment So, it wasn’t BIOS update, just luck for all that time during. PCIe and i915 error message are already reported (i915 is linked to closing/opening panel display independently of suspend/resume, PCIe is also suspend/resume but ever happened since 3.14, so not linked).
Hi, Baolu, can you help look at this issue please? The USB suspend failure breaks system suspend.
Happened again today, so that’s twice in a row… Thought I should share some early dmesg info just in case: [ 0.373371] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330 [ 0.373389] pci 0000:00:14.0: reg 0x10: [mem 0xf7a00000-0xf7a0ffff 64bit] [ 0.373449] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.373487] pci 0000:00:14.0: System wakeup disabled by ACPI [ 2.262778] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 2.262784] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 [ 2.263875] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810 [ 2.263880] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported [ 2.266626] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 2.266629] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Happened again tonight on 4.6.2. Didn’t realized it until this morning, when I’ve found my laptop dead because he had run out of battery…
[32376.146361] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 [32376.146365] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 [32376.146366] PM: Device 0000:00:14.0 failed to suspend async: error -16 [32376.620737] PM: Some devices failed to suspend, or early wake event detected Hi, Baolu, can you please help take a look at this USB issue?
hcd_pci_suspend() returns -EBUSY. That probably means a wakeup event is pending when trying to suspend host. It causes the usb host to wake up as the result.
I’m currently facing this. I’ll not reboot for now in case you would like me to test or report things while in this situation.
Some news: I’ve tried suspending it again, it almost worked (the power led went off, which doesn’t happen when facing the above issue), but eventually resumed. Also, note that it didn’t do twice suspend/resume cycle like it did like above, but only one. And the dmesg contains nothing about usb: [382483.225378] PM: Syncing filesystems ... done. [382484.159512] PM: Preparing system for sleep (mem) [382484.159855] bbswitch: enabling discrete graphics [382484.701275] Freezing user space processes ... (elapsed 0.001 seconds) done. [382484.703186] Freezing remaining freezable tasks ... (elapsed 0.023 seconds) done. [382484.726284] PM: Suspending system (mem) [382484.726295] Suspending console(s) (use no_console_suspend to debug) [382484.726475] wlp6s0: deauthenticating from c0:ee:fb:42:fe:78 by local choice (Reason: 3=DEAUTH_LEAVING) [382484.726577] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [382484.726581] sd 0:0:0:0: [sda] Synchronizing SCSI cache [382484.726680] sd 0:0:0:0: [sda] Stopping disk [382484.729504] sd 1:0:0:0: [sdb] Stopping disk [382485.291419] PM: suspend of devices complete after 565.034 msecs [382485.312596] PM: late suspend of devices complete after 21.166 msecs [382485.313158] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI [382485.313317] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI [382485.313328] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI [382485.325922] PM: noirq suspend of devices complete after 13.325 msecs [382485.326161] ACPI: Preparing to enter system sleep state S3 [382485.326458] ACPI : EC: EC stopped [382485.326458] PM: Saving platform NVS memory [382485.326488] Disabling non-boot CPUs ... [382485.360294] smpboot: CPU 1 is now offline [382485.380284] smpboot: CPU 2 is now offline [382485.400286] smpboot: CPU 3 is now offline [382485.427186] smpboot: CPU 4 is now offline [382485.446922] smpboot: CPU 5 is now offline [382485.466987] smpboot: CPU 6 is now offline [382485.486980] smpboot: CPU 7 is now offline [382485.489053] ACPI: Low-level resume complete [382485.489099] ACPI : EC: EC started [382485.489100] PM: Restoring platform NVS memory [382485.491871] Enabling non-boot CPUs ... [382485.491917] x86: Booting SMP configuration: [382485.491918] smpboot: Booting Node 0 Processor 1 APIC 0x2 [382485.495926] cache: parent cpu1 should not be sleeping [382485.496113] CPU1 is up [382485.496136] smpboot: Booting Node 0 Processor 2 APIC 0x4 [382485.500163] cache: parent cpu2 should not be sleeping [382485.500347] CPU2 is up [382485.500369] smpboot: Booting Node 0 Processor 3 APIC 0x6 [382485.504421] cache: parent cpu3 should not be sleeping [382485.504615] CPU3 is up [382485.504638] smpboot: Booting Node 0 Processor 4 APIC 0x1 [382485.507311] cache: parent cpu4 should not be sleeping [382485.507443] CPU4 is up [382485.507464] smpboot: Booting Node 0 Processor 5 APIC 0x3 [382485.510072] cache: parent cpu5 should not be sleeping [382485.510201] CPU5 is up [382485.510219] smpboot: Booting Node 0 Processor 6 APIC 0x5 [382485.512842] cache: parent cpu6 should not be sleeping [382485.512980] CPU6 is up [382485.512997] smpboot: Booting Node 0 Processor 7 APIC 0x7 [382485.515634] cache: parent cpu7 should not be sleeping [382485.515770] CPU7 is up [382485.523818] ACPI: Waking up from system sleep state S3 [382485.524485] acpi LNXPOWER:01: Turning OFF [382485.527984] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI [382485.528006] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI [382485.528011] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI [382485.538215] PM: noirq resume of devices complete after 13.722 msecs [382485.544560] PM: early resume of devices complete after 6.327 msecs [382485.544995] sd 0:0:0:0: [sda] Starting disk [382485.545052] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [382485.545156] sd 1:0:0:0: [sdb] Starting disk [382485.545295] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [382485.617948] rtc_cmos 00:01: System wakeup disabled by ACPI [382485.761886] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [382485.762126] iwlwifi 0000:06:00.0: L1 Disabled - LTR Enabled [382485.807955] usb 3-9: reset full-speed USB device number 3 using xhci_hcd [382485.861202] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [382485.862292] ata2.00: configured for UDMA/100 [382486.141338] usb 3-6: reset full-speed USB device number 2 using xhci_hcd [382486.474648] usb 3-11: reset high-speed USB device number 4 using xhci_hcd [382487.094667] psmouse serio1: synaptics: queried max coordinates: x [..5660], y [..4646] [382487.152911] psmouse serio1: synaptics: queried min coordinates: x [1386..], y [1252..] [382487.994270] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [382488.102933] ata1.00: configured for UDMA/133 [382488.147605] pciehp 0000:00:1c.0:pcie04: link training error: status 0x1001 [382488.147607] pciehp 0000:00:1c.0:pcie04: Failed to check link status [382488.147650] PM: resume of devices complete after 2603.359 msecs [382488.147944] PM: Finishing wakeup. [382488.147945] Restarting tasks ... done. [382489.237475] bbswitch: disabling discrete graphics [382489.237485] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95) [382490.927888] wlp6s0: authenticate with c0:ee:fb:42:fe:78 [382490.930621] wlp6s0: send auth to c0:ee:fb:42:fe:78 (try 1/3) [382490.949568] wlp6s0: authenticated [382490.950604] wlp6s0: associate with c0:ee:fb:42:fe:78 (try 1/3) [382490.971160] wlp6s0: RX AssocResp from c0:ee:fb:42:fe:78 (capab=0x431 status=0 aid=2) [382490.972570] wlp6s0: associated (Yes, I’m still on the same boot, as the timestamp shows) At the moment, further attempts results in the same effect. So they might be two issues in one actually.
please attach the output of "cat /proc/wakeup"
No such file, but I have /proc/acpi/wakeup: Device S-state Status Sysfs node RP01 S4 *disabled pci:0000:00:1c.0 PXSX S4 *disabled RP02 S4 *disabled PXSX S4 *disabled RP03 S4 *disabled pci:0000:00:1c.2 PXSX S4 *disabled pci:0000:06:00.0 RP04 S4 *disabled pci:0000:00:1c.3 PXSX S4 *disabled pci:0000:07:00.0 *disabled platform:rtsx_pci_sdmmc.0 *disabled platform:rtsx_pci_ms.0 RP05 S4 *disabled PXSX S4 *disabled RP06 S4 *disabled PXSX S4 *disabled RP07 S4 *disabled PXSX S4 *disabled RP08 S4 *disabled PXSX S4 *disabled GLAN S4 *disabled EHC1 S0 *enabled pci:0000:00:1d.0 EHC2 S4 *enabled pci:0000:00:1a.0 XHC S0 *enabled pci:0000:00:14.0 HDEF S4 *disabled pci:0000:00:1b.0 PEG0 S4 *disabled pci:0000:00:01.0 PEGP S4 *disabled pci:0000:02:00.0 PEGA S4 *disabled PEG1 S4 *disabled PEG2 S4 *disabled PWRB S4 *enabled platform:PNP0C0C:00 LID0 S4 *enabled platform:PNP0C0D:00 Is that what you want?
yep, please check if you can reproduce the problem if you disable all the items in /proc/acpi/wakeup. say, we can see that EHC1 is enabled, and we can disable it by running "echo EHC1 > /proc/acpi/wakeup"
OK. So, I didn’t touch to PWRB and LID0, because I was afraid not being able to recover from sleep if doing so (I suspect those to be the PoWeR Button and LID open action), but anyway here is the result: as soon as EHC2 si disabled, whatever the state of ECH1 or XHC is, suspend does work!
New update: today, I’ve tried to logout/login to reset my session, because after more than 9 days of uptime, some things started to be instable. Thing is, I wasn’t able to logout (it just stayed doing nothing, and I could still open apps). I eventually killed the X server, but after logging back in, I had the idea to try suspend with EHC2 enabled. And it worked. So… I’m going to reboot now since it’s currently not in that problematic situation anymore, but please tell what you would like me to test next time it happens.
Still happening from time to time. The problem is that I don’t always see that it’s happening, especially when I close my laptop to put it in my backpack, causing to issue: heat (because close to no dissipation when in the bag, especially since Dell put the air grid at the lid basis, so it’s actually covered when the laptop is closed), and potentially dying out of battery (meaning loosing current session and opened apps/docs).
Turns out that EHC2 is not always the culprit — it happened again y-day, but with XHC being guilty this time. Still no-one here with ideas on what information could be useful for debugging?
Hey, I’ve just stumbled upon this on the ArchWiki: https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate#Instantaneous_wakeups_from_suspend That’s exactly this bug. It links to https://bugzilla.kernel.org/show_bug.cgi?id=66171#c6. And there’s a thread here: https://bbs.archlinux.org/viewtopic.php?pid=1575617. Maybe this will help you fix this more permanently/without relying on users to modify their systems by themselves.
Above message is spam just reusing some words from me and adding a link to an external website. Also, FWIW, 8 years have passed and I don’t have this laptop anymore, so…