Bug 216745 - Kernel 6.1 breaks Thinkpad T14 Gen 2 AMD connection to USB-C dock Gen 2 with kernel Null pointer
Summary: Kernel 6.1 breaks Thinkpad T14 Gen 2 AMD connection to USB-C dock Gen 2 with ...
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: AMD Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-26 21:51 UTC by Eric Zou
Modified: 2022-11-28 08:31 UTC (History)
1 user (show)

See Also:
Kernel Version: 6.1.0-rc6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
journal output with DRM debug set to 0xf (1.16 MB, text/plain)
2022-11-26 21:51 UTC, Eric Zou
Details

Description Eric Zou 2022-11-26 21:51:21 UTC
Created attachment 303299 [details]
journal output with DRM debug set to 0xf

Full description of the problem:
Connecting T14 Gen 2 AMD to Thinkpad USB C Dock Gen 2 via USB-C on DP Alt mode.

Since kernel 6.1.0-rc4 (and rc 5, rc 6), once the usb c cable is plug in, the dock and computer detected the connection by blinking on both power buttons (on laptop and dock), and then the laptop became completely unresponsive, has to be powered off by long press on power button. Based on the journal output it looks like something about DRM and AMDGPU, and Kernel null pointer (and oops message).

Keywords: 
DRM, AMDGPU

Most recent kernel version which did not have the bug:
Tried 5.19.17, 6.0.10 and it's working.

A journal output with DRM debug value set to 0xf is attached.
Comment 1 Eric Zou 2022-11-26 21:54:45 UTC
I have a feeling that this bug shall actually be directly filed to 

https://gitlab.freedesktop.org/drm/amd

instead of here, but I am not sure.

Thanks.
Eric
Comment 2 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-11-27 12:46:14 UTC
(In reply to Eric Zou from comment #0)
>
> Since kernel 6.1.0-rc4 

So 6.1.0-rc3 worked?

Anyway: this is not my area of expertise, but a few fixes that might (or might n not) be related to this were mainlined just this week. Could you hence maybe try master or 6.1-rc7 (out later today)?
Comment 3 Eric Zou 2022-11-27 13:00:23 UTC
Sorry I should have specified that I didn't try 6.1-rc3 so I don't know if that works. I started 6.1 on rc4.

No problem I will try rc-7 today.

I also don't know exactly where to file bug report when I think it is related to DRM. I just "think" it may be DRI(Non intel) but I really don't know anything about it.
Comment 4 Eric Zou 2022-11-27 23:14:56 UTC
I will close this one now (if I can) to follow https://gitlab.freedesktop.org/drm/amd/-/issues/2171

as I believe my issue is a duplicate of that.

Thanks
Eric
Comment 5 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-11-28 04:12:18 UTC
(In reply to Eric Zou from comment #4)
> I will close this one now (if I can) to follow
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171

It might (but TBH there is a second issue that recently was fixed that might be the real cause), but then it should be fixed with rc7; and if not, please let me know here (or by private mail)
Comment 6 Eric Zou 2022-11-28 08:31:38 UTC
Hi Thorsten
Thanks for your attention. I will give you an update here:

I tried rc7 asap it was out as tarball. rc7 contains code changes that I mentioned in https://gitlab.freedesktop.org/drm/amd/-/issues/2171 , and it contains exactly the patches as they discussed on that thread and prediction of what will work and not after the push to upstream to catch the release.

And my rc7 running result is a match of the progress so far from them. Allow me to copy paste my post from yesterday:

-------------------------------------
1. The kernel crashed is gone so at least I don't need to force poweroff when plug in the usb c cable to my USB-C dock Gen 2 (40AS)

2. Now my two monitors (FHD, connected to HDMI port on dock and FHD, connected to DP port on dock) just don't detect that there is signal incoming.

3. (As a result of kernel crashed is gone) I can just unplug the cable and my laptop just come back normally.
-------------------------------------

And thus the reason I believe I can close this one and follow them instead.

Sincerely
Eric

Note You need to log in before you can comment on or make changes to this bug.