From: Ward Vandewege <ward@pong.be>
To: "François Cami" <stilgar2k@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in kernel 2.4.x with x>=12
Date: Mon, 26 Nov 2001 17:23:09 +0200 [thread overview]
Message-ID: <20011126172309.A5368@countzero.vandewege.net> (raw)
In-Reply-To: <20011126145505.A3783@countzero.vandewege.net> <3C023E74.8090303@wanadoo.fr> <20011126154626.A4119@countzero.vandewege.net> <3C024A98.50506@wanadoo.fr>
In-Reply-To: <3C024A98.50506@wanadoo.fr>; from stilgar2k@wanadoo.fr on Mon, Nov 26, 2001 at 02:58:48PM +0100
On Mon, Nov 26, 2001 at 02:58:48PM +0100, François Cami wrote:
> Ward Vandewege wrote:
>
> > This seems to suggest there is a problem in the Athlon/Duron optimization code.
>
> As a matter of fact the problem seems to be more with the KT133/KT133A
> chipset, than with the Athlon/Duron optimization code.
>
> I'm nearly sure that compiling for K6 or i586 (the MMX one)
> would work fine, too, and it will beat a 386 kernel hands down.
Confirmed. 2.4.16-pre1 works just fine on my Duron, when compiled for K6.
I'm now compiling 2.4.16 - it's a busy day for gcc :-)
Bye for now,
Ward.
--
Pong.be -( "If you think penguins are fat and waddle, you have )-
Virtual hosting -( never been attacked by one running at you in excess of )-
http://pong.be -( 100 MPH." -- Linus )-
prev parent reply other threads:[~2001-11-26 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 12:55 Oops in kernel 2.4.x with x>=12 Ward Vandewege
[not found] ` <3C023E74.8090303@wanadoo.fr>
2001-11-26 13:46 ` Ward Vandewege
2001-11-26 13:52 ` François Cami
[not found] ` <3C024A98.50506@wanadoo.fr>
2001-11-26 15:23 ` Ward Vandewege [this message]
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=20011126172309.A5368@countzero.vandewege.net \
--to=ward@pong.be \
--cc=linux-kernel@vger.kernel.org \
--cc=stilgar2k@wanadoo.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.