BL40p reboot loop at POST

[Jason Menear_1]

Hello,

We have two BL40p's in a blade enclosure. Of the two, one is new with no O/S or production use. The second has had an O/S loaded (Windows 2003 Server Enterprise) but will be reloaded with a fresh O/S.

The second 40p, with O/S, has an issue whereby it will reboot multiple times at POST. It appears to check all 4 processors before it hits the reboot.

The first 40p does not exhibit this issue.

(We have a third 40p (another enclosure) that we do not believe has the issue.)

The concern is that the O/S with the issue of rebooting will one day become stuck for a long time (or infinitely) in the loop.

The 40p with the issue contains: 4 3.0GHz Processors and 4GB RAM; 2 Compaq/HP HBAs.

Things I've tried:
- disabling both SAN cards' IRQ via the BIOS setup
- clearing NVRAM/boot disk
- booting from backup BIOS
- cold booting
- pulling the 40p from the enclosure, waiting and reinserting
- using the BIOS test utility to test processors and RAM (no errors reported)

The server does not appear to have any other problems. I am viewing the reboots via iLO.


Anyone have any suggestions for this issue?

Thanks!
Jason

[FredyP]

Jason,

Did you ever get any feedback on this issue(bl40p reboot)? I have a bl40p doing the exact same thing.

Thanks,
Fredy,
719-592-7129

[Jason Menear_1]

Yes, I had a response from HP after opening a case.

I was told to attempt to resolve the issue by:

1) Disabling ASR
2) Disabling hyper-threading

Neither option worked, individually or as a combination.

I was also asked to view the IML logs, for which nothing was logged.

I was not very pleased with HP's level of service on the response. I'd recommend, however, that you open a case with them so they are aware of mulitple occurences of the issue!

Jason

[Jason Menear_1]

This issue has been found to be "known" within HP, after it was reported by several customers.

The solution is a replacement system board.

The issue is not related only to POST rebooting - you may experience random reboots.

I've been working with HP on the issue since this posting. It has been about 3 weeks since HP indicated it could be reproduced.

System board replacements seem to have fixed the issue.