On Mon, 2002-12-02 at 22:04, Bret Towe wrote: > On Mon, 2002-12-02 at 07:14, Michel Dänzer wrote: > > On Mon, 2002-12-02 at 06:00, Bret Towe wrote: > > > > > > > but i ran glaxium from a ssh shell so i could run gdb on it > > > but glaxium didnt have debug symbols but however i did get an error > > > radeonWaitIrq: drmRadeonIrqWait: -16 > > > it appeared 2-3s after x froze > > > > Should be pretty much exactly 3 seconds. :) > > > > > and after reading the thread that Linus started im wondering if this is > > > related > > > > Hardly, this is just the current most prominent symptom of a lockup, as > > the chip obviously no longer generates interrupts when it's locked up. > > You can try RADEON_NO_IRQS=1 RADEON_NO_USLEEPS=1 for different symptoms. > tried that didnt seem to make any diff
Well, you shouldn't get an drmRadeonIrqWait error with these, or something's very wrong. > > > and this might make since due to the fact im using a joystick that is > > > usb but i dont know if its related but the problem usally accors when i > > > move the ship around really fast and that would make the joystick send > > > more stuff at that time > > > but this is just a guess > > > > Does playing with the keyboard make a difference? > doesnt seem to had same effects Then it's probably unrelated to the joystick. > and what would be best way to get a backtrace? get glaxium with > debugging symbols? or should i just run gdb on x? You can't get a backtrace for a lockup, that's one of the bad things about them. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
