Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Project 'drm/intel' was moved to 'drm/i915/kernel'. Please update any links and bookmarks that may still have the old path.
Screen freeze when plug 4K DP monitor on Dell WD19TB docking
The screen has flicker after boot into desktop, the keyboard/mouse lost function and screen freezen after plug external DP 4K monitor attached to Dell WD19TB docking.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
Activity
Sort or filter
Newest first
Oldest first
Show all activity
Show comments only
Show history only
Kaichuan Hsiehchanged title from Screen freeze when plug 4K DP monitor through Dell WD19TB docking to Screen freeze when plug 4K DP monitor on Dell WD19TB docking
changed title from Screen freeze when plug 4K DP monitor through Dell WD19TB docking to Screen freeze when plug 4K DP monitor on Dell WD19TB docking
@kaichuan.hsieh, can you please try out disabling psr and see if you can still reproduce observed flickering or the freeze? This can be done by adding i915.enable_psr=0 into kernel boot parameters.
Yes, disable PSR fixes the flickering issue.
And the freeze is somehow hard to reproduce, when it happens, you can reproduce it many times in a row, but now it maybe in another state, so I can't tell if this also fixes the freeze issue.
Also not necessarily related to this issue at all but make sure all FW's are loaded successfully.
I see DMC has been loaded but GUC is not:
May 27 06:12:29 ubuntu kernel: i915 0000:00:02.0: Direct firmware load for i915/adlp_guc_70.1.1.bin failed with error -2 May 27 06:12:29 ubuntu kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin: fetch failed with error -2 May 27 06:12:29 ubuntu kernel: i915 0000:00:02.0: [drm] GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
System architecture: Linux u-XPS-9320 5.18.0-051800rc2drmintelnext20220528-generic #202205280203 SMP PREEMPT_DYNAMIC Sat May 28 02:07:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Docking station: Dell WD22TB4(update all the firmware today by fwupdmgr update)
Plug in the dock at 23s, un-plug the dock at around 48s
When the dock is plugged, the screen freeze, keyboard and touchpad have no function, can't type in and can't move. After the docker is un-plugged, keyboard and touchpad work again.
When the screen is freeze, I can ssh into the machine and found the gnome-shell occupy CPU 100%.
Attached the perf record/report screenshot with debug symbols.
I see the following errors in the log, is the BIOS up-to-date?:
May 27 06:12:29 ubuntu kernel: UBSAN: array-index-out-of-bounds in /home/kernel/COD/linux/drivers/acpi/acpica/dswexec.c:401:12May 27 06:12:29 ubuntu kernel: index -1 is out of range for type 'acpi_operand_object *[9]'May 27 06:12:29 ubuntu kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.18.0-051800drmtip20220526-generic #202205260203May 27 06:12:29 ubuntu kernel: Hardware name: Dell Inc. XPS 9320/, BIOS 1.3.0 04/19/2022...May 27 06:12:31 ubuntu kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20211217/psargs-330)May 27 06:12:31 ubuntu kernel: May 27 06:12:31 ubuntu kernel: No Local Variables are initialized for Method [_OSC]May 27 06:12:31 ubuntu kernel: May 27 06:12:31 ubuntu kernel: Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation)May 27 06:12:31 ubuntu kernel: Arg0: 0000000083f34cc5 <Obj> Buffer(16) 5D A8 3B B2 B7 C8 42 35May 27 06:12:31 ubuntu kernel: Arg1: 000000005ec0c6a9 <Obj> Integer 0000000000000001May 27 06:12:31 ubuntu kernel: Arg2: 00000000dd5c12bc <Obj> Integer 0000000000000002May 27 06:12:31 ubuntu kernel: Arg3: 000000001d54b6f1 <Obj> Buffer(8) 00 00 00 00 05 00 00 00May 27 06:12:31 ubuntu kernel: May 27 06:12:31 ubuntu kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
@acelan , was the attached dmesg.log from the hang case? I can see there one connect and disconnect sequence at
06:13:40 , without any obvious issues. Is the machine still accessible?
Can you reproduce the issue plugging the hub without any display connected to it? If not, could you try if the problem reproduces with i915.enable_dp_mst=0 ?
Yes, the log is from the hang case. The machine is currently on my hand. Kaichuan Hsieh will get another machine to reproduce this issue today.
Looks like i915.enable_dp_mst=0 fixes the issue. Boot up with this parameter 3 times, can't reproduce the issue, and encounter the issue the fourth time reboot without this parameter.
Tried i915.enable_dp_mst=0 on my Precision 5750 with Ubuntu 22.04 + 5.18 drm-intel-next 05-28, issue behavior changes to:
1, built in 4k panel still freezes
2, external 4K monitor changes to flicking instead of freeze
@acelan , could you provide the no MST dmesg log as well (unless you notice the issue is still reproducible with that)? Also with MST enabled at the freeze state are you able to stop the GUI (systemctl stop gdm, or killall Xorg) note if you get back the framebuffer console, and provide the dmesg log afterwards (marking somehow the timestamp in dmesg when the freeze happened, and also when you got back the FB console).
@sunnycrown , not sure if the two issues have the same root cause, you have an Nvidia card, while @acelan doesn't. Could you provide a drm.debug=0x10e log after the freeze and - if the machine is still accessible - after an attempt to stop the GUI and recover an FB console (marking the timestamps in dmesg for the freeze and recovery)?
In my Precision 5750, on top of Ubuntu 22.04 image, after installed NV graphic driver via "sudo apt install nvidia-driver-510", without dp_mst disable, it works with 4K 60hz external monitor.
Yes, there are 2 outputs connected to the dock, but the 2 outputs are to the same monitor with different type of connector(DP and HDMI). This is much easier to reproduce this issue.
u@u-XPS-9320:~$ xrandr --output XWAYLAND0 --offX Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Serial number of failed request: 36 Current serial number in output stream: 37u@u-XPS-9320:~$ xrandr --output XWAYLAND1 --offu@u-XPS-9320:~$ xrandr --output XWAYLAND2 --offX Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Serial number of failed request: 34 Current serial number in output stream: 36u@u-XPS-9320:~$ xrandr --output XWAYLAND1 --mode 3440x1440
This is more like a gnome shell issue I'm afraid of. When the screen freeze, meta + l makes the screen dim(other hotkeys do not work) and then touch the touchpad leads me to gdm to login. Touchpad and keyboard work in gdm. And then login to desktop, keyboard and touchpad stop working again, and the screen looks like freeze.
@acelan , yes scanout seems to be okay then, so looks more like a user space issue.
You could also try unplugging one of the monitors before stopping the GUI, to see if you get back a working FB console (the modeset with 2 monitors fails then for an unrelated BW issue).
@sunnycrown , disabling MST means that only one output stream will be supported for each TBT DP tunnel, so probably not all connectors on the hub can be used at the same time.