From: Allan Duncan <allan.d@bigpond.com>
To: Simon Fowler <simon@himi.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: Linux 2.4.20-pre4 & ff. blows away Xwindows with Matrox G400 and agpgart
Date: Fri, 13 Sep 2002 08:54:10 +1000 [thread overview]
Message-ID: <3D811B12.A6615688@bigpond.com> (raw)
In-Reply-To: 20020912213201.GA9168@himi.org
Simon Fowler wrote:
>
> On Thu, Sep 12, 2002 at 11:50:19AM +0200, Andi Kleen wrote:
> > Allan Duncan <allan.d@bigpond.com> 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.
next prev parent reply other threads:[~2002-09-12 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D7FF444.87980B8E@bigpond.com.suse.lists.linux.kernel>
2002-09-12 9:50 ` Linux 2.4.20-pre4 & ff. blows away Xwindows with Matrox G400 and agpgart Andi Kleen
2002-09-12 21:32 ` Simon Fowler
2002-09-12 22:54 ` Allan Duncan [this message]
2002-09-13 1:20 ` Simon Fowler
2002-09-13 3:11 ` Allan Duncan
2002-09-12 1:56 Allan Duncan
2002-09-12 7:51 ` Simon Fowler
2002-09-12 9:12 ` Nuitari
2002-09-12 23:24 ` Allan Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D811B12.A6615688@bigpond.com \
--to=allan.d@bigpond.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@himi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox