Comment # 27 on bug 1029634 from Lyude Paul

Hi! Someone here CCd me seeing if I could provide any tips and I'd be happy to
try.

So unfortunately I've had no luck reproducing this on my Skylake machines using
plain MST displays, but I don't have the same Dell machine that you guys are
mentioning here (I'm going to see if we possibly have one at the office, but no
guarantees). Do you think I could get a little more information from you guys:

A full dmesg from when you reproduced the issue, along with adding
"drm.debug=0x6" to your kernel commandline to get the kernel to give me a bit
more debugging info. If you guys have any trouble getting this let me know,
I've got some tricks up my sleeves to get debugging logs out of machines.

As well, the full output from running dmidecode? This doesn't smell too badly
of bad firmware, but since Dell's got some of the worst firmware I've ever run
into I'd like to just make sure :).

As an extra, if anyone could actually get me access to one of these machines
having this issue over ssh, that would be extremely helpful.