Error message during vpar bootup

[Hooi Siew Hoong_1]

Hi,

I have installed vpar on my N4000-44. I always see the following error message during the vpar bootup during the "Copy processor logs to /var/tombstones". And after I acknowledge the message, the boot continues without any issues.

Start Kernel Logging facility ....................................... N/A
Set privilege group ................................................. N/A
Display date ........................................................ N/A
Copy processor logs to /var/tombstones ..............................
************* SYSTEM ALERT **************
SYSTEM NAME: bdhp4317gsp
DATE: 02/06/2003 TIME: 03:58:38
ALERT LEVEL: 13 = System hang detected via timer popping

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 4 = timeout

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x78E020D41100F010 00000003 00000001 - type 15 = Activity Level/Timeout
0x58E028D41100F010 00006701 06033A26 - type 11 = Timestamp 02/06/2003 03:58:38
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice: a
*****************************************
OK
Save system crash dump if needed .................................... N/A
Enable auxiliary swap space ......................................... OK
Start syncer daemon ................................................. OK


Does anyone have any idea what is this about?

Thanks
Siewhoong

[Ravi_8]

Hi,

you need to boot from vpar kernel

ISL> boot /stand/vpmon

[Hooi Siew Hoong_1]

Hi,

This is in fact seen from the virtual console when the virtual partition is booted from the vpmon.

siewhoong

[Dietmar Konermann]

Usually this Alert level 13 happens if the communication between the GSP and the OS (vpmon in this case, I believe) is interrupted. Maybe, reading the tombstones causes a delay which leads to this symptom. Maybe a GSP firmware update helps...

Does this happen with latest OS patches, latest diagnostics and vpar 2.x? Otherwise I would consider updating/patching if the GSP is on latest FW revision.

Best regards...
Dietmar.

[Hooi Siew Hoong_1]

Thanks, I would try to upgrade the firmware to the latest and see what happens.

[T G Manikandan]

check the version of GSP.

If it is B version then update the firmware to B2.17

http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PF_CCANGSPB0217&context=firmware:cpu