Troubleshooting
Windows Miniport Event Log Codes
The Windows Miniport driver logs events and errors in the Windows Event log. Serious errors are always logged. Informational events are only logged if the registry parameter LogError=1 is used.
All Miniport logged events are issued with an Event ID of 11 (INTERNAL ADAPTER ERROR) but do not necessarily indicate an HBA error occurred. Byte offset 0x10 of the event is the driver event code. Byte offsets 0x11 to 0x13 contain
Table 5 describes the SCSI port error log codes.
Table 5: SCSI Port Error Log Codes
0x10 |
|
|
|
Offset | Explanation | 0x11 to 0x13 Further Information | |
0xD0 | SNS_REQ (XMIT_SEQ | 0x11 | = cmdstat, 12 = parm err |
| failed) |
|
|
|
|
|
|
0xD1 | SNS_RSP (RCV_SEQ | 0x11 | = cmdstat, 12 = parm err |
| failed) |
|
|
|
|
|
|
0xD3 | RCV_ELS_REQ failed | 0x11 | = cmdstat, 12 = parm err |
|
|
|
|
0xD4 | XMT_ELS_REQ failed | 0x11 | = cmdstat, 12 = parm err |
|
|
| |
0xD5 | Too many targets found | 0x11 to 13 = D_DID that didn’t fit | |
| (160+) |
|
|
|
|
| |
0xD6 | SNS request | 0x11 to 13 = no additional information | |
|
|
|
|
0xD7 | Mailbox interrupt | 0x11 | = mailbox word 0 |
|
|
|
|
0xD8 | TPRLO requested when | 0x11 | = local req. state, 12 = |
| busy | discstate, 13 = mailbox word 0 | |
|
|
|
|
0xD9 | Link down | 0x11 | = local req. state, 12 = |
| occurred | discstate, 13 = mailbox word 0 | |
|
|
|
|
0xDA | Hard link down | 0x11 | = local req. state, 12 = |
| occurred | discstate, 13 = mailbox word 0 | |
|
|
| |
0xE1 | Error interrupt occurred | Status register bytes | |
|
| ||
|
| hardware failure, return HBA for | |
|
| repair. | |
|
|
|
|
0xE2 | Mailbox cmd | 0x11 | = command |
|
|
|
|
32 | AB232A |