Bug 85865 - [855GM] i915 black screen on LVDS
Summary: [855GM] i915 black screen on LVDS
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-04 16:25 UTC by Orion Poplawski
Modified: 2017-07-24 22:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (17.54 KB, text/plain)
2014-11-04 16:25 UTC, Orion Poplawski
no flags Details
dmesg (50.03 KB, text/plain)
2014-11-04 16:26 UTC, Orion Poplawski
no flags Details
dmesg drm.debug=6 (201.64 KB, text/plain)
2014-11-05 00:07 UTC, Orion Poplawski
no flags Details

Description Orion Poplawski 2014-11-04 16:25:46 UTC
Created attachment 108906 [details]
Xorg.0.log

Dell Latitude X300.  On startup, X vt is completely black, no cursor.

3.17.2-300.fc21.i686
xorg-x11-drv-intel-2.99.916-2.fc21.i686
mesa-dri-drivers-10.3-1.20140927.fc21.i686

00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Dell Latitude X300
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Memory at e0000000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at 1800 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power Management version 1
        Kernel driver in use: i915
        Kernel modules: i915

# dmesg | grep drm
[    2.882322] [drm] Initialized drm 1.1.0 20060810
[    3.316536] [drm] Memory usable by graphics device = 128M
[    3.316544] [drm] Replacing VGA console driver
[    3.320973] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.320981] [drm] Driver supports precise vblank timestamp query.
[    3.386614] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[    3.404587] [drm] initialized overlay support
[    3.448627] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[    3.484557] fbcon: inteldrmfb (fb0) is primary device
[    4.204177] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    4.204795] [drm] Initialized i915 1.6.0 20140725 for 0000:00:02.0 on minor 0
[    4.273772] [drm:i9xx_check_fifo_underruns] *ERROR* pipe B underrun
[    4.314672] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[    4.359447] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[    6.576672] SELinux: initialized (dev drm, type drm), not configured for labeling
[   61.106599] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[   61.150541] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[   65.267186] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
[   65.267197] [drm:i8xx_irq_handler] *ERROR* pipe A underrun
[   65.333986] [drm:i8xx_irq_handler] *ERROR* pipe A underrun
Comment 1 Orion Poplawski 2014-11-04 16:26:22 UTC
Created attachment 108907 [details]
dmesg
Comment 2 Chris Wilson 2014-11-04 21:29:44 UTC
Can you try with /etc/X11/xorg.conf.d/intel.conf:

Section "Device"
  Identifier "igfx"
  Option "DRI" "2"
EndSection
Comment 3 Orion Poplawski 2014-11-04 21:40:49 UTC
Thanks, but no effect.  The underrun messages appear very early in the boot, so it appear that things go awry quickly.
Comment 4 Chris Wilson 2014-11-04 21:44:27 UTC
Ok, I was hoping that the underruns would be transient, and you just had an easy userspace issue to fix...

Next up is a drm.debug=6 dmesg.
Comment 5 Orion Poplawski 2014-11-05 00:07:02 UTC
Created attachment 108920 [details]
dmesg drm.debug=6
Comment 6 Daniel Vetter 2014-11-26 16:27:44 UTC
Is this a regression somehow? We've had i855gm support since ages ...
Comment 7 Orion Poplawski 2014-11-26 16:45:31 UTC
Yeah, this used to work fine back in the Fedora 17 days.  Unfortunately I don't know when this broke as the machine was not in use for a while.
Comment 8 Daniel Vetter 2014-11-26 17:04:33 UTC
Fedora 3.17 is about kernel 3.0. So you could just grab that one and double-check it works, then start the bisect. Becuase bisect only takes log(num_commits) test points it will not take much longer than bisecting just one kernel release (14 tests usually for one kernel release, 4-5 more for 3.0 till today).
Comment 9 Jesse Barnes 2015-03-09 22:09:49 UTC
Timing out on this one.  Please re-open with bisect results if this is still an issue.


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.