On Tue, 2005-03-15 at 11:53 -0500, Dave Jones wrote:
On Tue, Mar 15, 2005 at 04:15:42PM +, Dave Airlie wrote:
I might get time to do a code review, my main worry is that all the
problems reported with those patches in -mm made it into the patchset
that
went into
On Mon, 2005-03-14 at 15:32 +1100, Paul Mackerras wrote:
Andrew Clayton writes:
2.6.11-bk2 OK
2.6.11-bk3 Lockup
Have you tried the most recent kernel? There were some changes to the
It was still broken with -bk9.
AGP code that caused it to oops for me. Linus took my patch to fix
On Mon, 2005-03-14 at 15:32 +1100, Paul Mackerras wrote:
Have you tried the most recent kernel? There were some changes to the
AGP code that caused it to oops for me. Linus took my patch to fix
that this last weekend.
2.6.11-bk10 is a slight improvement.
When X starts the screen goes
On Tue, 2005-03-15 at 10:53 +1100, Benjamin Herrenschmidt wrote:
[snip]
You are using radeonfb ? if yes, try without and let me know.
Just using the basic vga console.
Ben.
Andrew
---
SF email is sponsored by - The IT Product Guide
in the
kernel stops this from happening.
This is an UP AMD Athlon 1800+ XP (VIA chipset) with an AGP Radeon
9200SE under Fedora Core 3.
See my earlier post lkml for more details...
http://www.ussg.iu.edu/hypermail/linux/kernel/0503.1/1096.html
Cheers,
Andrew Clayton
On Mon, 2005-03-14 at 01:32 +0100, Jerome Glisse wrote:
Maybe the lockup you experiment is linked with the lockup
Adam gets. Adam have you upgraded you kernel recently ?
Maybe a 2.6.10 or even previous one could fix this. Thus
To clarify:
2.6.11-bk2 OK
2.6.11-bk3 Lockup
Cheers,