linux-kernel - DRM BUG - X fails to start with 2.6.38-rc2+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 22 Jan 2011 09:35:03 +0000
From:	Chris Clayton <chris2553@...glemail.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: DRM BUG - X fails to start with 2.6.38-rc2+

Hi,

I'm not subscribed, so please cc me on any reply,

I've built and installed the latest -git kernel (pulled this morning) and X 
fails to start.  I see the grey X background and, for a split second, what 
looks like the kdm login dialogue box appears before disappearing again. Then 
the screen goes black and the monitor goes into power saving made. I can't 
access consoles with Alt-Fn - the machine is effectively locked and can be 
rcovered only by powering off and then on again.

The only diagnostics I can find in the logs is at the end of/var/log/kernel:

Jan 22 08:20:08 upstairs kernel: r8169 0000:02:00.0: eth0: link up
Jan 22 08:20:17 upstairs kernel: [drm] Initialized drm 1.1.0 20060810
Jan 22 08:20:19 upstairs kernel: pci 0000:00:02.0: PCI INT A -> GSI 16 (level, 
low) -> IRQ 16
Jan 22 08:20:19 upstairs kernel: pci 0000:00:02.0: setting latency timer to 64
Jan 22 08:20:19 upstairs kernel: ioremap error for 0xbdce0000-0xbdce3000, 
requested 0x10, got 0x0
Jan 22 08:20:19 upstairs kernel: [drm] Supports vblank timestamp caching Rev 1 
(10.10.2010).
Jan 22 08:20:19 upstairs kernel: [drm] Driver supports precise vblank timestamp 
query.
Jan 22 08:20:19 upstairs kernel: [drm] Initialized i915 1.6.0 20080730 for 
0000:00:02.0 on minor 0
Jan 22 08:20:37 upstairs kernel: BUG: unable to handle kernel NULL pointer 
dereference at 00000194
Jan 22 08:20:37 upstairs kernel: IP: [<f87c1aae>] 
drm_calc_vbltimestamp_from_scanoutpos+0x3e/0x4b0 [drm]

/var/log/Xorg.0.log appears not to have been written to because it contains what 
appears to be only random data rather than the usual text.

The graphics-related lspci output shows:

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated 
Graphics Controller (rev 03) (prog-if 00 [VGAcontroller])
        Subsystem: Giga-byte Technology Device d000
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e1000000 (64-bit, non-prefetchable) [size=4M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at e000 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features

00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated 
Graphics Controller (rev 03)
        Subsystem: Giga-byte Technology Device d000
        Flags: bus master, fast devsel, latency 0
        Memory at e1400000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [d0] Power Management version 2

All works fine with 2.6.37 .

Please let me know if any additional diagnostics are needed or if you want any 
patches testing.

Thanks in advance

Chris

-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/