Bug 1216593 - Display connected over a docking station horribly flickers and even shuts down sometimes
Summary: Display connected over a docking station horribly flickers and even shuts dow...
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Leap 15.5
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-26 08:28 UTC by Krystof Jelinek
Modified: 2023-10-29 09:51 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Krystof Jelinek 2023-10-26 08:28:10 UTC 
Hello,

if I connect a display over a USB-C docking station on an intel integrated UHD graphics on a laptop (with a secondary nvidia chip), the display starts to horribly flicker after a short period of time. Visual glitches, improperly rendered lines and other things start showing almost immediately after boot, and after that, the display completely loses signal as well, rendering the system unusable.

I found out on a lot of forums that this bug is related to new Kernel drivers from version 5.16 onward, I tested it on an old Debian buster (with kernel 5.14) and everything was fine. The issue however persists from Leap 15.4 to 15.5 to even tumbleweed, which I tried to make sure that newer package versions wouldn't resolve it.

The docking station model is Dell WD15, however from what I read, it's completely unrelated to the issue.


If you need more info, don't hesitate to contact me.
Chris
Comment 1 Takashi Iwai 2023-10-26 08:38:06 UTC 
The best would be to report this to upstream and debug / fix there, as it happens with the TW kernel.
Please open an entry on gitlab.freedesktop.org Issues DRM/Intel.

Attach the detailed graphics hardware information there.  And, if it's reliably reproducible, try to boot the recent upstream (e.g. TW) kernel with drm.debug=0x1e log_buf_len=16M options, and get the dmesg output at the visual problem, and attach it, too.
Comment 2 Krystof Jelinek 2023-10-29 09:51:00 UTC 
(In reply to Takashi Iwai from comment #1)
> The best would be to report this to upstream and debug / fix there, as it
> happens with the TW kernel.
> Please open an entry on gitlab.freedesktop.org Issues DRM/Intel.
> 
> Attach the detailed graphics hardware information there.  And, if it's
> reliably reproducible, try to boot the recent upstream (e.g. TW) kernel with
> drm.debug=0x1e log_buf_len=16M options, and get the dmesg output at the
> visual problem, and attach it, too.

Ok, thank you. Will do.