Misc Z13/395+ CPU problems.

So I'm finally getting around to playing a game on this thing (woot! Satisfactory factory goodness).

Alas, after about 30 minutes of play (steam + proton), the wayland user session suddenly locked up. But fortunately the keycombo to enter a virtual console worked (and alas - I don't have another machine here with me where I could have sshed).

Here's the dmseg logs I could snarf. Nasty amdgpu errors:

geeksvilleOP•3/11/25, 1:14 PM

logfile2.9KB

geeksvilleOP•3/11/25, 1:17 PM

this was with 6.13.5-102.bazzite.fc41.x86_64 (64-bit) kernel

geeksvilleOP•3/11/25, 10:02 PM

just looking at this log and the 6.13.6 changelog. I bet it is fixed in:
amdgpu/pm/legacy: fix suspend/resume issues

Ggeeksville just looking at this log and the 6.13.6 changelog. I bet it is fixed in: amdgpu...

antheas•3/11/25, 10:27 PM

.6 is in testing with mesa 25

geeksvilleOP•3/11/25, 11:11 PM

thanks! just snarfed it. So far I think 6.13.6 probably fixes it! @antheas

Though 6.13.6-101 does have a regression compared to 6.13.5:

Pressing the sleep button in the gui no longer fully enters sleep (black screen happens, wake happens but can still hear fans spinning). New error message appears in the dmesg output:

message.txt3.99KB

geeksvilleOP•3/11/25, 11:12 PM

[ 137.130226] amd_pmc AMDI000B:00: Last suspend didn't reach deepest state

geeksvilleOP•3/11/25, 11:16 PM

the failure happens after the virtual console is shutdown. I turned on no_console_suspend after seeing this problem and wherever the new sleep problem is after suspend devices completes (because the screen was dark but cpu clearly still kicking)

antheas•3/11/25, 11:17 PM

I can't test it rn Heading to bed

antheas•3/11/25, 11:17 PM

Tomorrow

antheas•3/11/25, 11:17 PM

Fucking Kernel I swear to god

Ggeeksville just looking at this log and the 6.13.6 changelog. I bet it is fixed in: amdgpu...

antheas•3/11/25, 11:24 PM

just looking at the changelog that thing probably broke it

geeksvilleOP•3/11/25, 11:24 PM

heh!

Aantheas just looking at the changelog that thing probably broke it

CheckYourFax•3/11/25, 11:30 PM

https://tenor.com/view/busy-gif-9099753845369881805

Tenor

CheckYourFax•3/11/25, 11:30 PM

Antheas to the gpu kernel peeps

antheas•3/11/25, 11:30 PM

built the revert

antheas•3/11/25, 11:35 PM

https://github.com/hhd-dev/kernel-bazzite/releases/tag/6.13.6-102

GitHub

Release 6.13.6-102: Revert AMD Sleep patch · hhd-dev/kernel-bazzite

Commit a355d0d24d00d19fa70d6408fc1be34fe8ac79e5 is suspected to be causing sleep issues on the Z13. Revert it.
Full Changelog: 6.13.6-101...6.13.6-102

antheas•3/11/25, 11:38 PM

Worked on my side but it was a dirty build

antheas•3/11/25, 11:38 PM

So tomorrow I'll test this one and hopefully Kyle will drop into testing

antheas•3/11/25, 11:39 PM

There is a chance it was something else

antheas•3/11/25, 11:39 PM

I partially built the kernel

antheas•3/11/25, 11:39 PM

So maybe missing module

geeksvilleOP•3/12/25, 1:26 AM

btw - alas, after 1 hr of play Satisfactory still crashed using this bazzite:testing branch (kernel 6.13.6-101.bazzite.fc41.x86_64). Wayland locked up. Relevant dmesg attached:

geeksvilleOP•3/12/25, 1:43 AM

newcrash29.02KB

geeksvilleOP•3/12/25, 2:03 AM

btw I just took a look at the first exception in this latest newcrash file. I bet the root cause is somewhere in panel-self-refresh. The relevant code is young (Nov 2024ish: https://lore.kernel.org/all/20241105202341.154036-1-hamza.mahfooz@amd.com/T/#m650152eb173c3a0b299c39dd843e92d0903b8b49 ) amdgpu_dm_enable_self_refresh().

geeksvilleOP•3/12/25, 2:04 AM

I'm going to dig around and see if I can find a runtime flag to turn off this feature and see if the problem goes away.

geeksvilleOP•3/12/25, 2:25 AM

ok I dug around in the relevant kernel srcs and that exception. I think very high likelyhood the problem is in the new panel-replay optimization feature. I'm currently doing a test with "rpm-ostree kargs --append=amdgpu.dcdebugmask=0x400" to mask out just that feature. I also wouldn't be surprised (based on the code comments about what that feature does) that this will also fix the occasional draw artifacts. Also the power savings provided by this feature is probably small

Ggeeksville btw - alas, after 1 hr of play Satisfactory still crashed using this bazzite:tes...

CheckYourFax•3/12/25, 2:27 AM

because the new kernel hasn't landed in testing yet

Ggeeksville ok I dug around in the relevant kernel srcs and that exception. I think very hi...

CheckYourFax•3/12/25, 2:28 AM

You can test if this is the problem by adding

dcdebugmask=0x10

dcdebugmask=0x10

to your kargs

CheckYourFax•3/12/25, 2:29 AM

this disables panel self refresh

CheckYourFax•3/12/25, 2:29 AM

rpm-ostree kargs --append-if-missing=dcdebugmask=0x10

rpm-ostree kargs --append-if-missing=dcdebugmask=0x10

CheckYourFax•3/12/25, 2:30 AM

its a power usage optimization feature

CCheckYourFax because the new kernel hasn't landed in testing yet

geeksvilleOP•3/12/25, 2:30 AM

right, I was just mentioning the 6.13.6-101 didn't even fix the original thing I thought it fixed

CCheckYourFax this disables panel self refresh

geeksvilleOP•3/12/25, 2:30 AM

IMO no need to turn off all of PSR, from looking at the code the error is in the self-refresh path only.

geeksvilleOP•3/12/25, 2:30 AM

so 0x400 probably better

Ggeeksville IMO no need to turn off all of PSR, from looking at the code the error is in the...

CheckYourFax•3/12/25, 2:31 AM

Yes, but to test whether this is actually the problem its a good idea to disable it. if your issue is fixed, you know the problem lies there

geeksvilleOP•3/12/25, 2:31 AM

0x400 turns off a subset of what 0x10 turns off

Ggeeksville 0x400 turns off a subset of what 0x10 turns off 😉

CheckYourFax•3/12/25, 2:32 AM

Sure. If that doesn't work it might still be worthwhile to turn the whole feature off.

CheckYourFax•3/12/25, 2:32 AM

My way of testing things is usually turn the whole shit off, see if it works, and then re-enable things one by one

geeksvilleOP•3/12/25, 2:32 AM

sure, I'm testing 0x400 now, if that doesn't work I'll go to a bigger hammer (with higher costs)

geeksvilleOP•3/12/25, 2:33 AM

yeah - but i've looked at the code and the error path is definitely in the section guarded by 0x400. Testing now though

geeksvilleOP•3/12/25, 3:25 AM

alas 0x400 was not sufficient, the exception eventually occurred and made it a bit deeper into amdgpu_dm_enable_self_refresh() but failed later in the function. So I switched to 0x10 (to turn off all of the PSR code). Been running now for 40 min and I think it will be golden. Because the occasional draw artifacts that everyone has seen no longer occur.

I bet this problem could occur on any eDP panel that supports PSR. ya'll could turn on dcdebugmask=0x10 on for everyone via kargs and I think the cost would be zero for any unit that doesn't have a PSR capable display. From browsing 6.14 commits it looks like AMD geeks are still futzing with this feature, so such a hack will probably be needed only for a little while.

geeksvilleOP•3/12/25, 3:29 AM

i.e. tasty sounding commits like this:

geeksvilleOP•3/12/25, 3:29 AM

drm/amd/display: Disable PSR-SU on eDP panels

geeksvilleOP•3/12/25, 9:53 AM

@antheas

the good news: turning off PSR definitely works-around the original exception in this report, it also fixes the occasional brief draw artifacts we've seen. See comment above about tasty sounding 6.14 commits for the root cause.

the bad news: I just installed the new testing build. Whichever change you backed out to make 6.13.6-102 kernel wasn't the cause of 6.13.6 failing to fully enter sleep. Sleep still doesn't fully enter when on the testing branch. Relevant dmesgs are unchanged:

[ 49.815569] PM: suspend entry (s2idle)
[ 49.841997] Filesystems sync: 0.025 seconds
[ 49.894384] Freezing user space processes
[ 50.888266] Freezing user space processes completed (elapsed 0.993 seconds)
[ 50.888285] OOM killer disabled.
[ 50.888290] Freezing remaining freezable tasks
[ 50.889316] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 50.904563] queueing ieee80211 work while going to suspend
[ 50.911953] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Asserting Reset
[ 51.048414] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 51.185959] PM: suspend devices took 0.296 seconds
[ 51.187718] ACPI: EC: interrupt blocked
[ 70.547009] amd_pmc AMDI000B:00: Last suspend didn't reach deepest state
[ 70.547561] ACPI: EC: interrupt unblocked
[ 70.746632] [drm] PCIE GART of 512M enabled (table at 0x00000083FFB00000).
[ 70.746668] amdgpu 0000:c4:00.0: amdgpu: SMU is resuming...

antheas•3/12/25, 9:54 AM

Ok so I have to do a full kernel rebuild and try it today

geeksvilleOP•3/12/25, 9:55 AM

https://tenor.com/view/batman-batman-goodnight-justice-never-sleeps-gif-14587113417653441519

Tenor

Ggeeksville https://tenor.com/view/batman-batman-goodnight-justice-never-sleeps-gif-14587113...

antheas•3/12/25, 7:11 PM

Turns out it was always broken and 13.6 is fine

antheas•3/12/25, 7:11 PM

You probably plugged in a dock or something

geeksvilleOP•3/12/25, 11:15 PM

hmm - even with no USB accessories attached behavior is same on my flow 13.6 gives that error message wrt suspend (and fans keep spinning while sleeping). 13.5 is fine.

Misc Z13/395+ CPU problems.

Similar Threads

Similar Threads

Similar Threads