ValveSoftware / SteamOS

SteamOS community tracker
1.53k stars 69 forks source link

3.6.x Preview/Beta Branches do not allow Steam Deck to Sleep #1558

Open xenrohachi opened 1 month ago

xenrohachi commented 1 month ago

Please describe your issue in as much detail as possible:

Beta/Preview Channels do not allow Steam Deck to go to sleep. Pressing power button will play sleep video, but after about 1-2 seconds the SD will play the "power on" sound and re-awaken. Uninstalled Decky to ensure it was not being caused by that. SD OLED, i have the stock Kingston 512GB NVMe

Edit: Uploaded System Report after bug, profile name: SpoopyToots

Steps for reproducing this issue:

  1. Be on Beta/Preview
  2. Press Power Button for Sleep
  3. Do not get sleep mode
xenrohachi commented 1 month ago

$ cat /sys/power/pm_wakeup_irq cat: /sys/power/pm_wakeup_irq: No data available

`$ cat /proc/interrupts` ``` CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 45 0 0 0 0 0 0 0 IO-APIC 2-edge timer 1: 19 0 0 0 0 0 14 0 IO-APIC 1-edge i8042 4: 70 0 0 0 110 0 0 0 IO-APIC 4-edge AMDI0010:02 6: 0 0 0 0 0 0 0 0 IO-APIC 6-edge AMDI0010:03 7: 7177 0 0 0 0 0 665 0 IO-APIC 7-fasteoi pinctrl_amd 8: 0 0 0 0 0 1 0 0 IO-APIC 8-edge rtc0 9: 3400 369 0 0 0 0 0 0 IO-APIC 9-fasteoi acpi 10: 17219 0 1075 0 0 0 0 0 IO-APIC 10-edge AMDI0010:00 11: 471452 0 0 938 0 0 0 0 IO-APIC 11-edge AMDI0010:01 15: 0 0 176 1992 0 0 0 0 IO-APIC 15-edge ttyS5 25: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:01.2 0-edge PCIe PME, aerdrv, pcie-dpc 26: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:01.3 0-edge PCIe PME, aerdrv, pcie-dpc 27: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:01.4 0-edge PCIe PME, aerdrv, pcie-dpc 28: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:08.1 0-edge PCIe PME 29: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:08.2 0-edge PCIe PME 30: 0 0 0 0 0 0 0 0 PCI-MSI-0000:00:08.3 0-edge PCIe PME 32: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 0-edge xhci_hcd 33: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 1-edge xhci_hcd 34: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 2-edge xhci_hcd 35: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 3-edge xhci_hcd 36: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 4-edge xhci_hcd 37: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 5-edge xhci_hcd 38: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 6-edge xhci_hcd 39: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.3 7-edge xhci_hcd 41: 149780 0 0 0 0 0 12834 0 PCI-MSIX-0000:04:00.4 0-edge xhci_hcd 42: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 1-edge xhci_hcd 43: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 2-edge xhci_hcd 44: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 3-edge xhci_hcd 45: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 4-edge xhci_hcd 46: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 5-edge xhci_hcd 47: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 6-edge xhci_hcd 48: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.4 7-edge xhci_hcd 50: 0 0 0 120 0 0 0 0 PCI-MSIX-0000:01:00.0 0-edge nvme0q0 51: 5938 0 0 0 0 0 0 0 PCI-MSIX-0000:01:00.0 1-edge nvme0q1 52: 0 4483 0 0 0 0 0 0 PCI-MSIX-0000:01:00.0 2-edge nvme0q2 53: 0 0 7652 0 0 0 0 0 PCI-MSIX-0000:01:00.0 3-edge nvme0q3 54: 0 0 0 5825 0 0 0 0 PCI-MSIX-0000:01:00.0 4-edge nvme0q4 55: 0 0 0 0 6409 0 0 0 PCI-MSIX-0000:01:00.0 5-edge nvme0q5 56: 0 0 0 0 0 5904 0 0 PCI-MSIX-0000:01:00.0 6-edge nvme0q6 57: 0 0 0 0 0 0 6192 0 PCI-MSIX-0000:01:00.0 7-edge nvme0q7 58: 0 0 0 0 0 0 0 5364 PCI-MSIX-0000:01:00.0 8-edge nvme0q8 60: 4449 242 0 0 0 0 0 0 PCI-MSI-0000:02:00.0 0-edge mmc0 61: 7176 0 0 0 0 0 663 0 amd_gpio 84 FTS3528:00 63: 0 0 0 0 0 0 0 0 PCI-MSIX-0000:04:00.2 0-edge psp-1 65: 26193 0 0 0 1205 0 0 0 IO-APIC 27-fasteoi AudioDSP 66: 0 0 0 0 392 0 0 0 PCI-MSI-0000:04:00.1 0-edge snd_hda_intel:card0 67: 1 0 0 0 0 0 1 0 amd_gpio 86 nau8821 68: 38496 0 0 0 0 0 0 0 PCI-MSI-0000:03:00.0 0-edge bhi, mhi, mhi, ce0, ce1, ce2, ce3, ce5, ce7, ce8, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ, DP_EXT_IRQ 69: 161459 0 0 0 0 12773 0 0 PCI-MSIX-0000:04:00.0 0-edge amdgpu NMI: 1 5 5 5 5 5 337 4 Non-maskable interrupts LOC: 242344 232212 226364 199747 345582 156457 340875 160101 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 1 5 5 5 5 5 338 4 Performance monitoring interrupts IWI: 525 1 5 0 0 500 0 0 IRQ work interrupts RTR: 0 0 0 0 0 0 0 0 APIC ICR read retries RES: 7204 8378 9580 7225 4669 4219 5169 22034 Rescheduling interrupts CAL: 234238 233766 273941 234717 254323 233941 260024 279312 Function call interrupts TLB: 9259 7618 9945 7137 8202 8341 9661 10152 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 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: 4 3 3 3 3 3 3 3 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 ```

