public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Davis <tadavis@lbl.gov>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Dual Athlon CPU detection..
Date: Thu, 18 Mar 2004 11:47:05 -0800	[thread overview]
Message-ID: <4059FCB9.4070204@lbl.gov> (raw)

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?

             reply	other threads:[~2004-03-18 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 19:47 Thomas Davis [this message]
2004-03-18 20:52 ` Dual Athlon CPU detection Mark
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=4059FCB9.4070204@lbl.gov \
    --to=tadavis@lbl.gov \
    --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