Date: Sun, 7 Nov 2004 22:07:18 +0100 (MET)
Message-Id: <200411072107.iA7L7I0K004173@harpo.it.uu.se>
From: Mikael Pettersson <mikpe@csd.uu.se>
To: ledva@centrum.cz, linux-kernel@vger.kernel.org
Subject: Re: bugy config cpu 386 selection CONFIG_X86_TSC
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1298
Lines: 35

On Sun, 07 Nov 2004 20:07:45 +0100, <ledva@centrum.cz> wrote:
>I just had to compile kernel for zipslack for 386 because
>it's default has some problem with *WP
>I chose linux-2.4.27 tree.
...
>I did
>
>make mrproper && make menuconfig && \
>make dep && make bzImage
>
>selected 386 and several other options as you
>can see in .config which can be obtained from
>http://portal.promon.cz/ledvinka/i/tscerr/config
>
>All changes were done entirely via menuconfig.
>Result of booting up the kernel is:
>
>CPU: 386
>Kernel panic: Kernel compiled for Pentium+, requires TSC feature!
>In idle task  - not syncing

Your config still has CONFIG_X86_TSC set, hence the panic.

Do a 'make oldconfig' after switching CPU type from a
TSC-capable one to a TSC-less one in 2.4 kernels. There
is a known bug in the old configuration system where it
can leave derived options in an inconsistent state after
a single round of option changes. CONFIG_X86_TSC is the
prime example of this. Doing a second configuration round
allows the derived options to reach a fixpoint.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/