On Mon, 2002-12-02 at 07:14, Michel Dänzer wrote: > On Mon, 2002-12-02 at 06:00, Bret Towe wrote: > > On Sun, 2002-12-01 at 20:23, Bret Towe wrote: > > > On Sun, 2002-12-01 at 15:55, Michel Dänzer wrote: > > > > On Fre, 2002-11-29 at 18:37, Bret Towe wrote: > > > > > last night i installed glaxium (0.5) for the first time > > > > > and was playing it runs great > > > > > however when i move the window it freezes x within a minute > > > > > sometimes even less > > > > > but as long as i dont move the window it plays fine > > > > > > > > Do you keep moving the window until it locks up, or do you move the > > > > window and then let it be, and it will lock up after a while? > > > > > > > i move it once to the location that i wanted it then start to play > > > (wait 3-15s) then freeze > > > > > > > Also, can you log in remotely and see if killing glaxium restores normal > > > > operation? > > > tried that looked like it had already died > > It as in glaxium or the machine? If the former, can you try > glaxium died i tried to recompile it with debuging symbols but no luck ill have to try again later did somehow get sound in glaxium now tho... go fig
> fuser -k /dev/dri/card0 i did try this with glaxium since it stays open now with sound continuing to play in background it freezes the server fully even the mouse wont move after that command > > as normal user? That should kill any leftover processes using the DRM > while keeping the X server alive. > > Although the information below kind of implies a 'real' lockup, not a > 'soft' one. > > > > > > > this is a radeon 7500 (built by ati card) > > > > > pageflipping is enabled > > > > > > > > I don't expect this to make a difference, but can you still try without? > > > will do will let know soon > > > > ok i disabled it and i forgot to move the window this time and it still > > froze > > So it doesn't seem to be related to moving the window after all. > seems not > > 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 > > 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 it would be nice right now if someone else with a 7500 try this out and see if get the same stuff cause this mobo isnt stable its starting to fail its possable it doesnt like somethin this game does but this would be a first for it usally it just doesnt like compiling (over heats or some damned thing) and what would be best way to get a backtrace? get glaxium with debugging symbols? or should i just run gdb on x? > > -- > 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
