mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: 2.4.26 doesn't boot on a 386 without "Unsynced TSC support"
@ 2004-07-28 19:08 Mikael Pettersson
  2004-07-29 13:36 ` Erik Mouw
  0 siblings, 1 reply; 3+ messages in thread
From: Mikael Pettersson @ 2004-07-28 19:08 UTC (permalink / raw)
  To: erik, linux-kernel; +Cc: wli

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.)

^ permalink raw reply	[flat|nested] 3+ messages in thread
* 2.4.26 doesn't boot on a 386 without "Unsynced TSC support"
@ 2004-07-28 15:47 Erik Mouw
  0 siblings, 0 replies; 3+ messages in thread
From: Erik Mouw @ 2004-07-28 15:47 UTC (permalink / raw)
  To: linux-kernel; +Cc: wli

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-07-29 13:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-28 19:08 2.4.26 doesn't boot on a 386 without "Unsynced TSC support" Mikael Pettersson
2004-07-29 13:36 ` Erik Mouw
  -- strict thread matches above, loose matches on Subject: below --
2004-07-28 15:47 Erik Mouw

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®