public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mark Cuss" <mcuss@cdlsystems.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel reports 4 CPUS instead of 2...
Date: Wed, 16 Oct 2002 11:24:51 -0600	[thread overview]
Message-ID: <077901c27538$ef71b4a0$2c0e10ac@frinkiac7> (raw)

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Hello all

I'm working with a new Dell Poweredge 4600 Server with Dual CPUs.  However,
Linux reports that it sees 4 CPUs...  I have opened the thing to see if Dell
gave me 2 extras for free, but no luck:  Attached is /proc/cpuinfo.

I've tried the RedHat 8.0 stock kernel, as well as a freshly compiled 2.4.19
but both exhibit the same behavior.

The specifics on the machine:

Dual Xeon 2.2 GHz CPUs (512 k L2 cache)
2 Gigs DDR RAM
The chipset is a ServerWorks CMIC-HE (see attached lspci for complete
listing).

Has anyone else seen this behavior?  The only other SMP machine I have is an
older Dell server with Dual 1 GHz coppermines, and it reports 2 CPUs...

Any information or advice is greatly appreciated...

Thanks in Advance,

Mark


Mark Cuss
Real Time Systems Analyst
CDL Systems Ltd.
Suite 230
3553 - 31 Street NW
Calgary, Alberta
T2L 2K7

Phone (403) 289-1733 extension 226
Email:  mcuss@cdlsystems.com
URL: www.cdlsystems.com

[-- Attachment #2: pe4600 --]
[-- Type: application/octet-stream, Size: 1756 bytes --]

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Intel(R) XEON(TM) CPU 2.20GHz
stepping	: 4
cpu MHz		: 2190.049
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips	: 4364.69

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Intel(R) XEON(TM) CPU 2.20GHz
stepping	: 4
cpu MHz		: 2190.049
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips	: 4377.80

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Intel(R) XEON(TM) CPU 2.20GHz
stepping	: 4
cpu MHz		: 2190.049
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips	: 4377.80

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 15
model		: 2
model name	: Intel(R) XEON(TM) CPU 2.20GHz
stepping	: 4
cpu MHz		: 2190.049
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips	: 4377.80


[-- Attachment #3: lspci --]
[-- Type: application/octet-stream, Size: 1154 bytes --]

00:00.0 Host bridge: ServerWorks CMIC-HE (rev 22)
00:00.1 Host bridge: ServerWorks CMIC-HE
00:00.2 Host bridge: ServerWorks CMIC-HE
00:00.3 Host bridge: ServerWorks CMIC-HE
00:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
00:06.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891 (rev 01)
00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 Host bridge: ServerWorks CSB5 South Bridge (rev 93)
00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 USB Controller (rev 05)
00:0f.3 ISA bridge: ServerWorks: Unknown device 0225
00:10.0 Host bridge: ServerWorks CIOB30 (rev 03)
00:10.2 Host bridge: ServerWorks CIOB30 (rev 03)
00:11.0 Host bridge: ServerWorks CIOB30 (rev 03)
00:11.2 Host bridge: ServerWorks CIOB30 (rev 03)
01:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5700 Gigabit Ethernet (rev 14)
01:08.0 PCI bridge: Intel Corp.: Unknown device 0309 (rev 01)
02:06.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
02:06.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)

             reply	other threads:[~2002-10-16 17:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 17:24 Mark Cuss [this message]
2002-10-16 17:35 ` Kernel reports 4 CPUS instead of 2 Richard B. Johnson
2002-10-16 17:56   ` Samuel Flory
2002-10-16 17:54     ` Richard B. Johnson
2002-10-16 18:14       ` Samuel Flory
2002-10-16 19:28       ` James Cleverdon
2002-10-16 19:44         ` Mark Cuss
2002-10-16 20:10           ` Richard B. Johnson
2002-10-16 20:47           ` Samuel Flory
2002-10-16 21:44             ` Mark Mielke
2002-10-16 22:14               ` Samuel Flory
2002-10-16 22:21             ` Mark Cuss
2002-10-16 18:37     ` Mark Cuss
2002-10-16 23:21   ` Bryan Whitehead
2002-10-17  0:34     ` Mark Chernault
2002-10-17 12:56     ` Richard B. Johnson
2002-10-17 14:19       ` Dave Jones
2002-10-17 17:15       ` Bryan B Whitehead
2002-10-16 17:37 ` Joel Jaeggli
2002-10-16 17:48   ` Mark Cuss
2002-10-16 17:44 ` FD Cami
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16 18:08 Nakajima, Jun
2002-10-17  1:02 Matt_Domsch

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='077901c27538$ef71b4a0$2c0e10ac@frinkiac7' \
    --to=mcuss@cdlsystems.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