mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Jacek Lipkowski <sq5bpf@acid.ch.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch to make 2.4.32 work on i486 again
Date: Wed, 1 Feb 2006 11:28:10 +0100	[thread overview]
Message-ID: <17376.36154.580526.776564@alkaid.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.58.0601312313050.6477@acid.ch.pw.edu.pl>

Jacek Lipkowski writes:
 > Booting the 2.4.32 kernel compiled for a i486 on an i486 box fails,
 > because "Kernel compiled for Pentium+, requires TSC feature!" (printed
 > from check_config() include/asm-i386/bugs.h). To reproduce, select 486 in
 > the kernel configuration and grep CONFIG_X86_TSC .config
 > 
 > Seems strange that no one noticed this, am i the only one still using 486
 > boxes? :)
 > 
 > Jacek
 > 
 > Simple patch against vanilla 2.4.32:
 > 
 > --- arch/i386/config.in.old	2006-01-30 22:57:21.000000000 +0100
 > +++ arch/i386/config.in	2006-01-30 23:00:55.000000000 +0100
 > @@ -65,6 +65,7 @@
 >     define_bool CONFIG_X86_POPAD_OK y
 >     define_bool CONFIG_RWSEM_GENERIC_SPINLOCK n
 >     define_bool CONFIG_RWSEM_XCHGADD_ALGORITHM y
 > +   define_bool CONFIG_X86_TSC n
 >  fi
 >  if [ "$CONFIG_M486" = "y" ]; then
 >     define_int  CONFIG_X86_L1_CACHE_SHIFT 4
 > @@ -72,6 +73,7 @@
 >     define_bool CONFIG_X86_ALIGNMENT_16 y
 >     define_bool CONFIG_X86_PPRO_FENCE y
 >     define_bool CONFIG_X86_F00F_WORKS_OK n
 > +   define_bool CONFIG_X86_TSC n
 >  fi
 >  if [ "$CONFIG_M586" = "y" ]; then
 >     define_int  CONFIG_X86_L1_CACHE_SHIFT 5

This is a known limitation of the 2.4 kernel's configuration system:
a single round of make ${foo}config doesn't always reach a fixpoint
with regard to the derived options. CONFIG_X86_TSC is the standard
example of this: switching from a stable .config with TSC (say i686)
to one without (say i486) leaves a stray definition of CONFIG_X86_TSC
behind in .config. Solution: run 'make oldconfig' after flipping the
user-selectatable options.

Your patch may fix the TSC case, but there are probably more cases
like this in 2.4.

/Mikael

      parent reply	other threads:[~2006-02-01 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 22:29 Jacek Lipkowski
2006-01-31 22:37 ` Grant Coady
2006-02-01  5:20 ` Willy Tarreau
2006-02-02 21:21   ` Marcelo Tosatti
2006-02-01 10:28 ` Mikael Pettersson [this message]

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=17376.36154.580526.776564@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sq5bpf@acid.ch.pw.edu.pl \
    /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®