On Fri, Jun 30, 2006 at 12:44:45PM +0200, Michel Dänzer wrote: > On Tue, 2006-06-27 at 16:25 +0200, Marcel Sebek wrote: > > On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote: > > > On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote: > > > > > > > > This is the trace with ati driver. I also tried vesa, the trace also > > > > started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, > > > > but it has a few more lines between. > > > > > > Please provide the full log file and try and get a backtrace with gdb. > > > > > > > Full log and gdb bt attached. The backtrace was gained from core > > file because running xserver in gdb resulted in keyboard hard freeze > > (no sysrq). > > Yeah, you can only do that from a remote login, or you end up in a dead > lock where gdb stops execution of the X server, which is what provides > interaction with gdb... > > The backtrace looks input related, and indeed, looking at the log file, > it looks like /dev/input/event1 no longer represents a mouse but a > keyboard, so the X server ends up running without a core pointer and > probably chokes on that. > Yes, exactly. event1/2 is switched in the new kernel. The same happened to me once in the past, but IIRC the xserver printed some reasonable warning about missing core pointer, so I found that easily. I've created a simple udev rule and now have mouse on /dev/input/psmouse. I should have done it when I started using evdev interface. Thank you for your time. -- Marcel Sebek
Attachment:
signature.asc
Description: Digital signature