From: Stan Bubrouski <stan@ccs.neu.edu>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: khorben@defora.org
Subject: Re: [Fwd: Linux on Cyrix 6x86]
Date: Tue, 30 Dec 2003 14:20:27 -0500 [thread overview]
Message-ID: <1072812026.1760.19.camel@duergar> (raw)
In-Reply-To: <3FF1C5BC.8010902@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Tue, 2003-12-30 at 13:36, H. Peter Anvin wrote:
> From: Pierre Pronchery <khorben@defora.org>
> To: hpa@zytor.com
> Subject: Linux on Cyrix 6x86
> Date: Tue, 30 Dec 2003 15:19:18 +0100
>
> Hi,
>
> I've just compiled Linux 2.4.23 for a Cyrix 6x86 P166+ processor, with
> the appropriate "Processor family" option "586/K5/5x86/6x86/6x86MX"
> (CONFIG_M586=y). It says it's for 586-compatible processors, possibly
> lacking the TSC register, though the kernel panic'd at boot, saying it
> needed a TSC register.
>
I have the same processor in my old archive machine with an ancient
2.0.36 kernel. I do recall the kernel is an i586 and I believe there
was a cyrix CPU option back then (I have to take the drives out of that
machine and put them in this one to check as the system stopped booting
a few days ago). So looks like a bug.
> The same kernel configuration, this time set for 386, booted
> successfully.
>
<SNIP>
>
> PS: I first tried to sent this to davej@suse.de, but his address seems
> not to be valid anymore (<davej@suse.de>: user has moved to <unknown>).
>
I responded to this message only to possibly correct this address, I
believe you are looking for davej@redhat.com, correct?
-sb
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-30 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 18:36 H. Peter Anvin
2003-12-30 19:20 ` Stan Bubrouski [this message]
2004-01-02 20:07 ` Marcelo Tosatti
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=1072812026.1760.19.camel@duergar \
--to=stan@ccs.neu.edu \
--cc=khorben@defora.org \
--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®