There’s life in the old dog yet – HP Integrity RX2600 EFI Unexpected TRAP

A couple of months ago I installed Red Hat Enterprise Linux on a dedicated hard drive of my HP Integrity RX2600 servers. Because the installation programm doesn’t support the native Management Processor console I had to connect a screen, keyboard and mouse to the device. The installation worked like a charm and after a hour the host rebooted.

Unfortunately the system didn’t want to boot anymore since the installation. A rare and funny accident – evil to him who evil thinks (if [ “$os” <> “HP-UX” ]; then crash; fi;).

EFI didn’t want to start-up anymore – it just crashed with a “Unexpected TRAP“:

...
1 0 0x000207 0x00000000000E003D CPU0 starting EFI
0 0 0x0002B9 0x00000000000000AF EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x00000000000000F2 EFI POST code
0 0 0x0002B9 0x0000000000000001 EFI POST code
0 0 0x0002B9 0x0000000000000002 EFI POST code
0 0 0x0002B9 0x0000000000000003 EFI POST code
0 0 0x0002B9 0x0000000000000004 EFI POST code
0 0 0x0002B9 0x0000000000000004 EFI POST code
7 0 0x00006B 0x000000000000001E unexpected trap
7 0 0x000066 0x000000000000001E trap taken, number in ext PE
7 0 0x00003C 0x0000000000005A00 trap taken, offset in ext PE

Researching the internet didn’t helped much – I only found hints for faulty hardware and old firmware revisions. In this case the firmware was up-to-date – beside that firmware updates are impossible without a working EFI shell:

[rx2600-mgmt] MP:CM> sysrev

SYSREV

Current firmware revisions

 MP FW     : E.03.30
 BMC FW    : 01.53
 EFI FW    : 01.22

In the system log I found the following entries among others:

MP:SL (+,-,<CR>,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >

Log Entry 560: 17 Sep 2013 09:22:33
Alert Level 5: Critical
Keyword: Type-02 0f7000 1011712
System firmware error
Logged by: Redundant w/ an E0 code;
Sensor: System Firmware Progress
Data2: PRV State: 0x3F
0xC152381F59020950 FF3F4070000F0300


Log Entry 559: 17 Sep 2013 09:22:33
Alert Level 7: Fatal
Keyword: BOOT_TRAP_TAKEN
Trap taken
Logged by: System Firmware  0
Data: Implementation dependent data field
0xF680006600E00930 000000000000001E


Log Entry 558: 17 Sep 2013 09:22:32
Alert Level 5: Critical
Keyword: Type-02 0f7000 1011712
System firmware error
Logged by: Redundant w/ an E0 code;
Sensor: System Firmware Progress
Data2: PRV State: 0x3F
0xC152381F58020920 FF3F4070000F0300


Log Entry 557: 17 Sep 2013 09:22:32
Alert Level 7: Fatal
Keyword: BOOT_UNEXPECTED_TRAP_POST_REDIR_TABLE
Unexpected trap
Logged by: System Firmware  0
Data: Implementation dependent data field
0xF680006B00E00900 000000000000001E

After a couple of desperate reset attempts I crawled under my table and discovered that I forgot to disconnect the USB mouse and keyboard after the installation.

And this was the cause of failure: disconnecting the USB mouse and keyboard really solved the problem – EFI is working fine again:

EFI version 1.10 [14.61]
EFI64 Running on Intel(R) Itanium Processor Family
EFI 1.10 IPF zx6000/rx2600/zx2000 1.22 [Thu Mar 11 14:22:35 2004] - HP
0 0 0x0002B9 0x0000000000000013 EFI POST code

I’d never thought that a connected USB mouse/keyboard can cause the whole EFI firmware to stop working..

Leave a Reply