cstm infolog on L2000 /w hp-ux 11.0

[???_185]

with cstm info tool, the L2000 infolog shows me following errors...
Can anyone tell me, what's the meaning of these error messages? OR
Where can I find the manuals, docs, or something else /t describe these messages?

# cstm
cstm> sel dev nn
cstm> info;infolog;
where, nn is corresponding cpu #

------------------------------
HPMC Chassis Codes

Chassis Code Extension
------------ ---------
0x0000082000ff6242 0x0000000000000000
0x1800082011006312 0xcb81000000000000
0x0000087000ff6292 0x0000000000000000
....
General Registers 0 - 31
00-03 0000000000000000 00000000000001b8 0000000000351bf0 00000000006634b8
04-07 0000000100740000 0000000000000020 0000000000000060 0000000000664608
....

Control Registers 0 - 31

00-03 000000007ffe2838 0000000000000000 0000000000000000 0000000000000000
....

Space Registers 0 - 7
00-03 06586c00 05828800 00000000 00000000
04-07 00000000 0456f800 04dc6400 00000000


IIA Space (back entry) = 0x0000000000000000
IIA Offset (back entry) = 0x000000000011993c
Check Type = 0x20000000
CPU State = 0x9e000004
Cache Check = 0x00000000
TLB Check = 0x00000000
Bus Check = 0x0030103b
Assists Check = 0x00000000
Assist State = 0x00000000
Path Info = 0x00000000
System Responder Address = 0x000000fffbffe022
System Requestor Address = 0xfffffffffffa0000


Floating Point Registers 0 - 31
00-03 0800000000000000 0000000000000000 0000000000000000 0000000000000000
04-07 0000000000000001 000001b800000096 3ff0000000000005 00000000000001b8
....

Check Summary = 0xcb81000000000000
Available Memory = 0x0000000080000000
CPU Diagnose Register 2 = 0x0204000004802204
CPU Status Register 0 = 0x2440c24000000000
CPU Status Register 1 = 0x8002000000000000
SADD LOG = 0x0060001800000018
Read Short LOG = 0xc18200fffbffe022

-------------- Memory Error Log Information --------------

Bus 0 Log Information

Timestamp = Wed Mar 8 07:17:02 GMT 2000 (20:00:03:08:07:17:02)

OV RQ RS ESTAT A C D corr unc fe cw pf
-- -- -- ----- - - - ---- --- -- -- --
X X ERR_ERROR X X

Bus Requestor Address = 0xfffffffffffa0000
Bus Target Address = 0x0000000000000000
Bus Responder Address = 0xfffffffffed00000

Error Status Reg = 0x0000000000100010
Runway Control Reg = 0x0000021c00001418
Runway Address Reg = 0xc1bff0fffed08040
Runway Data High Reg = 0xe840c000083c025c
Runway Data Low Reg = 0xe840c000083c025c
Memory Address Reg = 0x000001ff3fffffff
Memory Address Corr Reg = 0x000001ff3fffffff
Memory Syndrome Reg = 0x0000000000000000
Memory Syndrome Corr Reg = 0x0000000000000000
....

------------ I/O Module Error Log Information ------------

Summary of IO subsystem log entries
-----------------------------------
Phys Loc Vendor Device Severity
Description (hex) Id Id CORR UNC FE CW
----------- ----- ------ ------ ----------------
System Bus Adapter RP 0x000000ffff01ff83 0x103c 0x1051 X
System Bus Adapter RP 0x000000ffff06ff83 0x103c 0x1051 X
System Bus Adapter RP 0x000000ffff08ff83 0x103c 0x1051 X
....
Detail display of IO subsystem log entries
------------------------------------------

System Bus Adapter -- Rope Interface
------------------------------------------

Timestamp = Wed Mar 8 07:17:11 GMT 2000 (20:00:03:08:07:17:11)

OV RQ RS ESTAT A C D corr unc fe cw pf
-- -- -- ----- - - - ---- --- -- -- --
ERR_FUNCTION X

IO Requestor Address = 0x0000000000000000
IO Target Address = 0x0000000000000000
IO Responder Address = 0x0000000000000000
IO Physical Location = 0x000000ffffffff82
IO Hardware Path = 0x00ffffffffffff00

Module Error Register = 0x0000000000000000
Rope Physical Location = 0x000000ffff01ff83

----------------------------------

Thank you...

[Andrew Rutter]

hi,

part of the PIM data is missing from the beginning, however it looks like you had an IO error back in 2000 from the date stamp. That is if your system date is correct.

The system holds the last errors until they are either cleared manually or another error occures, in which they are over written.

The problem could be either an IO card or the backplane problem? have any of these parts been replaced before. As they are old errors it could also be irrelevant due to new patches installed.

If the date is correct on the system then check for errors in the syslog.log and also in the GSP to see if there are any more. If not then I would ignore them for now but keep checking. Also running the stm tests on the system may help.

Andy

[Mirko Schmidt]

Hello Zungwon,

this is only a part of an errorlog, better I say from a ts-file. Such files are saved at /var/tombstones . There are ts-files for each boot/crasch. To see the whats wrong at your system I need the whole ts99 and the ts98, ts97 to contrast the ts99 with older files.

Regards
Mirko Schmidt

[Sameer_Nirmal]

Hi,

The infolog for the cpu # selected shows its PIM ( Process/Processor Intenal Memory )
data. As indicated, a HPMC (High Priority Machine Check) had occured.

Although the posted infolog is not complete, following could be make-out from whatever being shown.

HPMC occured on account of Bus 0 check. The system bus might be hunged at that time.
More details could be know if complete infolog is read or by referring /var/stombstones/ts99 , ts98 files.