i915: loss of the screen connected in DP to my dockstation

Bug #2007173 reported by Nicolas Devillers
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since a few versions of the kernel I'm losing the screen connected to my dockstation thinkpad using displayport. My running laptop is a thinkpad T14s

I'm currently running
"Linux laptop 5.19.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 15 12:05:40 UTC 2 x86_64 x86_64 x86_64 GNU/Linux"

but I had the same issue while running "linux-image-5.15.0-60-generic" and I think with "linux-image-5.15.0-58-generic" too.

When losing the screen, I'm getting "i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful" from the kernel.

During the last screen loss, I tried to connect the DisplayPort to another screen to eliminate the possibility that it could be a issue with it.

Not only did the other screen not work either, but I got the following stacktrace:

17957.541801] CPU: 3 PID: 30705 Comm: kworker/3:1 Tainted: G U 5.19.0-28-generic #29~22.04.1-Ubuntu
[17957.541811] Hardware name: LENOVO 20T1S62300/20T1S62300, BIOS N2YET34W (1.23 ) 12/31/2021
[17957.541816] Workqueue: events i915_hotplug_work_func [i915]
[17957.542099] RIP: 0010:intel_dp_prep_link_retrain+0x1b0/0x1d0 [i915]
[17957.542378] Code: d2 74 32 48 89 55 a8 4c 89 4d b0 e8 1a 86 f3 f5 48 8b 55 a8 48 c7 c1 50 7c b0 c0 48 c7 c7 e6 00 ae c0 48 89 c6 e8 87 5a 41 f6 <0f> 0b 4c 8b 4d b0 e9 36 ff ff ff 48 8b 17 eb c9 e8 ab bc 4d f6 e9
[17957.542385] RSP: 0018:ffffb27bc6677cb0 EFLAGS: 00010246
[17957.542393] RAX: 0000000000000000 RBX: ffff9d6da9ef26c0 RCX: 0000000000000000
[17957.542398] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[17957.542401] RBP: ffffb27bc6677d08 R08: 0000000000000000 R09: 0000000000000000
[17957.542405] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9d6c99894170
[17957.542409] R13: ffffb27bc6677d27 R14: ffffb27bc6677d70 R15: ffff9d6ca032c800
[17957.542414] FS: 0000000000000000(0000) GS:ffff9d73ad6c0000(0000) knlGS:0000000000000000
[17957.542420] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[17957.542425] CR2: 0000170804379000 CR3: 0000000792010005 CR4: 00000000003706e0
[17957.542431] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[17957.542434] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[17957.542439] Call Trace:
[17957.542443] <TASK>
[17957.542453] intel_dp_retrain_link+0xee/0x2f0 [i915]
[17957.542773] intel_ddi_hotplug+0xc6/0x1f0 [i915]
[17957.543049] i915_hotplug_work_func+0x1f3/0x320 [i915]
[17957.543316] process_one_work+0x222/0x400
[17957.543327] worker_thread+0x50/0x3e0
[17957.543334] ? rescuer_thread+0x3c0/0x3c0
[17957.543340] kthread+0xe6/0x110
[17957.543349] ? kthread_complete_and_exit+0x20/0x20
[17957.543359] ret_from_fork+0x1f/0x30
[17957.543374] </TASK>
[17957.543377] ---[ end trace 0000000000000000 ]---
[17985.975481] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[17991.187501] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful

Distrib is :
"lsb_release -rd
Description: Linux Mint 21
Release: 21"

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2007173

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 2007173

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first.

(If apport-collect isn't completed; this bug may not be able to be explored until it's encountered on a system where apport tools are used in the bug report, where by this report can provide the confirmation (ie. this reported marked as duplicate of the report thus this is the confirmationl))

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.