On Tue, 2010-03-30 at 05:34 +0100, Dave Airlie wrote: 
quoted text
> 
> Original pull req below + reverts the fallback placement change which had 
> a side effect of causing more lockups on some AGP systems (this is a bug in 
> the AGP drivers that needs to be tracked down), [...]

While I was able to work around the lockups by making the AGP driver
never unbind a GTT entry, I think it's rather a radeon issue - how is
the AGP driver supposed to know when it's safe to unbind an entry?

That change had lots of other issues anyway, thanks for reverting it.


quoted text
> [...] and I've merged Jerome's GPU recovery code, as I'd much rather
> users had some of hope of recovering from their GPU locking up than a
> dead box. It seems to work for quite a lot of people that have tested
> it, and it won't make a GPU lockup problem worse.

Unfortunately, that's not true in all cases. The change itself mentions
that the new reset code is unreliable for R3xx generation GPUs, and
indeed with my RV350 it now turns my box into a brick immediately on a
GPU lockup most of the time whereas previously it was usually able to
recover at least in some cases, e.g. falling back to PCI mode after
trying to use a non-working AGP transfer mode.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/