linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPU/cache detection wrong
Date: 30 Sep 2002 17:34:15 +0100	[thread overview]
Message-ID: <1033403655.16933.20.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <m3hegaxpp0.fsf@lapper.ihatent.com>

On Sat, 2002-09-28 at 13:29, Alexander Hoogerhuis wrote:
> CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz stepping 04
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> 
> The machine is a Comapq Evo n800c with a 1.7GHz P4-M in it, and
> according to the BIOS I've got 16kb/512Kb L1/L2-cache. Accroding to
> the 2.4.20-pre7-ac3-kernel. It's been like this at least since
> 2.4.19-pre4 or so.

Can you stick a printk in arch/i386/kernel/setup.c in the function
init_intel    

Just before:                         
        /* look up this descriptor in the table */

stick

        printk("Cache info byte: %02X\n", des);

that will dump the cache info out of the CPU as the kernel scans it and
should let us find the error in the table.



  reply	other threads:[~2002-09-30 16:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 12:29 CPU/cache detection wrong Alexander Hoogerhuis
2002-09-30 16:34 ` Alan Cox [this message]
2002-09-30 17:43   ` Alexander Hoogerhuis
2002-09-30 22:15     ` Dave Jones
2002-10-01  7:21       ` Alexander Hoogerhuis
2002-10-01 11:06         ` Dave Jones
2002-10-01 15:31           ` Alexander Hoogerhuis
2002-10-01 17:01             ` Vojtech Pavlik
2002-10-01  1:06 David L. DeGeorge
2002-10-01 11:18 ` Dave Jones
2002-10-01 13:35   ` Maciej W. Rozycki
2002-10-01 15:15     ` Dave Jones
2002-10-01 16:03       ` Maciej W. Rozycki
2002-10-01 16:31         ` Dave Jones

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=1033403655.16933.20.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=alexh@ihatent.com \
    --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;
as well as URLs for NNTP newsgroup(s).