From: "Wilson" <defiler@null.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Any lingering Athlon bugs in Kernel 2.4.14?
Date: Thu, 8 Nov 2001 17:38:38 -0500 [thread overview]
Message-ID: <006c01c168a6$1be38540$c800000a@Artifact> (raw)
In-Reply-To: <Pine.LNX.4.10.10111081706491.31943-100000@coffee.psychology.mcmaster.ca>
----- Original Message -----
From: "Mark Hahn" <hahn@physics.mcmaster.ca>
To: "Wilson" <defiler@null.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, November 08, 2001 5:16 PM
Subject: Re: Any lingering Athlon bugs in Kernel 2.4.14?
> > Bugs in the Athlon optimizations present in the Linux kernel.
>
> what bugs would those be? if you're thinking of the infamous
> "my athlon dies when I boot a CONFIG_MK7 kernel on a kt133",
> it is by all accounts a *chipset* bug, not a kernel bug.
> it's still unclear whether the voodoo workaround
> (in both linux and ac) is doing something sensible.
>
Perhaps I should have said "Unfortunate interactions" rather than "bug."
The bottom line is that some people have trouble running Linux with "Athlon"
selected as the processor type.
I was just trying to reassure the original poster that there wasn't anything
wrong with the Athlon CPU itself.
next prev parent reply other threads:[~2001-11-08 22:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 16:46 Calin A. Culianu
2001-11-08 17:51 ` Robert Love
2001-11-08 18:17 ` Calin A. Culianu
2001-11-08 19:18 ` Robert Love
2001-11-09 23:30 ` Calin A. Culianu
2001-11-09 23:34 ` Robert Love
2001-11-09 23:45 ` Calin A. Culianu
2001-11-10 13:51 ` Alan Cox
2001-11-11 5:05 ` Calin A. Culianu
2001-11-11 16:47 ` Wayne Whitney
2001-11-08 21:50 ` Gniazdowski
2001-11-08 21:54 ` Wilson
2001-11-08 22:16 ` Mark Hahn
2001-11-08 22:38 ` Wilson [this message]
2001-11-09 23:32 ` Calin A. Culianu
2001-11-08 23:29 ` Alan Cox
2001-11-09 23:35 ` Calin A. Culianu
2001-11-10 9:01 ` Luigi Genoni
2001-11-10 9:16 ` Wayne Whitney
2001-11-10 13:32 ` Luigi Genoni
2001-11-19 18:47 ` bill davidsen
2001-11-08 23:13 ` Dan Hollis
2001-11-09 23:33 ` Calin A. Culianu
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='006c01c168a6$1be38540$c800000a@Artifact' \
--to=defiler@null.net \
--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
all inboxes | Powered by JetHome®