All of lore.kernel.org
 help / color / mirror / Atom feed
* [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
@ 2020-10-16  9:31 bugzilla-daemon
  2020-10-23  4:21 ` [Bug 209713] " bugzilla-daemon
                   ` (18 more replies)
  0 siblings, 19 replies; 20+ messages in thread
From: bugzilla-daemon @ 2020-10-16  9:31 UTC (permalink / raw)
  To: dri-devel

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@kernel-bugs.osdl.org
          Reporter: samy@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 20+ messages in thread
end of thread, other threads:[~2021-03-01 20:46 UTC | newest]

Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-16  9:31 [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
2020-10-23  4:21 ` [Bug 209713] " bugzilla-daemon
2020-10-23  8:12 ` bugzilla-daemon
2020-10-23 19:53 ` bugzilla-daemon
2020-12-26  9:22 ` bugzilla-daemon
2020-12-26  9:23 ` bugzilla-daemon
2021-01-11 21:27 ` bugzilla-daemon
2021-01-13 19:57 ` bugzilla-daemon
2021-01-13 20:44 ` bugzilla-daemon
2021-01-20 20:43 ` bugzilla-daemon
2021-01-23 18:04 ` bugzilla-daemon
2021-01-23 18:10 ` bugzilla-daemon
2021-01-24  9:03 ` bugzilla-daemon
2021-01-31 10:37 ` bugzilla-daemon
2021-02-16 15:41 ` bugzilla-daemon
2021-02-24 20:13 ` bugzilla-daemon
2021-02-25  0:00 ` bugzilla-daemon
2021-02-25  0:02 ` bugzilla-daemon
2021-02-26 19:47 ` bugzilla-daemon
2021-03-01 20:46 ` bugzilla-daemon

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.