Hide Forgot
Created attachment 532826 [details] Xorg.0.log Description of problem: Did a fresh install of F16 on a Lenovo X200. When used in the docking station with a monitor connected via the displayport all output goes green as soon as trying to login. The way to get around this is to run pm-hibernate and start the computer back up. I suspect it is related to something being setup by the BIOS which isn't done by the X driver. This bug was present in F14 as well, but there it only happened if I had been running it outside the dock and then plugged it into the dock. In F16 the display seems to get reset between the login chooser and the actual display. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.16.0-2.fc16.x86_64 How reproducible: Every time Steps to Reproduce: 1. Install F16 on an X200 2. Plug it into a dock with a monitor connected via dp 3. Watch the unusable green screens Actual results: Expected results: Additional info:
Ok, this is just getting worse :( It shows up that the green screen comes back when I switch to another system using my hdmi kvm switch. The moment I switch back to the laptop display, it turns green.....
[jes@red-feather ~]$ lspci -nn -s 0:2 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
Created attachment 532870 [details] dmesg output from drm.debug=4
Adam, Is the provided info sufficient or want me to try and extract more data? As long as this bug is present, F16 is completely unusable for me unfortunately :( Jes
What kernel is this with? In particular, do you see this with 3.1.5? (Might not be built in koji yet, if you don't mind doing a local build without drm-intel-make-lvds-work.patch that's equivalent for me.)
Adam, This is with whatever was in F16 at the time I reported the bug. I have to admit I don't remember the kernel version off-hand - but I will try and run the latest updates and try again. I can try and build a kernel without that patch as well and see if it makes any difference. I will get back to you. Jes
It happens with 3.1.4 - I will have to try and rebuild without the patch and see if it makes a difference.
Also try toggling these two bool options in xorg.conf: --- Section "Device" Identifier "intel" Driver "intel" Option "Tiling" "1" Option "LinearFramebuffer "0" EndSection --- You should be able to just use that section as your xorg.conf if you don't already have one. The defaults are what I've given here.
Tried again with 3.1.5 which doesn't have the make-lvds-work patch - it shows the same problem :( I will try fiddling with the xorg settings next. Cheers, Jes
Adam, I tried playing around with the variables, however when I flip both of them the X server doesn't even start. That said, I think this problem is more likely to be in kms - yesterday I hit the problem again during boot, and was presented with a green screen when I was prompted for the password for my encrypted partition during boot. Cheers, Jes
Ok this is getting worse. I now also see this problem occasionally on my IvyBridge system after I installed Rawhide on it. It doesn't happen every time, I may have to try a couple of times switching back and forth between systems using my HDMI KVM switch. Jes
I just tried a current Linus kernel on my x200s, docked, with a DP monitor plugged in and things look ok. The fact that this also happens on your IVB, which shares no display hardware with the GM45 makes me think that maybe your monitor is having trouble rather than the driver... intel_reg_dumper might help here. Do you see any register differences between the green and working states on either machine?
Jesse, I have been thinking that too - but the bizarre thing with the ivybridge box is that I have only seen the green effect with it when running rawhide. I never saw it with Fedora 15 or 16, whereas it happens even with Fedora 14 on the X200. Where do I find intel_reg_dumper? I can try that on both systems with and without the green. Also note that it doesn't happen if I boot with the monitor connected. With the X200 it happens if I boot and then plug it into the dock, and with the ivybridge it happens when I switch to it using my HDMI KVM switch. Note the ivybridge box is connected via HDMI, not DP. The monitor is a Dell SP2309W FWIW. Cheers, Jes
intel_reg_dumper is part of the intel-gpu-tools package (you can get it at git.freedesktop.org if you can't find a packaged version). Sounds like the issue isn't DP specific then... I wonder if we're screwing up the palette loads somehow and occasionally racing?
Created attachment 564683 [details] ivy reg dump
Jesse, Sorry for the slow response - I managed to bbq my docking station and just moved the ivy box around so it was close enough to the monitor that I could hook it up again. I tried intel_reg_dumper before and after the display went green and when I diff the two, there are zero differences :( I have attached a reg dump of this box which is wired up via hdmi through an hdmi kvm switch to my monitor. Cheers, Jes
Some more data: 1) Tried removing the HDMI KVM switch and connect my laptop directly to the monitor. Still goes green. 2) Tried connecting to the monitor via DVI (ie. DP->HDMI->DVI). Same, still goes green.
Caved in and got hold of another monitor as this was making it impossible for me to work :( New is a cheapo BenQ, and with it there is no green problem when I re-dock my laptop. It looks like the Intel drivers don't like whatever EDID info it got back from my old Dell ..... Jes
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.