From: Brian Gerst <bgerst@didntduck.org>
To: Ross Vandegrift <ross@willow.seitz.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 broken on 486SX
Date: Fri, 24 Aug 2001 16:37:04 -0400 [thread overview]
Message-ID: <3B86BAF0.489E92C6@didntduck.org> (raw)
In-Reply-To: <20010824154233.A10048@willow.seitz.com> <20010824161747.A10618@willow.seitz.com>
Ross Vandegrift wrote:
>
> Ack, that was a horrific problem report. Here are a few relevant data points I left out:
>
> Kernels have always been compiled only with 386 optimizations.
> (tried 486 a few times, no difference)
> Always built including soft float support (not that it matters so early)
> Always built with gcc 2.95.2
> Same kernel binaries work perfectly on a number of other boxen:
> A 386DX, a number of Pentium 100's, another 486SX, and a K6-2
What was the last known working kernel for this machine? Have you tried
any -ac kernels?
--
Brian Gerst
next prev parent reply other threads:[~2001-08-24 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 19:42 2.4 broken on 486SX Ross Vandegrift
2001-08-24 19:59 ` Richard B. Johnson
2001-08-24 20:17 ` Ross Vandegrift
2001-08-24 20:37 ` Brian Gerst [this message]
2001-08-25 2:46 ` Steve Kieu
2001-08-25 7:12 ` Cliff Albert
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=3B86BAF0.489E92C6@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ross@willow.seitz.com \
/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