Re: Xwindow Failed Suddenly
On Mon, Mar 23, 2009 at 12:43:48 +0700, Zaki Akhmad wrote:
> I am using Debian Testing. While I am using computer on my xwindow,
> suddenly the xwindow it blink and failed. And I should restart my
> computer if I want my xwindow works again. The strange behaviour is,
> if I restart from terminal (# restart) then the splash works fine.
> Then it shows an error message. Here's my Xorg.log. Anybody can
> give me a hint?
> X.Org X Server 1.4.2
> Release Date: 11 June 2008
> X Protocol Version 11, Revision 0
> Build Operating System: Linux Debian (xorg-server 2:1.4.2-11)
> Current Operating System: Linux zara 2.6.26-1-686 #1 SMP Sat Jan 10
> 18:29:31 UTC 2009 i686
> Build Date: 20 February 2009 03:06:29AM
> (--) PCI:*(0:2:0) Intel Corporation Mobile 915GM/GMS/910GML Express
> Graphics Controller rev 3, Mem @ 0xb0080000/19, 0xc0000000/28,
> 0xb0000000/18, I/O @ 0x1800/3
> (--) PCI: (0:2:1) Intel Corporation Mobile 915GM/GMS/910GML Express
> Graphics Controller rev 3, Mem @ 0x88000000/19
> (II) intel(0): Creating default Display subsection in Screen section
> "Default Screen" for depth/fbbpp 24/32
> (==) intel(0): Depth 24, (--) framebuffer bpp 32
> (==) intel(0): RGB weight 888
> (==) intel(0): Default visual is TrueColor
> (II) intel(0): Integrated Graphics Chipset: Intel(R) 915GM
> (--) intel(0): Chipset: "915GM"
> (--) intel(0): Linear framebuffer at 0xC0000000
> (--) intel(0): IO registers at addr 0xB0080000
> (II) intel(0): 2 display pipes available.
> (==) intel(0): Using EXA for acceleration
> (==) intel(0): Enabling EXA render acceleration
> Error in I830WaitLpRing(), timeout for 2 seconds
It looks like this problem has been around for a while:
> (II) intel(0): [drm] removed 1 reserved context for kernel
> (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8eba000 at 0xb7ae8000
> (II) intel(0): [drm] Closed DRM master.
> Fatal server error:
The intel driver seems to be a bit flaky at the moment. (I have run into
problems with my 82Q963/Q965 card as well.)
You can try to switch to XAA as suggested in the bug report.
You can save the following:
<device screen="0" driver="intel">
<option name="vblank_mode" value="0" />
into a file named ".drirc" in your home directory and test if this
improves the situation. (I found some upstream bug reports suggesting to
set vblank_mode=0; however, this does not really make a difference for
You can wait for the next version of the intel driver in Debian or try
the current upstream snapshot.
You can try if a newer or older kernel improves the stability.
Regards, | http://users.icfo.es/Florian.Kulzer