$ uname -a Linux steamdeck 6.5.0-valve12-1-neptune-65-g1889664e19fc #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 00:07:43 +0000 x86_64 GNU/Linux

Managor commented 1 month ago

Turn off Bluetooth. That seems to be the root cause.

xenrohachi commented 1 month ago

Yup, that worked! lol

lyndonguitar commented 1 month ago

same thing for me

similar to this altho im not sure if its still an SSD related issue

submitted report steamuser: lyndonguitar

xenrohachi commented 1 month ago

Ok so it’s definitely Bluetooth related as you know. But even when you turn it off in Gaming Mode, it seems to turn itself back on in the background after some time. And it’s only able to be turned off in desktop mode.

BUT even when you turn it off in desktop mode, it’ll still turn itself back on. The last time it happened today: after i turned the Bluetooth off and returned to gaming mode, I put the SD to sleep. And it appeared to successfully shut down. About 2 minutes later the SD turned on by itself again. Went to desktop mode, Bluetooth was back on. I’ve uploaded 2 more system reports but only the last one should be relevant if you wanted to investigate further.

Thank you

Managor commented 1 month ago

I managed to find a repro. Pair the same Steam Controller two times through bluetooth.

lyndonguitar commented 1 month ago

same thing for me

similar to this altho im not sure if its still an SSD related issue

submitted report steamuser: lyndonguitar

turning off bluetooth did not fix mine

submitted another report with the same username

xenrohachi commented 1 month ago

I managed to find a repro. Pair the same Steam Controller two times through bluetooth.

Specifically a Steam Controller? i have one but never connected it to this SD. I did do this twice though with the Dualsense i usually use, same result.

Edit: Dusted off my old Steam Controller, same result

xenrohachi commented 1 month ago

Ok so maybe a bit of progress? I deleted all my previously paired devices. And turned off "allow device to wake SD" on all of them before deleting. Successfully went to sleep. Re-paired Dualsense, kept "allow to wake" on, still sleeping. Will report if the issue returns.

Sleeps with BT enabled as well.

xenrohachi commented 4 weeks ago

After a couple of days, the issue always seems to come back after some time. The only consistent solution I've had is to have no previously paired devices and turn the bluetooth on then off in the Steam UI. That will make the issue go away temporarily again. This issue only started happening on the 3.6 branch. I was on Preview before and had to switch to Beta to make the issue go away. Now that Beta is on 3.6, the issue is present again.

ajaxjiang96 commented 3 weeks ago

I've run into the same issue. Was connected to my AirPods Pro. The screen turns back on right after the sleep mode animation.

gaelkerchenbaum commented 2 weeks ago

Same issue here on the OLED deck. Pressing the sleep button on Preview wakes up immediately after the sleep animation. I had to reverse to Main. It has happened for me even with the previous fix in beta.

Bluetooth is turned off.

montek92 commented 2 weeks ago

Some time ago the console fell asleep normally. After one of the updates, I noticed that NFS Unbound wouldn't go to sleep (and it did!) - the console wakes up after pressing the POWER button. I thought - okay, EA probably messed something up. And I discovered that the EABackground background service was preventing the console from falling asleep. I give up.

I played non-steam games for some time and had no problem sleeping.

The new season of Last Epoch came out yesterday and... I turn the game off and the console wakes up after I turn it off! E.g. Diablo 4 sleeps without any problems (STEAM version) I downloaded the "pause game" plugin but it doesn't help (it helps with Fallout 4, because I also have trouble sleeping) SteamOS 3.7 and 3.6.8 (OLED) For test i back to 3.5.19 and sleep work very well...

KonstantinAlexeevich commented 2 days ago

I have same problem. I tried:

All of this points not working for me. It's so sad.

KonstantinAlexeevich commented 2 days ago

I сreate system report after "wrong sleep mode".

$ uname -a
Linux steamdeck 6.5.0-valve12-1-neptune-65-g1889664e19fc #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 00:07:43 +0000 x86_64 GNU/Linux

Stock SSD: phison esmp001tkb5c3-e19ts

SteamDeck Oled

systemreport_20240728150852.txt konsole_.txt

lostgoat commented 1 day ago

@KonstantinAlexeevich do you have any USB devices plugged in?

Your system report says that your deck is not going to sleep due to a USB device requesting immediate wakeup.

Does your system suspend correctly if you switch to the stable channel?

KonstantinAlexeevich commented 1 day ago

@lostgoat

Yesterday maybe usb was plugged in. Today I maded "Re-image Steam Deck" again and update to latest version by stable channel

(deck@steamdeck ~)$ uname -a
Linux steamdeck 6.1.52-valve16-1-neptune-61 #1 SMP PREEMPT_DYNAMIC Tue, 06 Feb 2024 00:51:49 +0000 x86_64 GNU/Linux

After that I do:

No one USB device wasn't plugged in this time

reports: systemreport-20240729182345.txt systemreport-20240729182442.txt

KonstantinAlexeevich commented 1 day ago

After awake my deck has no sound and a must shutdown it before I can play with sound. This is my root problem.