Bug 17711

Summary: [mesa_7_2_branch] X->VT causes X crash with 'fenced' assertion failed
Product: Mesa Reporter: lin, jiewen <jiewen.lin>
Component: Drivers/DRI/i915Assignee: Eric Anholt <eric>
Status: VERIFIED FIXED QA Contact:
Severity: critical    
Priority: highest CC: dri-devel, haihao.xiang, sndirsch
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 17596    
Attachments: Xorg.0.log
xorg.conf

Description lin, jiewen 2008-09-22 02:16:42 UTC
Created attachment 19090 [details]
Xorg.0.log

System Environment:
--------------------------
--Platform: 945gm
--Architecture(32-bit,64-bit,compatiblity): 32-bit
--2D driver: master 071937ae577db67a9b5760bd4c2c4b61a8194822
--3D driver: mesa-7_2_branch 35fe0e56e6f6b45ceea0c3d43be7596c1ea44e00
--DRM: shipped with kernel 2.6.27-rc5
--libdrm: master 8ca06eb492f861dbf049a2e104e4e2a5ba814c13
--Xserver: 1.5release
--Kernel: 2.6.27-rc5
--Display connector: LVDS

Bug detailed description:
--------------------------
Started X , and switch VT, X crash with infos:

X: intel_bufmgr_fake.c:1302: intel_bufmgr_fake_evict_all: Assertion `((&bufmgr_fake->fenced)->next == (&bufmgr_fake->fenced))' failed.
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xinit:  connection to X server lost.

Reproduce steps:
----------------
1 xinit &
2 chvt 1
Comment 1 lin, jiewen 2008-09-22 02:17:19 UTC
Created attachment 19091 [details]
xorg.conf
Comment 2 Gordon Jin 2008-09-22 06:34:18 UTC
This can also be triggered by X exit or suspend/resume.
Comment 3 Gordon Jin 2008-09-25 04:27:09 UTC
This works fine with the latest code, maybe fixed in libdrm.
Comment 4 Stefan Dirsch 2008-09-25 05:50:31 UTC
(In reply to comment #3)
> This works fine with the latest code, maybe fixed in libdrm.

With which libdrm commit did you test?

Comment 5 Gordon Jin 2008-09-25 06:08:36 UTC
libdrm master tip: 2db8e0c8ef8c7a66460fceda129533b364f6418c

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.