From: Erik Mouw <erik@harddisk-recovery.com>
To: linux-kernel@vger.kernel.org
Cc: wli@holomorphy.com
Subject: 2.4.26 doesn't boot on a 386 without "Unsynced TSC support"
Date: Wed, 28 Jul 2004 17:47:49 +0200 [thread overview]
Message-ID: <20040728154748.GB1675@harddisk-recovery.com> (raw)
Hi,
I tried to boot 2.4.26 on my good old 386 board, but got a kernel
panic:
CPU: 386
Kernel panic: Kernel compiled for Pentium+, requires TSC feature!
The error message comes from the function check_config() in
include/asm-i386/bugs.h (thanks to wli for figuring out faster than I
did).
I am sure I selected support for a 80386 CPU, so the error message
looks wrong to me. CONFIG_M586TSC is not set, but CONFIG_X86_TSC is
enabled by default. The only way to disable it, is to enable "Unsynced
TSC support", (CONFIG_X86_TSC_DISABLE).
The help for CONFIG_X86_TSC_DISABLE mentions to use it for "NUMA
mult-mode boxes, laptops and other systems suffering from unsynced TSCs
or TSC drift, which can cause gettimeofday to return non-monotonic
values." A simple 80386 board doesn't belong to these, and I can't
remember having problmes with gettimeofday() in the past (IIRC the
board last ran linux-1.2 or 2.0).
My question is: is this a code bug, or a documentation bug? Right now,
I guess 2.4.26 will not run on anything < Pentium without
CONFIG_X86_TSC_DISABLE enabled.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next reply other threads:[~2004-07-28 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 15:47 Erik Mouw [this message]
2004-07-28 19:08 Mikael Pettersson
2004-07-29 13:36 ` Erik Mouw
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=20040728154748.GB1675@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®