Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35516 - [linux] 3.9.x - 3.10.x Graphic regression kernel dual screen nvidia card with Display Port
Attached to Project:
Arch Linux
Opened by Torsten Wagner (torwag) - Tuesday, 28 May 2013, 12:15 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 10 October 2013, 10:15 GMT
Opened by Torsten Wagner (torwag) - Tuesday, 28 May 2013, 12:15 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 10 October 2013, 10:15 GMT
|
DetailsDescription:
relevant system components: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1) /proc/cmdline: root=UUID=<long id> rootfstype=ext4 ro systemd.unit=graphical.target fbcon=rotate:3 initrd=EFI\arch\initramfs-linux-fallback.img dual screen set-up via xorg-xrandr 1.4.0-1 and xf86-video-nouveau 1.0.7-1 using DVI and Display Port. When did it happen: Upgrading to linux-3.9.3-1-x86_64 or linux-3.9.4-1-x86_64 cause a disturbance of the screen connected to the Display Port. Screen seems to get wrong syncs or similar. What did I test: Xrandr settings was the same for both screens. The output is distorted already during booting. Distortion appear in emergency console as well. Removing fbcon=rotate:3 from kernel command line (using pivot) did not help What solved the problem: Downgrading kernel to 3.8.8-2-ARCH Steps to reproduce: Use two monitors on a nvidia graphic card one connected via display port Upgrade to kernel 3.9 Reboot |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 10 October 2013, 10:15 GMT
Reason for closing: Upstream
Thursday, 10 October 2013, 10:15 GMT
Reason for closing: Upstream
is there anything I can do to help to fix this?
Kernel 3.9.7-1-ARCH still suffers from the same problem. In the current changelogs for 3.10, I can't find anything which might address this problem.
I think it is a problem with noveau and KMS.
Unfortunately, debugging is a bit tricky due to the fact that it requires reboot (a git bisect is kind of tricky here) for testing (There seems ways without reboot but not sure they address the problem correctly).
Any ideas?
I tested all kernels which came along the pipe up to 3.10.x and all showed the same behavior.
Just now I try to find time to do a git-bisect with a vanilla kernel. If I can find a certain patch as culprit, we might move that bug report
upstream to the kernel and close it here. Pretty sure it should be KMS and kernel related.
I did a git bisect on the kernel for the described issue.
The following commit seems to contain the problem.
# first bad commit: [0a0afd282fd715dd63d64b243299a64da14f8e8d] drm/nv50-/disp: move DP link training to core and train from supervisor
I reported that upstream to the nouveau-people. Let's see what comes down from there.
https://bugs.freedesktop.org/show_bug.cgi?id=67628
You might consider closing the bug here... or keep it open as reference until it is fixed
still not fixed. I talked to the nouveau-devs and the told me they will look into it. However, did not get any feedback yet.
All I can say, it is not fixed yet.