Linux 2.4.20-pre4 & ff. blows away Xwindows with Matrox G400 and agpgart
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 3 lines · Allan Duncan
Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.
You're booting with mem=nopentium right ? It should go away when you turn that off. I'm working on a fix. You can safely turn it off for now, the old problems that it worked around are fixed.
-Andi
Quoted 9 lines · Andi Kleen
Quoted 3 lines · Allan Duncan
Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.
You're booting with mem=nopentium right ? It should go away when you turn that off. I'm working on a fix. You can safely turn it off for now, the old problems that it worked around are fixed.
The problem goes away without mem=nopentium - I've just booted into 2.4.20-pre5aa2 and fired up X.
Simon
Signature · 4 lines
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc (crappy) Homepage: http://bg77.anu.edu.au doe #237 (see http://www.lemuria.org/DeCSS) My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/
Quoted 7 lines · Simon Fowler
Quoted 5 lines · Andi Kleen
Quoted 3 lines · Allan Duncan
Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.
Quoted 6 lines
Quoted 4 lines
You're booting with mem=nopentium right ? It should go away when you turn that off. I'm working on a fix. You can safely turn it off for now, the old problems that it worked around are fixed.
The problem goes away without mem=nopentium - I've just booted into 2.4.20-pre5aa2 and fired up X.
Not in my case, at least for 2.4.20-pre4.
At which kernels does the nopentium become obsolete? Alan Cox mentioned some confusion about this. Obviously the latest ones, but does this extend as far back as 2.4.19?
In order to close in on what changes are triggering this, I found the patch for sched.c for -pre3 and ran that, and find that -pre3 is fine with or without nopentium, so that narrows it to what was altered pre3 to pre4.
There was nothing obvious in Marcelo's log of changes, so I will trawl through the diffs themselves tonight.
At the same time, I noticed that there seems to a fair bit of touchy behaviour of AGP out there, so maybe what is proving fatal to me is the same as the cause of flaky for others.
Quoted 2 lines · Allan Duncan
Not in my case, at least for 2.4.20-pre4.
2.4.19 works for me with nopentium, 2.4.20-pre5 fails with nopentium and works without it - I can't add anything beyond that.
Quoted 8 lines
At which kernels does the nopentium become obsolete? Alan Cox mentioned some confusion about this. Obviously the latest ones, but does this extend as far back as 2.4.19?
In order to close in on what changes are triggering this, I found the patch for
sched.cfor -pre3 and ran that, and find that -pre3 is fine with or without nopentium, so that narrows it to what was altered pre3 to pre4.
Quoted 6 lines
There was nothing obvious in Marcelo's log of changes, so I will trawl through the diffs themselves tonight.
At the same time, I noticed that there seems to a fair bit of touchy behaviour of AGP out there, so maybe what is proving fatal to me is the same as the cause of flaky for others.
AGP/DRI has been flaky for me in all sorts of ways, but then I've been using the DRI CVS code which does lots of strange things, so I can't pin the problems on AGP . . .
Simon
Signature · 4 lines
PGP public key Id 0x144A991C, or ftp://bg77.anu.edu.au/pub/himi/himi.asc (crappy) Homepage: http://bg77.anu.edu.au doe #237 (see http://www.lemuria.org/DeCSS) My DeCSS mirror: ftp://bg77.anu.edu.au/pub/mirrors/css/
Quoted 9 lines · Allan Duncan
Quoted 7 lines · Simon Fowler
Quoted 5 lines · Andi Kleen
Quoted 3 lines · Allan Duncan
Any suggestions of how to improve the error messages around the failure point are welcome. Nothing is written into dmesg at the time of failure.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
You're booting with mem=nopentium right ? It should go away when you turn that off. I'm working on a fix. You can safely turn it off for now, the old problems that it worked around are fixed.
The problem goes away without mem=nopentium - I've just booted into 2.4.20-pre5aa2 and fired up X.
Not in my case, at least for 2.4.20-pre4.
Errm. Turns out I ran the same test twice, both with nopentium.
So, in summary, nopentium doesn't break 2.4.20-pre3 and earlier, breaks 2.4.20-pre4 and later.
Thankyou all.