View Single Post
Old 08-06-08, 09:58 PM   #18
devsk
Registered User
 
Join Date: Jun 2006
Posts: 46
Default Re: Spawning new session leads to crash

Quote:
Originally Posted by drbloed View Post
Code:
...
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x49019a]
1: /lib/libc.so.6 [0x3594833170]
2: /usr/lib64/xorg/modules/drivers//nvidia_drv.so [0x7ff80b0726b8]

Fatal server error:
Caught signal 11.  Server aborting
...
I get the same stack for the X server crash. But here is a twist and a possible hint at the problem. The problem (and the same stack) happens in two scenarios:
1. Start a second session on vt8 under a different. First session will die randomly after some time. Reproducible every time.
2. Resume from suspend-to-ram. After successful resume, the session is thrown back to KDM. Some of the times.

The commonality is that the crash is seen if USB was too slow to respond during resume and mouse wasn't ready and evdev returned ENOENT error for the device or in second case if the device was busy (RESOURCE BUSY is seen in the log, because the current session, which is session #2, is using it) for keyboard or mouse and evdev returned error EBUSY. Are there folks here seeing this crash and not using evdev?

Maybe NVIDIA folks need to see what nvidia driver's interaction with evdev is. Recent Xorg changes have sort of forced evdev on people. And I think something needs to change in the driver to handle different error return codes.

-devsk

PS: X saves the previous log in Xorg.0.log.old. So, you do have access to previous log file as well.
devsk is offline   Reply With Quote