On Sam, 2011-05-07 at 23:54 -0300, Rogério Brito wrote:
>
> 2011/5/6 Michel Dänzer <daen...@debian.org>:
> > Hmm weird, probably an X driver bug. Does the option have any effect on
> > the distortion of 3D apps though?
>
> I reenabled ColorTiling and the weird problems that affected Emacs
> (and other applications) are gone. Should this be filed in any BTS?
> Which one?
For now, I'd settle for an answer to my repeated question about the
effect on 3D apps of disabling tiling. :}
> > Unfortunately, this only shows where the GPU lockup is noticed, not what
> > caused it.
> >
> > Do the lockups occur with radeon.agpmode=-1 (may also require
> > radeon.no_wb=1) as well?
>
> No, with radeon.agpmode=-1, I am able to use the computer OK, with no
> signs of GPU lockup like before, [...]
Does the attached kernel patch avoid the lockups with radeon.agpmode=1 ?
It's only necessary for higher rates with newer revisions of UniNorth,
but maybe it's necessary even for 1x with yours.
> I have not yet tried radeon.no_wb=1 till now. Should I use it?
No, it could only be necessary if radeon.agpmode=-1 wasn't stable.
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
commit 3164afbbeadd64dbeba84fde4ef14261e0abbfc1
Author: Michel Dänzer <daen...@vmware.com>
Date: Wed Mar 16 08:37:57 2011 +0100
agp/uninorth: Fix lockups with radeon KMS and >1x.
diff --git a/drivers/char/agp/uninorth-agp.c b/drivers/char/agp/uninorth-agp.c
index f845a8f..a32c492 100644
--- a/drivers/char/agp/uninorth-agp.c
+++ b/drivers/char/agp/uninorth-agp.c
@@ -80,7 +80,7 @@ static void uninorth_tlbflush(struct agp_memory *mem)
ctrl | UNI_N_CFG_GART_INVAL);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL, ctrl);
- if (uninorth_rev <= 0x30) {
+ if (!mem && uninorth_rev <= 0x30) {
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
ctrl | UNI_N_CFG_GART_2xRESET);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
