public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark <mark@harddata.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Dual Athlon CPU detection..
Date: Thu, 18 Mar 2004 13:52:34 -0700	[thread overview]
Message-ID: <200403181352.34737.mark@harddata.com> (raw)
In-Reply-To: <4059FCB9.4070204@lbl.gov>

On March 18, 2004 12:47 pm, Thomas Davis <tadavis@lbl.gov> wrote:
> I'm getting this in my /proc/cpuinfo:
>
> [tdavis@lanshark tdavis]$ more /proc/cpuinfo
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 6
> model           : 8
> model name      : AMD Athlon(tm) MP 2200+
> stepping        : 0
> cpu MHz         : 1800.902
> cache size      : 256 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
> bogomips        : 3547.13
>
> processor       : 1
> vendor_id       : AuthenticAMD
> cpu family      : 6
> model           : 8
> model name      : AMD Athlon(tm) Processor
> stepping        : 0
> cpu MHz         : 1800.902
> cache size      : 256 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
> bogomips        : 3596.28
> [tdavis@lanshark tdavis]$ uname -a
> Linux lanshark.nersc.gov 2.6.4-rc1-mm1 #1 SMP Tue Mar 2 14:09:44 PST 2004
> i686 athlon i386 GNU/Linux
>
>
> Is this a bad CPU, or a kernel bug?

AFAIK this information comes from the Bios. Some bioses don't verify that the 
second CPU as being an MP. It's been known for some time. Some people were 
using this to run 1 MP and 1 XP to save money on processors. However if you 
were to update your bios, it might start checking both for being MPs. 
Original bioses didn't even check for the first processor at one time but AMD 
complained and the bioses were modified.

-- 
Mark Lane, CET mailto:mark@harddata.com 
Hard Data Ltd. http://www.harddata.com 
T: 01-780-456-9771   F: 01-780-456-9772
11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3
--> Ask me about our Excellent 1U Systems! <--

  reply	other threads:[~2004-03-18 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 19:47 Dual Athlon CPU detection Thomas Davis
2004-03-18 20:52 ` Mark [this message]
2004-03-18 21:42   ` Willy Tarreau
2004-03-18 21:47   ` Thomas Davis

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=200403181352.34737.mark@harddata.com \
    --to=mark@harddata.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