CPU not detected on a Compaq Proliant 3000 dual P II 400 Mhz

Bug #64133 reported by Joachim Davain
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-23-server

I made an installation of 6.06 server on a Compaq Proliant 3000 dual PII 400 Mhz, but only CPU 0 is detected. The 2 CPUs are OK for the bios. I exchanged the 2 CPUs and I get the same result only CPU 0 is detected.

# more /proc/version

Linux version 2.6.15-23-server (buildd@rothera) (gcc version 4.0.3 (Ubuntu 4.0.3
-1ubuntu5)) #1 SMP Tue May 23 15:10:35 UTC 2006

# more /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 5
model name : Pentium II (Deschutes)
stepping : 2
cpu MHz : 399.089
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 sep mtrr pge mca cmov pat p
se36 mmx fxsr
bogomips : 799.34

Tags: cft-2.6.27
Revision history for this message
Ben Collins (ben-collins) wrote : Re: [Bug 64133] CPU not detected on a Compaq Proliant 3000 dual P II 400 Mhz

On Thu, 2006-10-05 at 08:07 +0000, Joachim Davain wrote:
> Public bug reported:
>
> Binary package hint: linux-image-2.6.15-23-server
>
> I made an installation of 6.06 server on a Compaq Proliant 3000 dual PII
> 400 Mhz, but only CPU 0 is detected. The 2 CPUs are OK for the bios. I
> exchanged the 2 CPUs and I get the same result only CPU 0 is detected.

Please attach dmesg (do no paste in comment).

Revision history for this message
Joachim Davain (joachim-davain) wrote :

Here is dmesg

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Joachim Davain (joachim-davain) wrote :

Yes, there is still interest in investigating this bug report.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Has this been tested this against any later Ubuntu releases?
Has the hardware been verified OK? (ie. not just CPU's)
Is this issue tested against any other Linux distributions or other OS's?

Revision history for this message
Joachim Davain (joachim-davain) wrote :

The hardware is OK according to the BIOS utilities.
I cannot test against other OS's as the server is in production.
I will try with the 8.04 LTS when it will be released.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Joachim,
Are you able to try the following?

sudo dmidecode > dmidecode.txt
sudo biosdecode > biosdecode.txt
sudo ownership > ownership.txt # Note: this is a Compaq specific command.

If so, please attach resulting text files.
Thanks.

Revision history for this message
Joachim Davain (joachim-davain) wrote :

Here are the requested files

Revision history for this message
Joachim Davain (joachim-davain) wrote :
Revision history for this message
Joachim Davain (joachim-davain) wrote :

Ownership output is empty.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Joachim,
OK. Pre-SMBIOS system. Your system was manufactured pre-1999 (probably). However, it does appear to have ACPI functionality. This appears to be disabled by default on your system probably due to it's age. You could try booting with "acpi=force" kernel option? Long-shot!

++++++++++++++++++
Note to Kernel Team:
1/ This is a Pre-SMBIOS system.
2/ Summary of problem: Second CPU not recognised.
3/ It appears to have ACPI functionality, although unsure if it's supported.
4/ Compaq Proliant 3000 was originally sold with Linux support (Suse 6&7 & RH 6&7 )
5/ Firmware & documentation can be searched for here http://h20000.www2.hp.com/bizsupport/TechSupport/ [search for "proliant"]
6/ Firmware updates (Linux supported) are available and where released as recently as 2005.

Leaving this with the Kernel Team to decide upon "Won't Fix" or otherwise.
++++++++++++++++++++++++++++++++

Changed in linux-source-2.6.15:
status: Incomplete → Confirmed
Revision history for this message
Joachim Davain (joachim-davain) wrote :

Gareth,

No change with acpi=force and same dmesg output.

Changed in linux-source-2.6.15:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Joachim Davain (joachim-davain) wrote :

Gareth,

I upgraded to 8.04. The problem remains the same (with or without acpi=force).

Changed in linux-source-2.6.24:
assignee: nobody → ubuntu-kernel-team
status: New → Confirmed
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

Joachim,
Can you examine the following link?:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1209379186243+28353475&threadId=200797
In particular the section regarding the following:
/QUOTE{
    0. Boot To System Configuration Utility (F10)
    1. At main menu press Ctrl-A (or Ctrl-Q) to activate Advanced mode
    2. Select System Configuration
    3. Select Hardware Configuration
    4. Select View and edit details
    5. Change APIC Mode to Full Table (or Full Table Mapped)
}/ENDQUOTE

Reply:
 "The APIC setting was the problem. The proper setting (in this circumstance) was FULL TABLE not FULL TABLE MAPPED. I've now got a proliant 3000 server running dual 550s."

Your system is a little different but similar APIC change maybe worth a try.

Revision history for this message
Joachim Davain (joachim-davain) wrote :

Gareth,

I looked at the link you gave me, but in my case the POST reports that both processors are running fine.

Anyway, I tried but the System Configuration Utility is not available on my system.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
C. Brayton (cbrayton-boizebueditorial) wrote :

I have had this problem in both 2.6.31-17 and 2.6.32-9 (both generic and using the compiled-in acpi-cpufreq)

cat /proc/cpuinfo yields

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2500 @ 2.00GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm
bogomips : 3994.65
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual

The CPU is a Duo 2 T2500 @2GHz, as shown, but the GHz is shown as 1GHz. This throttles down my CPU to a maximum of 1GHz, making frequency scaling impossible. I have tried disabling scaling in BIOS (Dell Latitude D620, v.A10) to at least get the cpu to run at a constant 2GHz so I can work while waiting for a fix. No joy so far. Have even thought of compiling the old speedstep-centrino driver as a module, but not done with that time-intensive experiment yet.

clscpu yields:

c
cbrayton@macunaimachine:~/Desktop/Leituras$ lscpu
Architecture: i686
CPU(s): 2
Thread(s) per core: 1
Core(s) per socket: 2
CPU socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 14
Stepping: 8
CPU MHz: 1000.000
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K
c

Revision history for this message
C. Brayton (cbrayton-boizebueditorial) wrote :

Disabling CPU Frequency Control (speedstep) in BIOS, I get the following, but the CPU is running near 100% with just a few apps open in XFCE:

cbrayton@macunaimachine:~/Desktop/Leituras$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2500 @ 2.00GHz
stepping : 8
cpu MHz : 1997.368
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm
bogomips : 3994.73
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2500 @ 2.00GHz
stepping : 8
cpu MHz : 1997.368
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc arch_perfmon bts aperfmperf pni monitor vmx est tm2 xtpr pdcm
bogomips : 3994.73
clflush size : 64
cache_alignment : 64
address sizes : 32 bits physical, 32 bits virtual
power management:

Revision history for this message
Brad Figg (brad-figg) wrote :

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in supported series, please file a new bug.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Changed in linux-source-2.6.15 (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Yuhong Bao (yuhongbao-386) wrote :

Do you know what a Compaq SmartStart CD is? This should have the SCU.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.