compaq ml350

[terry712]

was installed via smart start 6.2
installed as pre migration
migrated and then brought up to compaq agents 6.4
nw 6 sp3 etc

on the second processor i have constant 100% utilisation
first processor 1 - 2 %

the only thing listed under processor are cpqacpi , and a few server 01: 's

the only tid i see is if it's an overlay cd

any thoughts

 

[marvhuffaker]

Just a thought.. try turning off the second processor and see how well it runs on just the first one. Also if you can determine which specific module it is that is hogging the processor, and troubleshoot from there. In Monitor.nlm, go to "KERNEL ==> BUSIEST THREADS" and see if any particular module is at the top of the list and is significantly higher than the others.

I also have a question about the agents.. HP has created a bit of confusion because a while back Compaq had a version of their agents/drivers called NSSD 6.40. But now they've also got their latest Proliant Support pack at v 6.40 also (PSP 6.40).

Could you verify that you installed the Proliant Support Pack and not the older NSSD 6.40?

Marvin

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

it's psp 6.4 as i reinstalled this

i thought about turning 2nd processor off
only prob is - it's a remote server with no access and no rib board so as it's running ok - it's awkward to play
but may try at weekend as it's bugging me

i'm going to try it with next server when i'm doing upgrade to see if i can get it ok

th busiest threads is only cpaacpi and some server 01's

 

[terry712]

i needed to reboot post 6.4

the cpqacpi was still version 1.04 and not the fixed 1.06

 

[marvhuffaker]

Did rebooting resolve the problem? I didn't realize that you hadn't rebooted afterwards.

Marv



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

yep

i dont normally reboot after compaq agent patch
but on checking it doesnt update acpi stuff

suppose this is logical - as when you reboot it's the acpi stuff that tells you if you have type restart instead of reset then the agents may not have initialise yet