bugzilla-daemon at freedesktop.org
2018-Oct-22 23:19 UTC
[Nouveau] [Bug 108520] New: MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 Bug ID: 108520 Summary: MST DisplayPort HiDPI screen flicker Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: jhnmlkvch9 at gmail.com QA Contact: xorg-team at lists.x.org HiDPI MST monitor connected via DisplayPort has bad screen flicker (one to three high speed flickers every 20 seconds or so). Version of X: 1.20 Nouveau: 1.0.15-3 Kernel: 4.18.16-arch1-1-ARCH Curiously, the flicker only happens on my Optimus laptop with Hybrid Graphics disabled (Intel off, Nouveau on). The flicker disappears if Hybrid Graphics is enabled (Both Intel and Nouveau cards on). Can't find anything relevant in dmesg, journal etc., but let me know which logs will be useful and I can upload them. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181022/e652b026/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 00:09 UTC
[Nouveau] [Bug 108520] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> --- I'd guess that in hybrid mode, the DP port is driven by Intel, which has a more battle-tested implementation. dmesg and xorg log will be useful to provide background information, even if they don't have any errors in them. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/cca8ac98/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 18:56 UTC
[Nouveau] [Bug 108520] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #2 from JM9 <jhnmlkvch9 at gmail.com> --- Created attachment 142160 --> https://bugs.freedesktop.org/attachment.cgi?id=142160&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/820f464c/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 18:57 UTC
[Nouveau] [Bug 108520] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #3 from JM9 <jhnmlkvch9 at gmail.com> --- Created attachment 142161 --> https://bugs.freedesktop.org/attachment.cgi?id=142161&action=edit xorg log -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/dc4e3af7/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 18:57 UTC
[Nouveau] [Bug 108520] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #4 from JM9 <jhnmlkvch9 at gmail.com> --- (In reply to Ilia Mirkin from comment #1)> I'd guess that in hybrid mode, the DP port is driven by Intel, which has a > more battle-tested implementation. > > dmesg and xorg log will be useful to provide background information, even if > they don't have any errors in them.attached xorg log and dmesg -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/1bd29b35/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 19:00 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|MST DisplayPort HiDPI |[GK104] MST DisplayPort |screen flicker |HiDPI screen flicker -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/a66e2d18/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 19:04 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> --- OK, so ... A few facts: - GK104 - Driving 4 monitors Question: Are the 2560x1440 and 1920x1200 daisy-chained (hence the "MST" reference), or is it just that the 2560x1440 monitor's manufacturer name is "MST", without any reference to Multi-Stream Transport? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/fd4c20e5/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 19:38 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #6 from JM9 <jhnmlkvch9 at gmail.com> --- (In reply to Ilia Mirkin from comment #5)> OK, so ... > > A few facts: > > - GK104 > - Driving 4 monitors > > Question: Are the 2560x1440 and 1920x1200 daisy-chained (hence the "MST" > reference), or is it just that the 2560x1440 monitor's manufacturer name is > "MST", without any reference to Multi-Stream Transport?They are not daisy-chained. I'm not sure about the MST reference. I think this is a regression in X11 1.20. I filed a separate bug about that: https://bugzilla.freedesktop.org/show_bug.cgi?id=108516 (If Hybrid Graphics is enabled, MST reference is gone.) Another odd thing I noticed is, if I start X and then hot plug the monitor, there is no flicker. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/7a869026/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 20:29 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #7 from JM9 <jhnmlkvch9 at gmail.com> --- (In reply to JM9 from comment #6)> (In reply to Ilia Mirkin from comment #5) > > OK, so ... > > > > A few facts: > > > > - GK104 > > - Driving 4 monitors > > > > Question: Are the 2560x1440 and 1920x1200 daisy-chained (hence the "MST" > > reference), or is it just that the 2560x1440 monitor's manufacturer name is > > "MST", without any reference to Multi-Stream Transport? > > They are not daisy-chained. I'm not sure about the MST reference. I think > this is a regression in X11 1.20. I filed a separate bug about that: > https://bugzilla.freedesktop.org/show_bug.cgi?id=108516 > (If Hybrid Graphics is enabled, MST reference is gone.) >Scratch that. I was being confused. The MST reference is still there, but the naming scheme is different.> Another odd thing I noticed is, if I start X and then hot plug the monitor, > there is no flicker.-- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/b2ffd510/attachment-0001.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 20:47 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- So it sounds like there's a DP ports are hard-attached to the NVIDIA chip, which is why you're seeing it as "DP-1-1" for the "optimus" case. It's actually using the outputs attached to the NVIDIA gpu. The "local" DP outputs are probably meant for a dock. Are both the 2560x1440 and 1920x1200 monitors attached via DP? Or are there converters in between? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/cf72af7b/attachment.html>
bugzilla-daemon at freedesktop.org
2018-Oct-23 21:48 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 --- Comment #9 from JM9 <jhnmlkvch9 at gmail.com> --- (In reply to Ilia Mirkin from comment #8)> So it sounds like there's a DP ports are hard-attached to the NVIDIA chip, > which is why you're seeing it as "DP-1-1" for the "optimus" case. It's > actually using the outputs attached to the NVIDIA gpu. The "local" DP > outputs are probably meant for a dock. > > Are both the 2560x1440 and 1920x1200 monitors attached via DP? Or are there > converters in between?They are both connected via dock. 2560x1440 (the only one with the flicker problem) is additionally going through a DP to DVI Dual Link Adapter. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20181023/4190433f/attachment.html>
bugzilla-daemon at freedesktop.org
2019-Dec-04 09:45 UTC
[Nouveau] [Bug 108520] [GK104] MST DisplayPort HiDPI screen flicker
https://bugs.freedesktop.org/show_bug.cgi?id=108520 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #10 from Martin Peres <martin.peres at free.fr> --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/463. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20191204/2b3055c3/attachment.html>
Apparently Analagous Threads
- [Bug 111044] New: Resume up from suspend sometimes freezes system (Optimus/Nouveau)
- Intel Displayport on Centos 7
- Intel Displayport on Centos 7
- [Bug 109631] New: Moving gbm bo from GART to VRAM does not wait for rendering
- Atomic modesetting + DisplayPort MST