PCI Error Handling Product Note 3rd Edition

New iether Driver Error Messages
The new error messages for the iether driver (Gigabit Networking) that will appear in the console
log as illustrated in the following examples:
-------------------100BT/Gigabit Ethernet LAN/9000 Networking---------------@#%Thu Jan 24 MST
2008 21:50:49.540624 DISASTER Subsys:IETHER Loc:00000<1002> 1000Base-T in path 6/0/0/1/0
Was moved to DEAD state due to a PCI
error.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-------------------100BT/Gigabit
Ethernet LAN/9000 Networking---------------@#%Thu Jan 24 MST 2008 21:50:49.565469 DISASTER
Subsys:IETHER Loc:00000<1004> 1000Base-T in path 6/0/0/1/0 Is being suspended due to a PCI
error.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-------------------100BT/Gigabit
Ethernet LAN/9000 Networking---------------@#%Thu Jan 24 MST 2008 21:50:49.585899 DISASTER
Subsys:IETHER Loc:00000<1004> 1000Base-T in path 6/0/0/1/1 Is being suspended due to a PCI
error.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
New fcd Driver Error Messages
There 6 new error messages for the fcd driver (2-Gigabit 2 port and 4-Gigabit 1 port FibreChannel
- mass storage) that will be logged in syslog and diaglog as illustrated in the following
example(s):
1/0/10/1/0: Fibre Channel Driver has detected a Fatal PCI Error.
1/0/10/1/0: Fibre Channel Driver Received Suspend Request.
1/0/10/1/0: Fibre Channel Driver has been Successfully Suspended.
1/0/10/1/1: Fibre Channel Driver Received Suspend Request.
1/0/10/1/1: Fibre Channel Driver has detected a Fatal PCI Error.
1/0/10/1/1: Fibre Channel Driver has been Successfully Suspended.
New mpt Driver Error Messages
There are six new error messages for the mpt driver that will be logged in syslog and diaglog
for the following events:
• When the driver is taken offline due to a PCI error
• When the driver is suspended due to a PCI error
• When the driver is resumed after a PCI error
• When the resume operation fails due to a PCI error
• When a firmware update on the card associated with the driver fails due to a PCI error
• When an initiator ID change fails due to a PCI error
How to Online Recover from a PCI Error
The olrad command and the Attention Button can be used to attempt online recovery from a
PCI error without requiring a system reboot.
Recovery Using the olrad Command
1. If the PCI slot remains powered ON, use the olrad –p OFF slot_id command to power
it OFF.
2. If power OFF succeeds, try a Post Replace operation at the slot using the olrad -R
slot_id command.
3. If the Post Replace operation fails there is a high probability that the I/O card is bad. HP recommends
replacing the I/O card with an I/O card that has the same HP Manufacturing Part Number
12 PCI Error Handling Product Note