All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Pfeiffer <profmakx@profmakx.org>
To: linux-kernel@vger.kernel.org
Subject: CPU detection broken in 2.5.27?
Date: Sun, 21 Jul 2002 18:07:26 +0200	[thread overview]
Message-ID: <3D3ADC3E.9050307@milliways.de> (raw)
In-Reply-To: 200207211537.03813.mcp@linux-systeme.de

Hi all,

I just noticed that my /proc/cpuinfo states wrong or incomplete 
information about my processor. My PIII-1000M Processor is reported as 
00/0B (Stepping?) and with only 32 KB of cache (which obviously is the 
L1d and L1i value). I think this happened during the split of the CPU 
detection code... I found nothing about that in archives or similar 
(i.e. on the list).
Perhaps someone who knows how to do it can look into that as i would 
need hours just to understand just what they are doing there and to read 
the specs of the CPUID instruction etc

Thanks in advance

Markus



  parent reply	other threads:[~2002-07-21 16:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 13:37 heavy Disk I/O and system stops reacting for seconds Marc-Christian Petersen
2002-07-21 14:17 ` Adrian Bunk
2002-07-21 15:34   ` Marc-Christian Petersen
2002-07-21 16:07 ` Markus Pfeiffer [this message]
2002-07-21 16:41   ` CPU detection broken in 2.5.27? Dave Jones
2002-07-23 19:14     ` Patrick Mochel
2002-07-23 19:29       ` Dave Jones
2002-07-23 20:26         ` Patrick Mochel
2002-07-23 20:34           ` Dave Jones
2002-07-23 20:34             ` Patrick Mochel
2002-07-23 20:56               ` Dave Jones
2002-07-23 21:08                 ` Patrick Mochel
2002-07-21 16:45   ` Time problem with 2.5.27 on Intel (and kernel freezes...) Oliver Pitzeier
  -- strict thread matches above, loose matches on Subject: below --
2002-07-24  0:52 CPU detection broken in 2.5.27? Mikael Pettersson

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=3D3ADC3E.9050307@milliways.de \
    --to=profmakx@profmakx.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.