From: Mikael Pettersson <mikpe@csd.uu.se>
To: Chris Sykes <chris@spackhandychoptubes.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic on 2.4.22 (no TSC) when compiled for i486
Date: Fri, 26 Sep 2003 13:40:28 +0200 [thread overview]
Message-ID: <16244.9644.70305.752172@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030926084848.GA16991@spackhandychoptubes.co.uk>
Chris Sykes writes:
> I'm getting a kernel panic from my 2.4.22 kernel when compiled for
> i486 (see attached .config).
>
> "Kernel panic: Kernel compiled for Pentium+, requires TSC feature!"
>
> The CPU is a Cyrix Cx486DX2 100MHz part. I tried booting with notsc
> but I get the message:
> "notsc: Kernel compiled with CONFIG_X86_TSC, cannot disable TSC."
>
> The kernel will work fine when recompiled for i386.
>
> Does a real 486 have a TSC, or is this a config bug?
...
> CONFIG_M486=y
...
> CONFIG_X86_TSC=y
I've reproduced this problem. It's a bug in the configuration
system which triggers when you change an option which has
derived options.
In this case, when first configuring for a CPU with TSC the
derived CONFIG_X86_TSC option is added. Then when reconfiguring
for a TSC-less CPU (e.g., 486) the derived option stays because
it derived from something that _was_ defined at the start of the
config run.
The workaround is to do an additional 'make oldconfig', after
which the derived option will be gone.
/Mikael
next prev parent reply other threads:[~2003-09-26 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 8:48 Chris Sykes
2003-09-26 11:40 ` Mikael Pettersson [this message]
2003-09-26 12:15 ` Chris Sykes
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=16244.9644.70305.752172@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=chris@spackhandychoptubes.co.uk \
--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
all inboxes | Powered by JetHome®