[Bug 216899] New: amdgpu ring timeout after gfxoff on Navi 24 beige_goby

bugzilla-daemon at kernel.org bugzilla-daemon at kernel.org
Sat Jan 7 16:28:12 UTC 2023


https://bugzilla.kernel.org/show_bug.cgi?id=216899

            Bug ID: 216899
           Summary: amdgpu ring timeout after gfxoff on Navi 24 beige_goby
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.1.2-gentoo
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: dylan-kernel at dylex.net
        Regression: No

Created attachment 303547
  --> https://bugzilla.kernel.org/attachment.cgi?id=303547&action=edit
boot messages and pci info

I have a new Powercolor AMD Radeon RX 6400 ITX and whenever the screen is
blanked (DPMS or X blanking -- I haven't tried non-X) with gfxoff enabled, the
whole system hangs (or at least network and alt-sysrq are unresponsive, though
there seems to be some activity):

Jan  7 01:12:29 talula kernel: [drm:amdgpu_job_timedout] *ERROR* ring gfx_0.0.0
timeout, signaled seq=23406, emitted seq=23407
Jan  7 01:12:29 talula kernel: [drm:amdgpu_job_timedout] *ERROR* Process
information: process X pid 3404 thread X:cs0 pid 3412
Jan  7 01:12:29 talula kernel: amdgpu 0000:75:00.0: amdgpu: GPU reset begin!
Jan  7 01:12:32 talula kernel: amdgpu 0000:75:00.0: amdgpu: SMU: I'm not done
with your previous command: SMN_C2PMSG_66:0x00000029 SMN_C2PMSG_82:0x00000000
Jan  7 01:12:32 talula kernel: amdgpu 0000:75:00.0: amdgpu: Failed to disable
gfxoff!

Setting amdgpu_gfxoff to 0 in debugfs prevents this, and everything works
correctly.  I've tried this on 5.15.80 and checked I have the most recent
firmware.  Happy to provide any additional info or try additional diagnostics. 
Full boot messages and pci info for card attached.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list