Created attachment 43440 [details] 2.6.37 dmesg 2.6.36 works, 2.6.37 does not; issue is that internal display on a Dell Latitude E6510 becomes blank when KMS is loaded - X thinks everything is fine and keeps the monitor as the primary (I also have an external 22' Dell LCD monitor as a secondary) bisection points to: --- fe224bb7e12f1ea9a785ec942bc5d59950543888 is the first bad commit commit fe224bb7e12f1ea9a785ec942bc5d59950543888 Author: Ben Skeggs <bskeggs@redhat.com> Date: Mon Sep 27 08:29:33 2010 +1000 drm/nouveau: enable enhanced framing only if DP display supports it Reported-by: Adam Jackson <ajax@redhat.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com> :040000 040000 b7c4a355f61feea4e8937678b7114f10ecbde9e2 a6e97b63576d4ea0628114824e1f54ca397417e5 M drivers --- video card is: --- 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E6510 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at e2000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at e0000000 (64-bit, prefetchable) [size=32M] Region 5: I/O ports at 7000 [size=128] Expansion ROM at e3000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [78] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 <4us ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [b4] Vendor Specific Information <?> Capabilities: [100] Virtual Channel <?> Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information <?> Kernel driver in use: nouveau Kernel modules: nouveau --- xrandr output follows - (external monitor is connected using DVI regardless what xrands says) xrandr (with 2.6.37 - not working): --- Screen 0: minimum 320 x 200, current 3280 x 1050, maximum 8192 x 8192 eDP-1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1600x900 60.0*+ 40.0 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 connected 1680x1050+1600+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.9*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) --- xrandr (with 2.6.36 - working): --- Screen 0: minimum 320 x 200, current 3280 x 1050, maximum 8192 x 8192 eDP-1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1600x900 40.0* 1152x864 39.9 1024x768 39.9 800x600 39.6 640x480 39.9 720x400 39.6 640x400 39.3 640x350 39.3 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 connected 1680x1050+1600+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 59.9*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) ---
I wouldn't be certain this commit is the culprit yet. That commit has a typo which would also mess things up, and was fixed by 85341f27b49833325f97580edcd687b4d90bb30b.
(In reply to comment #1) > I wouldn't be certain this commit is the culprit yet. That commit has a typo > which would also mess things up, and was fixed by > 85341f27b49833325f97580edcd687b4d90bb30b. ok, but neither 2.6.37 nor 2.6.38-rc4-git8 work for me, even if they have the above commit. You probably only mean that the bisection might be misleading due to the above, but where does this leave me? what are the next steps I can take to get around that (if any)? some git-fu pointers would be highly appreciated, as I'm just learning the ropes... In the meantime, I'll try building a kernel based on 85341f27b49833325f97580edcd687b4d90bb30b and see what I get.
(In reply to comment #1) > I wouldn't be certain this commit is the culprit yet. That commit has a typo > which would also mess things up, and was fixed by > 85341f27b49833325f97580edcd687b4d90bb30b. ok, so you were right, 85341f27b49833325f97580edcd687b4d90bb30b works here. I'll start a new bisect with 85341f27b49833325f97580edcd687b4d90bb30b as the good and v2.6.37 as the bad and report back..another 13 steps..doh.
(In reply to comment #3) .. > I'll start a new bisect with 85341f27b49833325f97580edcd687b4d90bb30b as the > good and v2.6.37 as the bad and report back..another 13 steps..doh. due some hardware related problems I had the internal display swapped with a new one (the internal display was occasionally flickering badly), and now the situation is completely upside down: 2.6.37 works, while 2.6.36 doesn't anymore. The flickering display problem was going on for some time, even back in the 2.6.35 and 2.6.36 times, and it was manifesting even during BIOS POST, hence the thinking that it was a hw problem. However, now I'm thoroughly confused about the current situation. Is the newer display different and triggers different (inverse) behavior? I can't see any meaningful difference in dmesg output of 2.6.37 between working and non working...
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report. In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one. Thanks, The Nouveau Team
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.