From: "Christian Bornträger" <linux-kernel@borntraeger.net>
To: "Dan Podeanu" <pdan@spiral.extreme.ro>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: DISCOVERED! Cause of Athlon/VIA KX133 Instability
Date: Sun, 6 May 2001 12:51:22 +0200 [thread overview]
Message-ID: <003301c0d61a$803aba00$3303a8c0@pnetz> (raw)
In-Reply-To: <Pine.LNX.4.30.0105061308410.27147-100000@spiral.extreme.ro>
> Mandrake 8's kernel comes with i586 CPU support, it is alredy known it
> works. Remember that the instability occurs only when Athlon optimizations
> are used.
You are right.
But I like to point out that on my Athlon kernel 2.4.3 is working fine.
The first kernel I face problems is 2.4.3-ac7. I also know that the
problem occurs of kernel 2.4.4.
That might help to find the problem.
next prev parent reply other threads:[~2001-05-06 10:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 9:12 DISCOVERED! Cause of Athlon/VIA KX133 Instability Christian Bornträger
2001-05-06 10:10 ` Dan Podeanu
2001-05-06 10:51 ` Christian Bornträger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-06 14:41 Ray Shaw
[not found] <20010501085939.A40276@shell.aros.net>
2001-05-01 19:40 ` Seth Goldberg
2001-05-01 20:02 ` Mark Hahn
2001-05-02 2:22 ` Seth Goldberg
2001-05-02 3:38 ` Wayne Whitney
2001-05-02 3:43 ` Mark Hahn
2001-05-02 7:35 ` Moses McKnight
2001-05-03 10:34 ` Seth Goldberg
2001-05-02 15:47 ` Jonathan Morton
2001-05-03 10:41 ` Seth Goldberg
2001-05-03 12:25 ` Jonathan Morton
2001-05-02 11:17 ` Alan Cox
2001-05-02 17:36 ` Dan Hollis
2001-05-01 17:03 Will Newton
2001-05-01 18:54 ` Seth Goldberg
2001-05-01 19:33 ` Dan Hollis
2001-05-01 19:41 ` Seth Goldberg
2001-05-01 10:48 Seth Goldberg
2001-05-01 12:57 ` Alan Cox
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='003301c0d61a$803aba00$3303a8c0@pnetz' \
--to=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pdan@spiral.extreme.ro \
/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