From: brian@worldcontrol.com
To: Roberto Jung Drebes <drebes@inf.ufrgs.br>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Chris Vandomelen <chrisv@b0rked.dhs.org>,
linux-kernel@vger.kernel.org,
VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: Athlon: Try this (was: Re: Athlon bug stomping #2)
Date: Sat, 15 Sep 2001 00:15:30 -0700 [thread overview]
Message-ID: <20010915001530.A1594@top.worldcontrol.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0109140430540.2204-100000@jacui> <Pine.GSO.4.21.0109140523060.3130-100000@jacui>
In-Reply-To: <Pine.GSO.4.21.0109140523060.3130-100000@jacui>
> > On 13 Sep 2001, Eric W. Biederman wrote:
> > > Anyone want to generate a kernel patch so this fix can get some wider
> > > testing?
> On Fri, 14 Sep 2001, Roberto Jung Drebes wrote:
> > I'll try to isolate the single bit in the register that is causing the
> > fault and will send the diff.
On Fri, Sep 14, 2001 at 05:27:49AM -0300, Roberto Jung Drebes wrote:
> I tested here and it seems that bit 7 is responsible. Here is the diff to
> pci-pc.c:
I just tried the patch and for the first time I've been able to
successfully boot and run a 2.4 kernel with Athlon optimizations.
I have 11 machines all of which oops to death trying to boot
2.4.9ac5 with Athlon optimizations.
The machine that has been successful, and the only one I tried, is an
800 MHz Duron system with an Epox 8KTA3+ MB which is now running fine
with linux 2.4.9ac10 + the Athlon Bug stomper #2 bit 7 patch version 1.
I'll try some more of the machines on Monday.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2000 By Brian Litzinger, All Rights Reserved
next prev parent reply other threads:[~2001-09-15 7:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 12:31 Athlon bug stomping #2 VDA
2001-09-14 2:56 ` Roberto Jung Drebes
2001-09-14 4:02 ` Chris Vandomelen
2001-09-14 5:51 ` Eric W. Biederman
2001-09-14 7:34 ` Roberto Jung Drebes
2001-09-14 8:27 ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 9:26 ` Jeff Lightfoot
2001-09-14 18:19 ` Byron Stanoszek
2001-09-15 18:00 ` Liakakis Kostas
2001-09-15 20:28 ` VDA
2001-09-15 7:15 ` brian [this message]
2001-09-19 1:30 ` brian
2001-09-19 13:10 ` Re[2]: " VDA
2001-09-19 23:56 ` Nicholas Knight
2001-09-20 3:17 ` Nicholas Knight
2001-09-20 12:34 ` Alan Cox
2001-09-16 21:53 ` Carsten Leonhardt
2001-09-19 3:55 ` Dan Hollis
[not found] <372BFCD7961@vcnet.vc.cvut.cz>
2001-09-14 18:43 ` VDA
2001-09-14 23:16 ` Alan Cox
2001-09-15 17:44 ` Nicholas Knight
2001-09-15 18:02 ` Jonathan Morton
2001-09-15 23:23 ` Alan Cox
2001-09-16 1:52 ` Petr Vandrovec
2001-09-16 7:21 ` Steffen Persvold
2001-09-16 8:08 ` Jan Niehusmann
2001-09-19 3:47 ` Albert D. Cahalan
2001-09-16 11:02 ` Vojtech Pavlik
2001-09-16 13:53 ` Alan Cox
2001-09-16 13:50 ` Vojtech Pavlik
2001-09-16 14:47 ` Alan Cox
2001-09-16 17:01 ` Vojtech Pavlik
2001-09-16 16:52 ` Roberto Jung Drebes
2001-09-17 0:58 ` Petr Vandrovec
2001-09-17 1:37 ` Ignacio Vazquez-Abrams
2001-09-17 14:59 ` Jonathan Morton
2001-09-18 11:27 ` jury gerold
2001-09-20 23:38 ` bill davidsen
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=20010915001530.A1594@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=chrisv@b0rked.dhs.org \
--cc=drebes@inf.ufrgs.br \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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