Created attachment 132257 [details] dmesg with drm.debug=0xe I have a new Dell XPS 13 9360. According to drm logs: platform=KABYLAKE gen=9 pciid=0x5926 rev=0x06. I updated from Ubuntu 16.04 to 17.04 and installed Linux 4.12-rc7 (from today). I also have two Dell U2715H monitors (2560x1440) set up for DP1.2/MST. They worked well for the past couple of years with a XPS 13 9343 (Broadwell), using a mini-DP to DP cable. I'm trying to switch to the new laptop, but it doesn't seem to recognise the monitors at all. It never did. I am using a Google USB-C to DP cable. If I revert the monitors back to DP1.1, the first one is detected, but daisy-chaining won't work (of course). I also have a Dell dock, but I use it only as a glorified USB and Ethernet hub. In case you're wondering, I don't use it for anything more, because its USB audio tends to lock up and the gross, CPU-draining DisplayLink software/hardware hack is utter garbage (to be kind). Anyway, what really puzzles me about the Kaby Lake laptop is that this is a regression from two years ago. I'm attaching dmesg output with drm.debug=0xe. Please advise. The old laptop sometimes has terrifying loud POST errors about the built-in LCD screen, so switching to the new one would be timely. :-)
Hello Rudi. Could you please try to replicate the test but using the last version available of kernel and Xserver. Then could you please share with us the kern.log file and new dmesg file. Thanks.
Created attachment 132360 [details] dmesg from cod/tip/drm-tip/2017-06-29 (85a692e2c6a7cf93082044d776e838cb9e9b2146)
Hi Manuel, is the latest Xserver available as .deb packages? I can't find any. I rebooted into the latest kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ and I'm attaching its dmesg/kern.log outputs.
Created attachment 132361 [details] kern.log from cod/tip/drm-tip/2017-06-29 (85a692e2c6a7cf93082044d776e838cb9e9b2146)
Changing to REOPEN since reporter provided the requested information.
Hello Rudi, according to dmesg only eDP is detected as connected and the rest as disconnected since the beginning, any changes with latest tip? It include various DP MST fixes merged made on 10/12 that could help with this. Thanks.
I just tried with 4.15.0-994-generic #201801050316. Still nothing. Whenever I plug the USBC-DP cable, this shows up in the logs: Jan 09 10:59:32 domo kernel: ACPI Error: [SPRT] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dswload2-346) Jan 09 10:59:32 domo kernel: No Local Variables are initialized for Method [XTBT] Jan 09 10:59:32 domo kernel: Initialized Arguments for Method [XTBT]: (2 arguments defined for method invocation) Jan 09 10:59:32 domo kernel: Arg0: 000000003ba0dc24 <Obj> Integer 0000000000000001 Jan 09 10:59:32 domo kernel: Arg1: 00000000f74122ac <Obj> Integer 0000000002060002 Jan 09 10:59:32 domo kernel: ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20170831/psobject-252) Jan 09 10:59:32 domo kernel: ACPI Error: Method parse/execution failed \_GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550) Jan 09 10:59:32 domo kernel: ACPI Error: Method parse/execution failed \_GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550) Jan 09 10:59:32 domo kernel: ACPI Error: Method parse/execution failed \_GPE._E42, AE_ALREADY_EXISTS (20170831/psparse-550) Jan 09 10:59:32 domo kernel: ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20170831/evgpe-646) Jan 09 10:59:32 domo kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0 Jan 09 10:59:32 domo kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) Jan 09 10:59:32 domo kernel: pcieport 0000:00:1c.0: device [8086:9d10] error status/mask=00002001/00002000 Jan 09 10:59:32 domo kernel: pcieport 0000:00:1c.0: [ 0] Receiver Error (First) The Gnome preferences don't show any monitors as plugged in. If I go to the monitor's controls and switch the input from DP (the right port) to mDP (empty!), the monitor gets detected and is available to be set up on the Linux side, but of course no image will appear.
Hello, would you mind sharing a dmesg with the latest kernel??
Created attachment 136635 [details] new dmesg from 4.15
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Please test latest drm-tip as there are now some MST fixes again. https://cgit.freedesktop.org/drm-tip
Closing, please re-open if occurs again.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.