Bug 1781566
| Summary: | Cannot successfully suspend, machine starts again after a few seconds | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andre Klapper <a9016009> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | airlied, bcotton, bskeggs, btm.mosti, hdegoede, ichavero, itamar, jan, jan.kratochvil, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, joyeuxnye, kernel-maint, linville, masami256, mchehab, mjg59, steved, tbrisker |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-25 17:00:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Andre Klapper
2019-12-10 09:35:23 UTC
Still happening sometimes with `kernel-5.4.13-201.fc31.x86_64` Looking at the logs your system is using S3 suspend, which is mostly handled in firmware so this is somewhat surprising. When this happens the next time, can you do: cat /sys/power/pm_wakeup_irq And write down the output? This may give "No data available" as I'm not sure this debug method works with S3 suspend (most modern systems use a new suspend mode called suspend-to-idle aka s2idle). Assuming this gives useful data please also run: cat /proc/interrupts And copy and paste the output of both commands here, then we will see from there. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those. > Flags: needinfo?(a9016009)
No idea, that was already two months ago and I usually only suspend a lot when I'm at conferences / travelling which is both not very popular these days.
(In reply to Hans de Goede from comment #2) > cat /sys/power/pm_wakeup_irq > > And write down the output? This may give "No data available" Exactly: $:acko\> cat /sys/power/pm_wakeup_irq cat: /sys/power/pm_wakeup_irq: No data available $:acko\> cat /sys/power/mem_sleep s2idle [deep] And still happening in 33! Yay!
$:acko\> cat /sys/power/pm_wakeup_irq
cat: /sys/power/pm_wakeup_irq: No data available
$:acko\> cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 8 0 0 0 IO-APIC 2-edge timer
1: 31815 0 0 0 IO-APIC 1-edge i8042
8: 0 1 0 0 IO-APIC 8-edge rtc0
9: 813 4208 0 0 IO-APIC 9-fasteoi acpi
12: 5 0 0 716 IO-APIC 12-edge i8042
18: 28214 695814 0 0 IO-APIC 18-fasteoi i801_smbus
23: 46 43 0 0 IO-APIC 23-fasteoi ehci_hcd:usb1
42: 255794 0 0 0 PCI-MSI 512000-edge ahci[0000:00:1f.2]
43: 568 0 582 0 PCI-MSI 327680-edge xhci_hcd
44: 4 0 6 0 PCI-MSI 1048576-edge rtsx_pci
45: 0 36 0 0 PCI-MSI 360448-edge mei_me
46: 1624382 0 0 0 PCI-MSI 32768-edge i915
47: 0 110 0 0 PCI-MSI 442368-edge snd_hda_intel:card1
48: 0 0 0 0 PCI-MSI 49152-edge snd_hda_intel:card0
49: 0 0 0 50 PCI-MSI 409600-edge enp0s25
50: 5468 481983 0 0 PCI-MSI 1572864-edge iwlwifi
51: 7035 174040 0 0 dummy 44 rmi4_smbus
52: 0 0 0 0 rmi4 0 rmi4-00.fn34
53: 0 0 0 0 rmi4 1 rmi4-00.fn01
54: 0 0 322 0 rmi4 2 rmi4-00.fn03
55: 0 0 180045 0 rmi4 3 rmi4-00.fn11
56: 0 0 0 0 rmi4 4 rmi4-00.fn11
57: 0 0 1204 0 rmi4 6 rmi4-00.fn30
NMI: 123 119 125 119 Non-maskable interrupts
LOC: 4306237 3655404 3676302 3440942 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 123 119 125 119 Performance monitoring interrupts
IWI: 492272 75 71 78 IRQ work interrupts
RTR: 2 0 0 0 APIC ICR read retries
RES: 420323 363821 525824 380391 Rescheduling interrupts
CAL: 1098769 1177251 991490 1140869 Function call interrupts
TLB: 678628 631950 662485 625867 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 32 32 32 32 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 Posted-interrupt wakeup event
For the records, this is a Lenovo Thinkpad T450s (which I'd expect not to be that uncommon). Hans: Hi, any further info wanted / needed here? TIA. (In reply to Andre Klapper from comment #10) > Hans: Hi, any further info wanted / needed here? TIA. Since you get: $:acko\> cat /sys/power/pm_wakeup_irq cat: /sys/power/pm_wakeup_irq: No data available This really appears to be a firmware issue and there is not much which we can do. You could try switching to using s2idle by doing: echo s2idle > /sys/power/mem_sleep (I think, if that does not work, try a websearch on how to enable s2idle) Note on most modern hardware Linux will default to s2idle, so this is pretty well tested by now. For the records, most of the time suspend works fine and as expected. It only breaks sometimes, unpredictably. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Still happening with:
kernel-5.14.15-200.fc34.x86_64
Manufacturer: LENOVO
Product Name: 20TD002MCK
I cannot change the Fedora version 33->34.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. How to change the version field if folks don't have permissions to change the version field? Let me know what version it can be reproduced on and I'll update and reopen. Still an issue in F36 on a Lenovo Thinkpad X1, using `kernel-5.17.1-300.fc36.x86_64` [ak@ac ~]$ rpm -q kernel
kernel-5.17.0-300.fc36.x86_64
kernel-5.17.1-300.fc36.x86_64
[ak@ac ~]$ cat /sys/power/pm_wakeup_irq
9
[ak@ac ~]$ cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
1: 0 0 0 0 0 0 2897 0 IR-IO-APIC 1-edge i8042
8: 0 0 0 0 0 0 0 0 IR-IO-APIC 8-edge rtc0
9: 0 29697 0 0 0 0 0 0 IR-IO-APIC 9-fasteoi acpi
12: 0 0 0 0 0 721 0 0 IR-IO-APIC 12-edge i8042
14: 17624 0 0 0 0 0 0 0 IR-IO-APIC 14-fasteoi INT34BB:00
16: 0 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi i2c_designware.0, idma64.0, i801_smbus
17: 0 0 627709 0 0 0 0 0 IR-IO-APIC 17-fasteoi i2c_designware.1, idma64.1
120: 0 0 0 0 0 0 0 0 DMAR-MSI 0-edge dmar0
121: 0 0 0 0 0 0 0 0 DMAR-MSI 1-edge dmar1
122: 0 0 0 0 0 0 0 0 IR-PCI-MSI 475136-edge PCIe PME
123: 0 0 0 0 0 0 0 0 IR-PCI-MSI 483328-edge PCIe PME, pciehp
125: 0 0 0 0 0 0 0 0 IR-PCI-MSI 3162112-edge pciehp
127: 0 0 0 0 0 0 0 0 IR-PCI-MSI 3211264-edge pciehp
128: 0 0 0 4312723 0 0 0 0 IR-PCI-MSI 327680-edge xhci_hcd
129: 0 0 0 0 0 0 0 0 IR-PCI-MSI 23592960-edge xhci_hcd
130: 17624 0 0 0 0 0 0 0 INT34BB:00 100 SYNA8004:00
131: 0 66 0 0 0 0 0 0 IR-PCI-MSI 360448-edge mei_me
132: 0 0 24 0 0 0 0 0 IR-PCI-MSI 1572864-edge nvme0q0
133: 27865 0 0 0 0 0 0 0 IR-PCI-MSI 1572865-edge nvme0q1
134: 0 26898 0 0 0 0 0 0 IR-PCI-MSI 1572866-edge nvme0q2
135: 0 0 28219 0 0 0 0 0 IR-PCI-MSI 1572867-edge nvme0q3
136: 0 0 0 20702 0 0 0 0 IR-PCI-MSI 1572868-edge nvme0q4
137: 0 0 0 0 28341 0 0 0 IR-PCI-MSI 1572869-edge nvme0q5
138: 0 0 0 0 0 28758 0 0 IR-PCI-MSI 1572870-edge nvme0q6
139: 0 0 0 0 0 0 28855 0 IR-PCI-MSI 1572871-edge nvme0q7
140: 0 0 0 0 0 0 0 29356 IR-PCI-MSI 1572872-edge nvme0q8
141: 0 0 0 7232022 0 0 0 0 IR-PCI-MSI 32768-edge i915
142: 0 0 0 0 113 0 0 0 IR-PCI-MSI 520192-edge enp0s31f6
143: 0 0 0 0 0 467 0 0 IR-PCI-MSI 3670016-edge thunderbolt
144: 0 0 0 0 0 0 467 0 IR-PCI-MSI 3670017-edge thunderbolt
159: 0 0 0 0 0 0 0 1362083 IR-PCI-MSI 333824-edge iwlwifi:default_queue
160: 91295 0 0 0 0 0 0 0 IR-PCI-MSI 333825-edge iwlwifi:queue_1
161: 0 44645 0 0 0 0 0 0 IR-PCI-MSI 333826-edge iwlwifi:queue_2
162: 0 0 46794 0 0 0 0 0 IR-PCI-MSI 333827-edge iwlwifi:queue_3
163: 0 0 0 1204762 0 0 0 0 IR-PCI-MSI 333828-edge iwlwifi:queue_4
164: 0 0 0 0 77 0 0 0 IR-PCI-MSI 333829-edge iwlwifi:exception
165: 0 0 0 0 0 4850 0 0 IR-PCI-MSI 514048-edge AudioDSP
NMI: 209 197 201 251 195 183 193 197 Non-maskable interrupts
LOC: 15800784 14372520 14328238 24397049 18455978 14367507 17996712 13477260 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 209 197 201 251 195 183 193 197 Performance monitoring interrupts
IWI: 283675 223272 220887 4983881 273090 284491 238897 220327 IRQ work interrupts
RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries
RES: 187337 169688 168982 307730 192660 169284 525103 158347 Rescheduling interrupts
CAL: 1275258 845154 691738 477478 383505 557544 380004 481462 Function call interrupts
TLB: 102079 95510 98519 92841 95411 95596 95841 93298 TLB shootdowns
TRM: 1758 1758 1758 1758 1758 1758 1758 1758 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 355 356 356 356 356 356 356 356 Machine check polls
ERR: 0
MIS: 0
PIN: 0 0 0 0 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event
[ak@ac ~]$
I'm also seeing the same issue (and same output for these commands) with Fedora 35 and Lenovo X1 Carbon. FWIW, it seems that if I put the laptop into airplane mode (i.e. disable wifi and bluetooth) it does suspend properly. Linux FCW36 5.19.16-602.inttf.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Oct 17 16:51:38 EEST 2022 x86_64 x86_64 x86_64 GNU/Linux Updating to this kernel a few days ago and now the ability to sleep/suspend/hibernate is gone. It does go to a black screen for a few seconds then the login screen will reappear. You should provide kernel messages, where the kernel says why it gave up on the hibernate (or suspend but I have rather bad experience with suspend). Such as that 'journalctl -b0'. For example in my case I had to recently do 'rmmod thinkpad_acpi' to be able to hibernate my Lenovo laptop. This is what mostly I have in the log... When put to sleep, just go to a black screen for a few seconds then the login screen will reappear.. The same goes for hibernating.. I had no choice rather than Shutdown. Oct 26 14:05:32 FCW36.lan kernel: Freezing user space processes ... (elapsed 0.004 seconds) done. Oct 26 14:05:32 FCW36.lan kernel: OOM killer disabled. Oct 26 14:05:32 FCW36.lan kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Oct 26 14:05:32 FCW36.lan kernel: printk: Suspending console(s) (use no_console_suspend to debug) Oct 26 14:05:32 FCW36.lan kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver proc> Oct 26 14:05:32 FCW36.lan kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend+0x0/0x20 [nvidia] returns -5 Oct 26 14:05:32 FCW36.lan kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -5 Oct 26 14:05:32 FCW36.lan kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5 Oct 26 14:05:32 FCW36.lan kernel: PM: Some devices failed to suspend, or early wake event detected Oct 26 14:05:32 FCW36.lan kernel: nvme nvme0: 8/0/0 default/read/poll queues Oct 26 14:05:32 FCW36.lan kernel: nvme nvme2: 8/0/0 default/read/poll queues Oct 26 14:05:32 FCW36.lan kernel: nvme nvme1: 8/0/0 default/read/poll queues Oct 26 14:05:32 FCW36.lan kernel: ata2: SATA link down (SStatus 0 SControl 300) Oct 26 14:05:32 FCW36.lan kernel: e1000e 0000:00:1f.6 enp0s31f6: Failed to disable ULP Oct 26 14:05:32 FCW36.lan kernel: PM: resume devices took 3.244 seconds Oct 26 14:05:32 FCW36.lan kernel: OOM killer enabled. Oct 26 14:05:32 FCW36.lan kernel: Restarting tasks ... Oct 26 14:05:32 FCW36.lan kernel: userif-2: sent link down event. Oct 26 14:05:32 FCW36.lan kernel: userif-2: sent link up event. Oct 26 14:05:32 FCW36.lan kernel: done. After updating the NVIDIA driver, the problems of sleep look gone.. will test more to be assured.. nvidia-installer --version nvidia-installer: version 520.56.06 The NVIDIA Software Installer for Unix/Linux. I have dual-VGA laptop (Lenovo E15 integrated Iris Xe plus some nVidia) so I could add to kernel commandline: nouveau.blacklist=1 rd.driver.blacklist=nouveau And to /etc/modprobe.d/foo.conf: blacklist nouveau Sure no nVidia driver installed. And all the former problems with graphics are gone. I can confirm that the sleep/suspend/hibernate problem for my cases is because of the Nvidia driver. upgrading to kernel 6.0.5-200.fc36.x86_64 does not affect the function. I'm good now. 1. Run up to date Fedora 31 2. To access the GNOME Shell menu, click the upper right corner of the screen. 3. Activate the Alt key on your keyboard. 4. Press the button labeled "Pause" This was discussed once more on the Postgres email groups not more than a few days ago: http://www.postgresql.org/message-id/20140519091808.GA7296@msgid.df7cb.de https://funnyshooter2.com This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |