From: Stephen Olander Waters <swaters@luy.info>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: R200 lockup (was Re: DRI/X error resolution)
Date: Thu, 21 Sep 2006 23:54:01 -0500 [thread overview]
Message-ID: <1158900841.3280.12.camel@ix> (raw)
In-Reply-To: <20060922043801.GE16939@tau.solarneutrino.net>
On Fri, 2006-09-22 at 00:38 -0400, Ryan Richter wrote:
> On Thu, Sep 21, 2006 at 11:23:08PM -0500, Stephen Olander Waters wrote:
> > Hey,
> >
> > Did they ever fix that bug you reported here?
> > http://lkml.org/lkml/2005/5/11/121
> >
> > I'm having the same problem! Argh!
>
> No, sad to say it still happens to us too. Argh is right!
>
> I'll cc this to dri-devel and lkml in case anyone wants to try hunting
> the bug again.
>
> FWIW, I'm still seeing the ioctl(5, 0x6444, 0) / SIGALARM behavior I
> reported originally. This has continued to happen regularly with all
> 2.6 kernels up to 2.6.17.6 and Xfree/X.org up to 6.9.
Here is the bug I'm working from (includes hardware, software, etc.):
https://bugs.freedesktop.org/show_bug.cgi?id=6111
DRI will work if you set: Option "BusType" "PCI" ... but that's not a
real solution. :)
-s
next prev parent reply other threads:[~2006-09-22 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1158898988.3280.8.camel@ix>
2006-09-22 4:38 ` R200 lockup (was Re: DRI/X error resolution) Ryan Richter
2006-09-22 4:54 ` Stephen Olander Waters [this message]
2006-09-22 5:16 ` Ryan Richter
2006-09-22 5:29 ` Dave Airlie
2006-09-22 5:33 ` Ryan Richter
2006-09-22 5:52 ` Dave Jones
2006-09-22 14:21 ` Stephen Olander Waters
2006-09-22 15:39 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158900841.3280.12.camel@ix \
--to=swaters@luy.info \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@tau.solarneutrino.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.