On Fri, Mar 05, 2004 at 06:10:38PM +0100, Michel Dänzer wrote: > On Fri, 2004-03-05 at 16:23, Daniel Jacobowitz wrote: > > On Thu, Mar 04, 2004 at 02:31:16PM -0500, Daniel Jacobowitz wrote: > > > I didn't get a backtrace from here; sorry. I killed the X server and > > > restarted it. The restart makes this message appear in dmesg repeatedly: > > > > (gdb) bt > > #0 0xffffe410 in __kernel_vsyscall () > > #1 0x4013ab09 in ioctl () from /lib/tls/i686/cmov/libc.so.6 > > #2 0x0809a6a2 in xf86ioctl () > > #3 0x08276d56 in ?? () > > #4 0x00000007 in ?? () > > #5 0x00006444 in ?? () > > > > Not much help. It calls xf86ioctl again and again. > > The chip has probably locked up.
It looks that way. Is there anything I can do to help track down what the new X is doing that causes it to lock up? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
