HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Rp5470 Crashes with Alert-12

 
Thayanidhi
Honored Contributor

Rp5470 Crashes with Alert-12

Hi,
I have Rp5470 which crashes with the symptom.
SYSTEM NAME: sapdevcon
DATE: 01/05/2008 TIME: 06:36:17
ALERT LEVEL: 12 = Software failure

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

CALLER ACTIVITY: D = system shutdown STATUS: 2
CALLER SUBACTIVITY: BE = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 02

0xF8E020C01100DBE2 00000000 0000CBE2 type 31 = legacy PA HEX chassis-code
0x58E028C01100DBE2 00006C00 05062411 type 11 = Timestamp 01/05/2008 06:36:17
Type CR for next entry, - CR for previous entry, Q CR to quit.

TS99 has
------- Processor 0 HPMC Information - PDC Version: 44.12 ------

Timestamp = Sat Jan 5 05:49:40 GMT 2008 (20:08:01:05:05:49:40)

HPMC Chassis Codes

Chassis Code Extension
------------ ---------
0x0000082000ff6242 0x0000000000000000
0x1800082011006322 0xcb81800000000000
0x0000082000ff6462 0x0000000000000000

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

Merced Bus Requestor Address = 0x0000000000000000
Merced Bus Target Address = 0xfffffffffed20000
Merced Bus Responder Address = 0xfffffffffed20000
Merced Error Status Reg = 0x2003000000002010
Merced Error Overflow Reg = 0x2000000000000000
Merced AERR Addr1 Log Reg = 0x00c00001000c0000
Merced AERR Addr2 Log Reg = 0x00008000078f0008
Merced DERR Log Reg = 0x00c0000000000000
Merced Error Syndrome Reg = 0x00000000000000c0

I have attached the log files.
I feel no hardware failure as the error reported by hp-ux.

Can any one guide?

Thanks and Regards
T.Thayanidhi


Attitude (not aptitude) determines altitude.
4 REPLIES 4
Thayanidhi
Honored Contributor

Re: Rp5470 Crashes with Alert-12

Hi,

Attaching the GSP logs..

Regards
TT
Attitude (not aptitude) determines altitude.
Mridul Shrivastava
Honored Contributor

Re: Rp5470 Crashes with Alert-12

I feel there is no hardware failure on the server since GSP logs doesn't point to any hardware entity and in this case GSP logs won't give more detail about the panic.

Is it creating crash dump? or system is not able to boot at all ?

After which stage it starts crashing.. may be that can give us some idea.

I found one entry about service processor, I think which might have already been taken care as no more entries for that now.

Log Entry # 157 :
SYSTEM NAME: sapdevcon
DATE: 07/30/2007 TIME: 11:27:00
ALERT LEVEL: 8 = Boot Possible, performance impaired

SOURCE: 6 = platform
SOURCE DETAIL: 6 = service processor SOURCE ID: 0
PROBLEM DETAIL: 1 = selftest result

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 03 = console
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x7010028166002030 0B0010FF 00000000 type 14 = Problem Detail
0x4810028166002030 7265666C 5461736B type 9 = ASCII Message reflTask
0x4810028166002030 7372632F 4C4F4765 type 9 = ASCII Message src/LOGe
0x7010028166002030 01060C08 20000013 type 14 = Problem Detail
0x58100A8166002030 00006B06 1E0B1B00 type 11 = Timestamp 07/30/2007 11:27:00
Type CR for next entry, - CR for previous entry, Q CR to quit.
Time has a wonderful way of weeding out the trivial
Roberto Arias
Valued Contributor

Re: Rp5470 Crashes with Alert-12

hi all:

ALert Level 12 is a panic by software. ¿have you installed patch of new software?

try boot of vmunix.prev in single user and run level 2. in this level check software withc swlist -l fileset a state

best regards
The man is your friend
Thayanidhi
Honored Contributor

Re: Rp5470 Crashes with Alert-12

Hi,

After replacing the PCI-Backplane the problem solved.

Regards
TT
Attitude (not aptitude) determines altitude.