Open psii opened 3 years ago
$ sudo dmesg |grep 0000:02:00.0
[ 0.446459] pci 0000:02:00.0: [14e4:43ba] type 00 class 0x028000
[ 0.446483] pci 0000:02:00.0: reg 0x10: [mem 0xdd800000-0xdd807fff 64bit]
[ 0.446499] pci 0000:02:00.0: reg 0x18: [mem 0xdd400000-0xdd7fffff 64bit]
[ 0.446629] pci 0000:02:00.0: supports D1 D2
[ 0.446631] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.892824] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.Dell Inc.-XPS 15 9550.txt failed with error -2
[ 4.893557] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
[ 5.405859] brcmfmac 0000:02:00.0 wlp2s0: renamed from wlan0
[22048.412717] brcmfmac 0000:02:00.0: brcmf_pcie_pm_enter_D3: Timeout on response for entering D3 substate
[22048.412820] PM: Device 0000:02:00.0 failed to suspend async: error -5
[22056.316639] brcmfmac 0000:02:00.0: brcmf_pcie_pm_enter_D3: Timeout on response for entering D3 substate
[22056.316713] PM: Device 0000:02:00.0 failed to suspend async: error -5
Hey @psii mind giving us one more test and letting us know the results.
Install fwts
via apt and then run
sudo fwts s3
It takes a little time to run the test but it will give you a success or failure for the tests as it runs them.
Sure!
Results generated by fwts: Version V20.09.00 (2020-09-17 18:08:13).
Some of this work - Copyright (c) 1999 - 2020, Intel Corp. All rights reserved.
Some of this work - Copyright (c) 2010 - 2020, Canonical.
Some of this work - Copyright (c) 2016 - 2020, IBM.
Some of this work - Copyright (c) 2017 - 2020, ARM Ltd.
This test run on 06/04/21 at 20:43:58 on host Linux pop-os 5.11.0-7612-generic
#13~1617215757~20.10~97a8d1a-Ubuntu SMP Thu Apr 1 21:09:17 UTC 2 x86_64.
Command: "fwts s3".
Running tests: s3.
s3: Sleep suspend/resume test.
--------------------------------------------------------------------------------
Test 1 of 1: Sleep suspend/resume test.
Defaulted to 1 test, use --s3-multiple=N to run more S3 cycles
S3 cycle 1 of 1
Detecting the power method.
Response to CanSuspend is yes
User allowed to execute the CanSuspend action
Using logind as the default power method.
Requesting Suspend action
Skipping the minimum delay (0) and using a 3 seconds delay instead
S3 duration = 17.
pm-action returned 0 after 17 seconds.
FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 17 seconds, less
than the expected 30 seconds.
FAILED [CRITICAL] PmDevicesFailedToSuspend: Test 1, CRITICAL Kernel message:
[99174.870657] PM: Some devices failed to suspend, or early wake event detected
Message repeated 1 times.
ADVICE: This is a bug picked up by the kernel, but as yet, the firmware test
suite has no diagnostic advice for this particular problem.
Suspend/Resume Timings:
Could not determine time to suspend.
Could not determine time to resume.
Completed S3 cycle(s)
Found 1 errors in kernel log.
Found 1 PM related suspend issues.
PASSED: Test 1, No device errors detected.
PASSED: Test 1, No kernel oopses detected.
PASSED: Test 1, No kernel WARN_ON warnings detected.
PASSED: Test 1, No s2idle errors detected.
Found 2 errors and 0 oopses doing 1 suspend/resume cycle(s).
PASSED: Test 1, All suspends took less than 15.00 seconds.
PASSED: Test 1, All resumes took less than 15.00 seconds.
================================================================================
6 passed, 2 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
================================================================================
6 passed, 2 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.
Test Failure Summary
================================================================================
Critical failures: 1
s3: CRITICAL Kernel message: [99174.870657] PM: Some devices failed to suspend, or early wake event detected
High failures: NONE
Medium failures: 1
s3: Unexpected: S3 slept for 17 seconds, less than the expected 30 seconds.
Low failures: NONE
Other failures: NONE
Test |Pass |Fail |Abort|Warn |Skip |Info |
---------------+-----+-----+-----+-----+-----+-----+
s3 | 6| 2| | | | |
---------------+-----+-----+-----+-----+-----+-----+
Total: | 6| 2| 0| 0| 0| 0|
---------------+-----+-----+-----+-----+-----+-----+
Distribution (run
cat /etc/os-release
):Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):Issue/Bug Description: After the recent upgrade of the linux kernel from 5.8 to 5.11, suspend does not work anymore. When booting into the previous 5.8 kernel, suspend works as expected.
Steps to reproduce (if you know): N/A
Expected behavior: Closing the lid, or selecting "Suspend" should suspend the notebook.
Other Notes:
dmesg
outputs the following: