linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: TSCs are a no-no on i386
Date: Wed, 30 Jul 2003 16:18:11 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.GSO.3.96.1030730161309.911E-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20030730135623.GA1873@lug-owl.de>

On Wed, 30 Jul 2003, Jan-Benedict Glaw wrote:

> This small patch fixes a long-standing problem for bare i386 CPUs. These
> don't have TSCs and so, a recent 2.4.x kernel will simply halt the

 Actually i486 processors and some Pentium-like clones have none, too.

> machine leaving a text like "This CPU has no TSC feature (ie was
> compiled for Pentium+) but I do depend on it".

 That only happens if you change existing .config -- it may happen for all
options that are unset instead of being set to "n" -- and it can be worked
around by running `make oldconfig' twice. 

> Please apply. Worst to say, even Debian seems to start using i486+
> features (ie. libstdc++5 is SIGILLed on Am386 because there's no
> "lock" insn available)...

 You need the change for CONFIG_M486 and CONFIG_M586 as well.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +


  reply	other threads:[~2003-07-30 14:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 13:56 TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-30 14:18 ` Maciej W. Rozycki [this message]
2003-07-30 14:44   ` Jan-Benedict Glaw
2003-07-30 16:58 ` Matthew Garrett
2003-07-30 17:19   ` Alan Cox
2003-07-30 18:10 ` Adrian Bunk
2003-07-30 18:30   ` Mike Fedyk
2003-07-30 18:45     ` Adrian Bunk
2003-07-30 20:01       ` Alan Cox
2003-07-30 20:33         ` Jan-Benedict Glaw
2003-07-30 22:19           ` J.A. Magallon
2003-07-31  6:11             ` Jan-Benedict Glaw
2003-07-30 23:05           ` Alan Cox
2003-07-31 11:11             ` Richard B. Johnson
2003-07-31 11:26               ` Emulating i486+ insn on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:41             ` TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-31  0:22           ` Adrian Bunk
2003-07-31  6:22             ` Jan-Benedict Glaw
2003-07-31  7:17               ` Willy Tarreau
2003-07-31 11:38                 ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:51                   ` Alan Cox
2003-07-31 12:14                     ` Jan-Benedict Glaw
2003-07-31 13:01                       ` Jan-Benedict Glaw
2003-07-31 15:09                         ` Martin Schlemmer
2003-07-31 15:33                           ` Jan-Benedict Glaw
2003-08-01  5:37                             ` Martin Schlemmer
2003-07-31 15:12                     ` Jamie Lokier
2003-07-31 15:32                       ` Jan-Benedict Glaw
2003-07-31 15:07                 ` TSCs are a no-no on i386 Jamie Lokier
2003-07-31 15:23                   ` Willy Tarreau
2003-07-31 15:50                   ` Richard B. Johnson
2003-07-31 16:24                     ` Jan-Benedict Glaw
2003-08-06 11:08         ` Pavel Machek
2003-08-06 14:33           ` Maciej W. Rozycki
2003-07-30 20:28       ` Jan-Benedict Glaw
2003-07-30 21:50         ` Petr Vandrovec
2003-07-30 23:10           ` Alan Cox
2003-07-31 15:10             ` Jamie Lokier
2003-07-31 16:01               ` Alan Cox
2003-07-31 18:37                 ` Jamie Lokier
2003-07-31 19:10                   ` Alan Cox
2003-07-31  6:29           ` Jan-Benedict Glaw
2003-07-30 20:27   ` Jan-Benedict Glaw
2003-08-06 16:41 James Bottomley
2003-08-06 16:45 James Bottomley

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=Pine.GSO.3.96.1030730161309.911E-100000@delta.ds2.pg.gda.pl \
    --to=macro@ds2.pg.gda.pl \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).