Bug 13191

Summary: [855GM TTM]x crash machine with messages"drmOpenDevice: Open failed"
Product: xorg Reporter: Pi, Fengming <fengming.pi>
Component: Driver/intelAssignee: Eric Anholt <eric>
Status: VERIFIED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: jbarnes, zhenyu.z.wang
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log file none

Description Pi, Fengming 2007-11-11 22:53:19 UTC
System Environment:
--------------------------

--Platform: 855gm
--Architecture: 32-bit
--2D driver: git commit ab2055ebb20aa6de121fa377e488ce91913035ae
--3D driver:  Mesa commit9bf5da906fee80ae51c6c20ba59e297f74d77bd9
--DRM:   git commit793cd1dad5e248509a1b09dce7126f236efadb3e 
--Xserver:  git commit f48087b6c33c1f84bf2cfc0744b1c38697321c07
--Kernel: 2.6.22

Bug detailed description:
--------------------------
Start xorg on 855gm then it crash machine and the screen is dark all the time.you only have to reboot to go back to normal status.

Reproduce steps:
X &
Comment 1 Pi, Fengming 2007-11-11 22:54:47 UTC
Created attachment 12472 [details]
xorg log file
Comment 2 WuNian 2007-11-12 18:46:56 UTC
The X and OS hang at drmMMInit function, below is the backtrace:

(gdb) bt
#0  drmMMInit (fd=13, pOffset=8159, pSize=13334, memType=1) at xf86drm.c:2824
#1  0xb7e03638 in i830_allocator_init (pScrn=0x8213b80, offset=0,
    size=134217728) at i830_memory.c:482
#2  0xb7dfd992 in I830ScreenInit (scrnIndex=0, pScreen=0x8222de0, argc=1,
    argv=0xbfcfe6c4) at i830_driver.c:2414
#3  0x0806ce9e in AddScreen (pfnInit=0xb7dfd820 <I830ScreenInit>, argc=1,
    argv=0xbfcfe6c4) at main.c:771
#4  0x080a0f6c in InitOutput (pScreenInfo=0x81ebba0, argc=1, argv=0xbfcfe6c4)
    at xf86Init.c:1067
#5  0x0806d646 in main (argc=1, argv=0xbfcfe6c4, envp=0xbfcfe6cc) at main.c:369
Comment 3 Pi, Fengming 2007-11-21 23:11:40 UTC
this bug has gone with the latest git source

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.