Bug 1217300 - Steam deck wake up issues with external tv connected with hdmi.
Summary: Steam deck wake up issues with external tv connected with hdmi.
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL: G
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-18 12:44 UTC by ted chang
Modified: 2023-11-18 20:48 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
lg um7300pua - /sys/devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1/card1-DP-1/edid (256 bytes, application/octet-stream)
2023-11-18 12:44 UTC, ted chang
Details
dmesg logs - 2023-18-11 (299.82 KB, text/plain)
2023-11-18 12:45 UTC, ted chang
Details
jounrnalctl -b 0 - 2023-11-18 (7.06 MB, text/plain)
2023-11-18 12:46 UTC, ted chang
Details
PIcture of tty wakeup. (1.09 MB, image/jpeg)
2023-11-18 12:49 UTC, ted chang
Details
ps -ef - 2023-11-18 second occuranceb (35.51 KB, text/plain)
2023-11-18 20:39 UTC, ted chang
Details
dmesg logs - 2023-11-18 second occurance (276.85 KB, text/plain)
2023-11-18 20:40 UTC, ted chang
Details
jounrnalctl -b 0 - 2023-11-18 - second occurance (2.52 MB, text/plain)
2023-11-18 20:45 UTC, ted chang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ted chang 2023-11-18 12:44:44 UTC
Created attachment 870835 [details]
lg um7300pua - /sys/devices/pci0000:00/0000:00:08.1/0000:04:00.0/drm/card1/card1-DP-1/edid

The steam deck have wake up issues. The issue might be firmware related but Valve release a new firmware. The screen woke up to a blinking cursor. I managed to take a picture, grab journalctl and dmesg logs. This bug report has my TV edid too which is connected with HDMI


Hardware 
LG UM7300AUE Firmware: 05.30.40
Steam Deck LCD Firmware: F7A0119
Steam Deck Dock Firmware: 121

Linux steamdeck.lan 6.6.1-1-default #1 SMP PREEMPT_DYNAMIC Thu Nov  9 05:27:56 UTC 2023 (1fcc265) x86_64 x86_64 x86_64 GNU/Linux

gnome version: 45.1

 lsb_release -a
LSB Version:	n/a
Distributor ID:	openSUSE
Description:	openSUSE Tumbleweed
Release:	20231116
Codename:	n/a
Comment 1 ted chang 2023-11-18 12:45:59 UTC
Created attachment 870836 [details]
dmesg logs - 2023-18-11

This log was retrieved in tty.
Comment 2 ted chang 2023-11-18 12:46:47 UTC
Created attachment 870837 [details]
jounrnalctl -b 0 - 2023-11-18

Grab in tty
Comment 3 ted chang 2023-11-18 12:49:09 UTC
Created attachment 870838 [details]
PIcture of tty wakeup.
Comment 4 ted chang 2023-11-18 12:58:27 UTC
[10833.653587] amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx_0.0.0 (-110).
[10833.654288] [drm:process_one_work] *ERROR* ib ring test failed (-110).
[10833.881572] OOM killer enabled.
[10833.881575] Restarting tasks ... 
[10833.884539] Bluetooth: hci0: RTL: examining hci_

I should had check my available ram or running processes. I was running docker-compose  before this device was sleeping.

Oh well. Please close this issue if there isn't anything interesting with my logs.

The issue is that this device somehow didn't wake up correctly.
Comment 5 ted chang 2023-11-18 20:39:38 UTC
Created attachment 870840 [details]
ps -ef  - 2023-11-18 second occuranceb

I manage to grab running processes this time.
Comment 6 ted chang 2023-11-18 20:40:13 UTC
Created attachment 870841 [details]
dmesg logs - 2023-11-18 second occurance

Second time this wake issue happened.
Comment 7 ted chang 2023-11-18 20:45:51 UTC
Created attachment 870842 [details]
jounrnalctl -b 0 - 2023-11-18 - second occurance

Truncated the logs. The logs seems to spam 

Nov 18 12:00:12 steamdeck.lan gnome-keyring-d[1841]: asked to register item /org/freedesktop/secrets/collection/login/7, but it's already registered
Comment 8 ted chang 2023-11-18 20:48:05 UTC
Hmmm. Is it a libsecret bug? I might have to check memory usage of it. I am testing a library that allows me to access libsecret though flutter. Since I am developing something in the early stage, I do not care and keep rewriting the secret key. I will obviously fix it later. I might have to check the mem usage.