rp5430 server crashing

[OH_2]

Hellow everyone

I have a rp5430 system that is intermittently crashing. I am attaching a TS99 file for reference. Could anyone advise on the cause?

Thanks in advance for your assistance

[Khairy]

could you post output:

# dmesg
# echo "Map SelAll Information ; wait InfoLog Done Exit OK" | cstm

Rgds

[Stefan Stechemesser · Accepted solution]

Hi,

this looks like a memory problem with dimms 2a/2b on extender 0 but in theory it can also be a memory extender or systemboard problem.

As a test I would recomend to swap the dimms with two other dimms in the same machine to see if the error moves with the dimms.

You should be able to view the memory error by looking at the GSP error log and set up filter options:

GSP> sl


SL

Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e
e

Set up filter options on this buffer? (Y/[N]) y
y
(input format is : x y z t ... or CR for all options)

Which Source are you interested in?
. Source 0 : No source
. Source 1 : Processor
. Source 2 : Processor cache
. Source 3 : PDH
. Source 4 : Power
. Source 5 : Fabric connector
. Source 6 : Platform
. Source 7 : Memory
. Source 8 : I/O
. Source 9 : Cell
. Source 10 : Protection domain
-> 7
7
...

then you wil finally see the error log
0x2000082374ff6b83 0x0000ff00002aff74

and the "2a" (digits 5,6 from right) is the Dimm location and one of the "00" (I don't know which) is the extender number.

But maybe you would prefer to open a case with HP support as the analysis of HPMC logs is really not easy.

best regards

Stefan

[OH_2]

Hi Stefan,

Thanks for your update. I will be changing the two DIMMs as soon as possible. I was impressed with your analysis and would be interested to read any pdf document/s that may be available covering this topic.

OH

[Stefan Stechemesser]

Hi,

I'm not aware of any documetation of these chassis codes for older servers like L-N- or A-Class.

For all newer servers (since PA8800 CPU) the MP log has a "text mode" which would convert a hex chassis code to human understandable text and also decodes the Dimm location for errors like this.

But for the L-Class, you have to consult HP Service to get hex logs analyzed.

best regards

Stefan