From: "François Cami" <stilgar2k@wanadoo.fr>
To: Ward Vandewege <ward@pong.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in kernel 2.4.x with x>=12
Date: Mon, 26 Nov 2001 14:52:51 +0100 [thread overview]
Message-ID: <3C024933.3090408@wanadoo.fr> (raw)
In-Reply-To: <20011126145505.A3783@countzero.vandewege.net> <3C023E74.8090303@wanadoo.fr> <20011126154626.A4119@countzero.vandewege.net>
Ward Vandewege wrote:
> On Mon, Nov 26, 2001 at 02:07:00PM +0100, François Cami wrote:
>
>>Maybe that will sound funny but... Could you try
>>compiling the kernel for an i386 processor and
>>report the results ?
>>
>
> I've compiled 2.4.16-pre1 optimized for i386 instead of Athlon/Duron, and had no problem whatsoever booting. I'm now beating it a bit, compiling a kernel etc, but it appears to be rock solid.
>
> This seems to suggest there is a problem in the Athlon/Duron optimization code.
As I thought.
> Thanks François!
You're welcome.
François
next prev parent reply other threads:[~2001-11-26 13:49 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 [this message]
[not found] ` <3C024A98.50506@wanadoo.fr>
2001-11-26 15:23 ` Ward Vandewege
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=3C024933.3090408@wanadoo.fr \
--to=stilgar2k@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=ward@pong.be \
/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