From: Willy Tarreau <willy@w.ods.org>
To: johsc@arcor.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 panics on boot on 486 box: TSC requires pentium
Date: Wed, 27 Jul 2005 01:36:47 +0200 [thread overview]
Message-ID: <20050726233647.GU8907@alpha.home.local> (raw)
In-Reply-To: <20050726182258.GA1719@localhost>
On Tue, Jul 26, 2005 at 08:22:58PM +0200, johsc@arcor.de wrote:
> 2.4.31 compiled with -m486, panics on boot (486DX) and says something about
> TSC requires pentium, bang.
The processor type is wrong, you're on at least a pentium instead of a 486.
If you changed the config by hand (vi .config), you must do "make oldconfig"
after, to propagate values along the options.
> enabling the obscure flag
>
> [*] Unsynced TSC support
>
> seems to fix this - the corresponding .config label name is actually *more*
> helpful than the documentation.
Seems to me that it simply disables use of TSC. But if you see this option,
it means that your kernel has been compiled with SMP enabled, which is not
possible on 486 (I may be wrong here). Most probably, you took a config from
an inadequate kernel for your machine.
> - Obscure-sound-bug
> jazz16 on Travelmate 4000M doesn't seem to work either, sb.o
> complains about DSP version being "only" 3.01.
>
> (#insmod sb type=10 io=0x220 irq={5,7} dma=1 dma16=7)
>
> there is sound but mpg123 says 44100 is impossible.
mpg123 requires at least around 486 DX4-100 to play mp3 at 44100, so
perhaps it fails a self-test and complains because of that ?
Willy
next prev parent reply other threads:[~2005-07-27 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 18:22 2.4.31 panics on boot on 486 box: TSC requires pentium johsc
2005-07-26 23:36 ` Willy Tarreau [this message]
2005-07-27 9:50 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 20:38 Mikael Pettersson
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=20050726233647.GU8907@alpha.home.local \
--to=willy@w.ods.org \
--cc=johsc@arcor.de \
--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