Created attachment 40352 [details]
I've just tried kernel 2.6.37-rc6 and Intel HD graphics driver seems to be totally broken - see the attached photo.
When I tried to switch to a text console - the screen became entirely black and I couldn't switch to the broken X console any longer.
The computer was not hanging, but X server froze completely.
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
Subsystem: ASRock Incorporation Device 0042
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-
Interrupt: pin A routed to IRQ 42
Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at c000 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0500c Data: 4179
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
Kernel driver in use: i915
Kernel modules: i915
on Intel Core i5 650 CPU.
Kernel 126.96.36.199 works fine here.
It's a modesetting issue, for which we want the usual logs: drm.debug=0xe dmesg, Xorg.log and xrandr --verbose.
And a slightly finer granularity than 188.8.131.52 vs 2.6.37-rc6 would be appreciated.
X.org log on 2.6.36 and 37 is absolutely the same. Non-debug dmesg is here:
[ 5.364259] Linux agpgart interface v0.103
[ 5.445758] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
[ 5.445831] agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
[ 5.446348] agpgart-intel 0000:00:00.0: detected 262144K stolen memory, trimming to 32768K
[ 5.473023] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 5.550652] [drm] Initialized drm 1.1.0 20060810
[ 5.939576] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6.133302] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[ 6.191062] fb0: inteldrmfb frame buffer device
[ 6.191063] drm: registered panic notifier
[ 6.191088] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 5.279660] Linux agpgart interface v0.103
[ 5.488380] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
[ 5.489116] agpgart-intel 0000:00:00.0: detected 262140K stolen memory, trimming to 32768K
[ 5.540013] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 5.912777] [drm] Initialized drm 1.1.0 20060810
[ 6.223105] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6.223112] i915 0000:00:02.0: setting latency timer to 64
[ 6.247356] [drm] detected 255M stolen memory, trimming to 32M
[ 6.247407] i915 0000:00:02.0: irq 42 for MSI/MSI-X
[ 6.247414] [drm] set up 32M of stolen space
[ 6.534732] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[ 6.648274] fb0: inteldrmfb frame buffer device
[ 6.648275] drm: registered panic notifier
[ 6.648324] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Created attachment 40362 [details]
2.6.37-rc6 dmesg with drm.debug=0xe
Created attachment 40372 [details]
Probably that was the weirdest timing issue I've ever seen in my life. On the second reboot everything returned back to normal (under 2.6.37-rc6).
I will reopen this bug report if I manage to reproduce the problem.
Created attachment 40832 [details]
tty1 after a cold boot (not easily reproducible)
It seems like there's some sort of race condition in 2.6.37 i915 drivers.
Today after powering on I've booted straight to 2.6.37 and the image on the screen was distorted and the display was blinking intermittently until it blacked out completely.
As far as I can see there are zero unusual messages in dmesg or Xorg.0.log.
So.. should this bug report be reopened?
(In reply to comment #7)
> So.. should this bug report be reopened?
I can no longer reproduce it using 2.6.37-rc8 even after a cold boot, so let's say it's been fixed :)