linux-kernel - Re: R200 lockup (was Re: DRI/X error resolution)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158900841.3280.12.camel@ix>
Date:	Thu, 21 Sep 2006 23:54:01 -0500
From:	Stephen Olander Waters <swaters@....info>
To:	Ryan Richter <ryan@....solarneutrino.net>
Cc:	linux-kernel@...r.kernel.org, dri-devel@...ts.sourceforge.net
Subject: Re: R200 lockup (was Re: DRI/X error resolution)

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/