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...
 21 0 0x000207 0x00000000000E003D CPU0 starting EFI
 30 0 0x0002B9 0x00000000000000AF EFI POST code
 40 0 0x0002B9 0x00000000000000F2 EFI POST code
 50 0 0x0002B9 0x00000000000000F2 EFI POST code
 60 0 0x0002B9 0x00000000000000F2 EFI POST code
 70 0 0x0002B9 0x00000000000000F2 EFI POST code
 80 0 0x0002B9 0x00000000000000F2 EFI POST code
 90 0 0x0002B9 0x00000000000000F2 EFI POST code
100 0 0x0002B9 0x0000000000000001 EFI POST code
110 0 0x0002B9 0x0000000000000002 EFI POST code
120 0 0x0002B9 0x0000000000000003 EFI POST code
130 0 0x0002B9 0x0000000000000004 EFI POST code
140 0 0x0002B9 0x0000000000000004 EFI POST code
157 0 0x00006B 0x000000000000001E unexpected trap
167 0 0x000066 0x000000000000001E trap taken, number in ext PE
177 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:

1[rx2600-mgmt] MP:CM> sysrev
2
3SYSREV
4
5Current firmware revisions
6
7 MP FW     : E.03.30
8 BMC FW    : 01.53
9 EFI FW    : 01.22

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

 1MP:SL (+,-,<CR>,D, F, L, J, H, K, T, A, U, ? for Help, Q or Ctrl-B to Quit) >
 2
 3Log Entry 560: 17 Sep 2013 09:22:33
 4Alert Level 5: Critical
 5Keyword: Type-02 0f7000 1011712
 6System firmware error
 7Logged by: Redundant w/ an E0 code;
 8Sensor: System Firmware Progress
 9Data2: PRV State: 0x3F
100xC152381F59020950 FF3F4070000F0300
11
12Log Entry 559: 17 Sep 2013 09:22:33
13Alert Level 7: Fatal
14Keyword: BOOT_TRAP_TAKEN
15Trap taken
16Logged by: System Firmware  0
17Data: Implementation dependent data field
180xF680006600E00930 000000000000001E
19
20Log Entry 558: 17 Sep 2013 09:22:32
21Alert Level 5: Critical
22Keyword: Type-02 0f7000 1011712
23System firmware error
24Logged by: Redundant w/ an E0 code;
25Sensor: System Firmware Progress
26Data2: PRV State: 0x3F
270xC152381F58020920 FF3F4070000F0300
28
29Log Entry 557: 17 Sep 2013 09:22:32
30Alert Level 7: Fatal
31Keyword: BOOT_UNEXPECTED_TRAP_POST_REDIR_TABLE
32Unexpected trap
33Logged by: System Firmware  0
34Data: Implementation dependent data field
350xF680006B00E00900 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:

1EFI version 1.10 [14.61]
2EFI64 Running on Intel(R) Itanium Processor Family
3EFI 1.10 IPF zx6000/rx2600/zx2000 1.22 [Thu Mar 11 14:22:35 2004] - HP
40 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..

Translations: