On Mon, 2002-10-07 at 11:13, Andrew Gallatin wrote: > > Every so often, my X server locks up. It seems to be in a tight > loop, 95% user time, and making only these ktrace'able calls: > > 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 > 27069 XFree86 0.000039 CALL sigreturn(0xbd9e7b0c) > 27069 XFree86 0.000004 RET sigreturn JUSTRETURN > 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 > 27069 XFree86 0.000015 CALL sigreturn(0xbd9e6e0c) > 27069 XFree86 0.000004 RET sigreturn JUSTRETURN > 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 > > Anybody have a workaround for this? > > The whole system (2.53 Ghz P4) was compiled from sources late last > week... > > Between this, and the Type1 bezier font abort, the state of 5.0 on a > desktop is very sorry indeed. My old alpha running -stable is far > more stable.
Basically what this ktrace output means, from my reading, is that the server is stuck processing some client request and never gets back to it main scheduling loop / goes idle and turns off the alarm. Finding where the server is sitting would be valuable. If you have a hardware cursor and smooth mouse on (it's default) you'll still be able to move the mouse because the mouse response is done in a signal handler, so a busy server doesn't make your mouse stop working. Still wishing I could get a working gdb on an X. -- Eric Anholt <[EMAIL PROTECTED]> http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
