[Bug 221893] amd_pmc - Last suspend didn't reach deepest state on HP ProBook 445 14 G11 (AMD Ryzen 7 7735U)
| Newsgroups | org.kernel.vger.platform-driver-x86 |
|---|---|
| Message-ID | <[email protected]/> |
https://bugzilla.kernel.org/show_bug.cgi?id=221893 Mario Limonciello (AMD) ([email protected]) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Mario Limonciello (AMD) ([email protected]) --- > ROOT CAUSE Are you sure your agent got the root cause right? Does it fail every time without the patch? Does this patch fix it every time? I would prefer to see an amd-s2idle report to confirm this. You may consider using amd-s2idle to stress both patched and unpatched cases too (it has arguments to allow running a stress cycle). > amdgpu 0000:05:00.0: failed to write reg 1aa89 wait reg 1aa8a > amdgpu 0000:05:00.0: [drm] *ERROR* IB test failed on gfx_0.0.0 (-110). > amdgpu 0000:05:00.0: ib ring test failed (-110). > amdgpu 0000:05:00.0: SMU: No response msg_reg: 1a resp_reg: 0 I say all my comments above because this is pretty "unusual" to be tied to suspend failure tied to an EC issue. That's behavior that resembles graphics not being ready. > Created attachment 310660 [details] > hp-probook-445-g11-s2idle-quirk.patch This isn't the way to upstream patches. Can you please submit the patch to the platform-driver-x86 mailing list? https://www.kernel.org/doc/html/latest/process/submitting-patches.html -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.