http://bugs.xfree86.org/show_bug.cgi?id=271 ?

That seams like the one, I'm on an 8500 though.  When I play quake3 it stopes, the 
soundcard
loopes over it's dma like a broken record. Then quake3 exits(!0), don't know why I 
hope the DRI
exited cause the card was hung.  Why dose X not quit?  When I ssh and run reboot It 
never dose,
and hangs with no network responce.

I'd like to fix this in baby steps, how do I get X to stop so that I can reboot? Can 
we make X
exit with a status(32?) letting our Xwrapper know it's time to ask the user reboot?  I 
think I can
still print, heh.

I know I'v asked for this before and every one is more concerned with making the DRI 
not hang the
card.  Now after about a year it's time to think that will still not happen soon.  I 
have made
patches for DRI, but thay never seam to get maintained.

I realy would like to help, but I'm realy more concerned with playing games.  It's not 
easy to
think about debugging and capturing the flag at the same time.  However withought DRI 
there is no
games, so I must spend some time debugging and sending in bug reports.  How do I make 
the time I
spend debuging more productive?  I play quake3 alot(or at least I'd like to have time 
to play) and
It would help me to know how to play in a way that I'm helping ought.

--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Thu, 2003-08-07 at 12:09, Mike Mestnik wrote:
> > This is what I get on an strace of the now hung X server.
> > --- SIGALRM (Alarm clock) @ 0 (0) ---
> > sigreturn()                             = ? (mask now [])
> > ioctl(6, 0x6444, 0)                     = -1 EBUSY (Device or resource busy)
> > ioctl(6, 0x6444, 0)                     = -1 EBUSY (Device or resource busy)
> > ioctl(6, 0x6444, 0)                     = -1 EBUSY (Device or resource busy)
> > <Back to top>
> > 
> > ps tells me that quake3 exited with a non-zero status, the || in my 
> > script gets hung, and not being able to connect to tell me what happend.
> > 
> > There are no 3d apps running.  I read in another thread that the DRM 
> > is soposed to clear things up if the app closes the inode?  Unless 
> > some one else knowes what's wrong I'l start to look there.
> 
> This is a different issue. The X server loops calling the RADEON_CP_IDLE
> ioctl, so it has the hardware lock, but the chip has probably locked up.
> Could be related to http://bugs.xfree86.org/show_bug.cgi?id=271 ?
> 
> 
> PS: It might be a good idea to provide a bit more context next time...
> 
> -- 
> Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
> Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to