mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: erik@harddisk-recovery.com, linux-kernel@vger.kernel.org
Cc: wli@holomorphy.com
Subject: Re: 2.4.26 doesn't boot on a 386 without "Unsynced TSC support"
Date: Wed, 28 Jul 2004 21:08:38 +0200 (MEST)	[thread overview]
Message-ID: <200407281908.i6SJ8c9I015801@harpo.it.uu.se> (raw)

On Wed, 28 Jul 2004 17:47:49 +0200, Erik Mouw wrote:
>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!
...
>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).
...
>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.

It's a limitation in scripts/Configure.
If you start with a .config with TSC enabled/required,
and just flip the CPU selection option to a TSC-less
CPU, like 386 or 486, then you end up with a .config
that _still_ has TSC enabled/required.

The workaround is to run 'make oldconfig' afterwards.

FWIW, both 2.4 and 2.6 kernels run Ok on my 486.
(My 486's Fedora user-space is another matter,
requiring kernel hacks for unconditional RDTSC
usage in RPM, but that's another issue.)

             reply	other threads:[~2004-07-28 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 19:08 Mikael Pettersson [this message]
2004-07-29 13:36 ` Erik Mouw
  -- strict thread matches above, loose matches on Subject: below --
2004-07-28 15:47 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=200407281908.i6SJ8c9I015801@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=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®