Created attachment 20404 [details] lsmod X doesn't start. After startx, I get the following message: waiting for X server to shutdown XIO: fatal IO error 104 (message in russian, something like, "connection dropped by another side") on X server ":0:0" after 48068 request (48065 known processed) with 0 events remaining. error setting MTRR (base=0xe0000000, size=0x10000000, type=1) Invalid argument (22)
Created attachment 20405 [details] lspci
Created attachment 20406 [details] xorg.conf
Created attachment 20407 [details] xorg version
Created attachment 20408 [details] Xorg.0.log
Linux 2.6.27.6, libdrm 2.4.1, xf86-video-intel 2.5.1
Does this ever worked with older driver?
Looks like xserver caused fault, could you run it in gdb or ssh from another machine to get backtrack of the fault?
(In reply to comment #6) > Does this ever worked with older driver? > server 1.5.3, vesa 2.0.0.0 error setting MTTR (base=0xe0000000, size=0x007f0000, type=1) server 1.5.3, intel 2.4.3 error setting MTRR (base=0xe0000000, size=0x10000000, type=1) server 1.4.3, intel 2.4.3, libdrm 2.3.1 (didn't compile with libdrm 2.4.1) Waiting for X server to shutdown XIO: fatal IO error 11 ( The resource is temporarily unavailable) on X server "0:0" FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1, fixing server 1.4.3, vesa 1.3.0 Same message + monitor print "Sync out of Range" server 1.4.3, intel 2.5.1, libdrm 2.4.1 Same + "Sync out of Range" But, it's work in Debian (x86). xserver-xorg-video-intel 2.1.0-2 xserver-xorg-core 1.3.0.0.dfsg-12 Seems, there is no problem with intel driver (In reply to comment #7) > Looks like xserver caused fault, could you run it in gdb or ssh from another > machine to get backtrack of the fault? > I haven't skill to use debugger (i'v just run gdb ant try to start /usr/bin/X and got error) and possibility connect via ssh
Gordon, could we run a regression test of current driver on G33? I don't have G33 machine around now. Denis, is failure still existing? Could you turn "ModeDebug" option in Device section of xorg.conf and send the X log?
(In reply to comment #9) > Gordon, could we run a regression test of current driver on G33? I don't have > G33 machine around now. Zhenyu, our G33(x-bl1 and x-bl2) have never had this problem.
Denis, could you try intel driver 2.4.3 release? And please send dmesg log and turn on ModeDebug option in xorg.conf for X log.
(In reply to comment #8) > (In reply to comment #6) > > Does this ever worked with older driver? > > > server 1.5.3, vesa 2.0.0.0 > error setting MTTR (base=0xe0000000, size=0x007f0000, type=1) > server 1.5.3, intel 2.4.3 > error setting MTRR (base=0xe0000000, size=0x10000000, type=1) > server 1.4.3, intel 2.4.3, libdrm 2.3.1 (didn't compile with libdrm 2.4.1) > Waiting for X server to shutdown XIO: fatal IO error 11 ( > The resource is temporarily unavailable) on X server "0:0" > FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1, fixing > server 1.4.3, vesa 1.3.0 > Same message + monitor print "Sync out of Range" > server 1.4.3, intel 2.5.1, libdrm 2.4.1 > Same + "Sync out of Range" > But, it's work in Debian (x86). > xserver-xorg-video-intel 2.1.0-2 > xserver-xorg-core 1.3.0.0.dfsg-12 > Seems, there is no problem with intel driver > (In reply to comment #7) > > Looks like xserver caused fault, could you run it in gdb or ssh from another > > machine to get backtrack of the fault? > > > > I haven't skill to use debugger (i'v just run gdb ant try to start /usr/bin/X > and got error) and possibility connect via ssh > Denis, 1)are you using the same kernel on all test combination you listed above? 2)would you please attach your mtrr? you can get it via 'cat /proc/mtrr'. We need one file of your successful case ( xserver 1.3.0 + intel 2.1.0 ), and the failed case ( xserver 1.5.3 + intel 2.5.1 ) 3)could you please tell us video related items in your BIOS setting ( press F1, F2 or Del to enter during boot, depends on which bios vendor provide the bios)?
Looks we're losing Denis for this? ping again...
Denis, still haven't tried? I'd like to close this, as it blocks our Q4 release, but we can't see it. Please try recent release, reopen if this still fails for you.
I'm sorry, that i didn't report about problem (lots of problems IRL, really). Now, it seems, i found problem, why xserver hang
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.