[Bug 209713] New: amdgpu drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_link_encoder.c:483 dcn10_get_dig_frontend+0x9e/0xc0 [amdgpu] when resuming from S3 state

[bugzilla-daemon at bugzilla.kernel.org]

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

            Bug ID: 209713
           Summary: amdgpu
                    drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_l
                    ink_encoder.c:483 dcn10_get_dig_frontend+0x9e/0xc0
                    [amdgpu] when resuming from S3 state
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.8.13-arch1-1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: samy at lahfa.xyz
        Regression: No

Created attachment 293025
  --> https://bugzilla.kernel.org/attachment.cgi?id=293025&action=edit
parts of dmesg where the call trace happens during the resume from S3 sleep
state.

I'm thinking that this bug is a regression since I haven't seen this call trace
before on kernel older than 5.8.12-arch1-1 but I have yet to confirm this.

The call trace may also happen only in a very specific way, my current computer
has a USB-C Dock that is plugged in and the call trace happened when the USB-C
was plugged in and the computer was suspended, then resumed.

It is a Lenovo Thinkpad T495 model 20NKS28F00 with an AMD Ryzen 7 3700U and a
Vega Radeon RX 10.

Further comments will confirm if the call trace happens only when the USB-C
Dock is plugged.

As well as if this call trace happens on kernels older than 5.8.12-arch1-1.

The computer does resume successfully and there is a like a minor screen glitch
for a millisecond so it's not a very severe bug.

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