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.
-ryan
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
On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> 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. :)
Oh, wow. I had no idea there was a workaround. What kind of
performance hit does that entail? R200 performance is pretty dismal to
begin with, but it would be awfully nice to not have all our
workstations crashing all the time...
I wonder why that works. What chipset do you use? All our machines are
AMD 8151.
I'm about to leave town for several days, but I'll try that when I
return.
Cheers,
-ryan
On 9/22/06, Ryan Richter <[email protected]> wrote:
> On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> > 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. :)
I really think this more AGP related a bug in the driver for the VIA
AGP chipsets what AGP chipset are you guys using?
Dave.
On Fri, Sep 22, 2006 at 03:29:48PM +1000, Dave Airlie wrote:
> On 9/22/06, Ryan Richter <[email protected]> wrote:
> >On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> >> 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. :)
>
> I really think this more AGP related a bug in the driver for the VIA
> AGP chipsets what AGP chipset are you guys using?
AMD 8151 here. I have yet to try Option "BusType" "PCI", so I can't say
if that works here (it'll be a week or so before I have a chance to
try).
-ryan
On Fri, Sep 22, 2006 at 03:29:48PM +1000, Dave Airlie wrote:
> On 9/22/06, Ryan Richter <[email protected]> wrote:
> > On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> > > 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. :)
>
> I really think this more AGP related a bug in the driver for the VIA
> AGP chipsets what AGP chipset are you guys using?
Looking at that bug though, most of the reporters are on AMD64 systems,
which uses amd64-agp, not via-agp. (We leave the chipset GART alone,
and just use the on-CPU one).
This..
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode.
agpgart: X requested AGPx8 but bridge not capable.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
should be fixed in recent Xorg/kernels. There is a v3 8x->4x
fallback failure that some people trigger, but that manifests itself
in other ways with different messages (where it tries to fall
back to 0x mode, and madness ensues), there's a fix for that
in Andrews -mm tree that should be going to Linus RSN.
Other than that, I'm unaware of any outstanding nasties in the
AGP drivers. I'm not really sure what to suggest for further
debugging.
Dave
On Fri, 2006-09-22 at 01:52 -0400, Dave Jones wrote:
> On Fri, Sep 22, 2006 at 03:29:48PM +1000, Dave Airlie wrote:
> > On 9/22/06, Ryan Richter <[email protected]> wrote:
> > > On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> > > > 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. :)
> >
> > I really think this more AGP related a bug in the driver for the VIA
> > AGP chipsets what AGP chipset are you guys using?
>
> Looking at that bug though, most of the reporters are on AMD64 systems,
> which uses amd64-agp, not via-agp. (We leave the chipset GART alone,
> and just use the on-CPU one).
I have the Via K8T8000 chipset (MSI K8T Master2-Far motherboard)
Hrm... the Debian amd64 package in 'unstable' curiously does not include
amd64-agp.ko.
http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-image-2.6.17-2-amd64&version=unstable&arch=amd64&page=3&number=50
However, the i686 version does have amd64-agp.ko.
http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-image-2.6.17-2-686&version=unstable&arch=i386&page=3&number=50
-s
On Fri, Sep 22, 2006 at 09:21:11AM -0500, Stephen Olander Waters wrote:
> On Fri, 2006-09-22 at 01:52 -0400, Dave Jones wrote:
> > On Fri, Sep 22, 2006 at 03:29:48PM +1000, Dave Airlie wrote:
> > > On 9/22/06, Ryan Richter <[email protected]> wrote:
> > > > On Thu, Sep 21, 2006 at 11:54:01PM -0500, Stephen Olander Waters wrote:
> > > > > 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. :)
> > >
> > > I really think this more AGP related a bug in the driver for the VIA
> > > AGP chipsets what AGP chipset are you guys using?
> >
> > Looking at that bug though, most of the reporters are on AMD64 systems,
> > which uses amd64-agp, not via-agp. (We leave the chipset GART alone,
> > and just use the on-CPU one).
>
> I have the Via K8T8000 chipset (MSI K8T Master2-Far motherboard)
>
> Hrm... the Debian amd64 package in 'unstable' curiously does not include
> amd64-agp.ko.
> http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=linux-image-2.6.17-2-amd64&version=unstable&arch=amd64&page=3&number=50
It's probably built-in if the kernel also supports IOMMU.
Dave