Bug 12093 - [855GM] remote restart X hangs system.
Summary: [855GM] remote restart X hangs system.
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
Depends on:
Reported: 2007-08-21 20:21 UTC by he jiang
Modified: 2007-08-28 22:30 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Kernel log after hanged (62.64 KB, text/plain)
2007-08-21 20:24 UTC, he jiang
no flags Details
Xorg's log (33.86 KB, text/plain)
2007-08-21 20:25 UTC, he jiang
no flags Details
Xorg's config file (3.63 KB, text/plain)
2007-08-21 20:25 UTC, he jiang
no flags Details

Description he jiang 2007-08-21 20:21:26 UTC
When remote to 855gm machine use ssh, start x and quit X, the 855gm's display fall into halt, other operations can't effect on 855gm local, but 855gm can be connected and pinged. 
Then start x again from remote, 855gm hanged, can't be connected and pinged.

On 855gm local, however start X and quit X many times, the problem can't be reproduced.
Comment 1 he jiang 2007-08-21 20:24:05 UTC
Created attachment 11202 [details]
Kernel log after hanged
Comment 2 he jiang 2007-08-21 20:25:04 UTC
Created attachment 11203 [details]
Xorg's log
Comment 3 he jiang 2007-08-21 20:25:35 UTC
Created attachment 11204 [details]
Xorg's config file
Comment 4 Wang Zhenyu 2007-08-21 20:37:21 UTC
try to build xserver with --disable-config-dbus --disable-config-hal
Comment 5 he jiang 2007-08-22 20:18:18 UTC
After rebuild Xserver use these options on 855gm, the bug also exists.
Comment 6 Wang Zhenyu 2007-08-22 20:21:54 UTC
so you should try to attach it to gdb, and get backtrack info in seg fault.
Comment 7 WuNian 2007-08-22 23:42:39 UTC
In my 945GM machine, when I killed X, it also had below backtrace:

xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
[2]+  Exit 84                 xterm
[root@x-945gm ~]# 0: X(xf86SigHandler+0x7e) [0x80b3c9e]
1: [0xffffe420]
2: X [0x80a020c]
3: X(main+0x4cf) [0x806e56f]
4: /lib/libc.so.6(__libc_start_main+0xdc) [0x9be7e4]
5: X(FontFileCompleteXLFD+0xb9) [0x806d861]

Fatal server error:
Caught signal 11.  Server aborting

But X can restart up. So I think the backtrace has nothing to do with the hanged issue on 855GM. The backtrace seems about font library. Maybe we need update some font modules.
Comment 8 Michael Fu 2007-08-23 19:09:39 UTC
Eric suggest to try latest upstream server again..
Comment 9 Wang Zhenyu 2007-08-23 22:03:41 UTC
It seems still dbus problem. Try to remove dbus-devel package, then build xserver with dbus and hal config disabled.
Comment 10 he jiang 2007-08-23 23:13:44 UTC
After disable dbus and hal, rebuild xserver, the bug still exists and following is backtrace infor when kill X:
(gdb) bt
#0  __glXgetActiveScreen (num=0) at glxscreens.c:189
#1  0x080a15e5 in AbortDDX () at xf86Init.c:1102
#2  0x081b4788 in AbortServer () at log.c:406
#3  0x081b4c96 in FatalError (
    f=0x81bdd50 "Caught signal %d.  Server aborting\n") at log.c:552
#4  0x080b3d0d in xf86SigHandler (signo=11) at xf86Events.c:764
#5  <signal handler called>
#6  0x081aa122 in RemoveGeneralSocket (fd=-1) at connection.c:1071
#7  0x080a020c in teardown () at dbus-core.c:90
#8  0x0806e56f in main (argc=2, argv=0xbfd15414, envp=Cannot access memory at address 0x8000007
) at main.c:471
Comment 11 Wang Zhenyu 2007-08-23 23:23:27 UTC
did you do what I said to remove dbus-devel as a workaround?
Comment 12 he jiang 2007-08-24 01:14:59 UTC
dbus-devel is removed, which is dependency of hal.
Then rebuild xserver.
But the bug still exists.
The backtrace is the same as above.
Comment 13 Gordon Jin 2007-08-28 22:30:34 UTC
It's ok with the latest code.

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.