Simon Fowler wrote:
>
> On Thu, Sep 12, 2002 at 11:50:19AM +0200, Andi Kleen wrote:
> > Allan Duncan <[email protected]> writes:
> > >
> > > 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.
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.
On Fri, Sep 13, 2002 at 08:54:10AM +1000, Allan Duncan wrote:
> 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.
> 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.
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
--
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/