Hi there
ES40 running Tru64 v4.0f bounced last night with errors caused by emx
(emulex fibre channel) driver errors.
Here is an extract from the Binnary Errorlog :-
**** V3.3 ********************* ENTRY 16 ********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 2758.
Timestamp of occurrence 27-SEP-2000 04:15:35
Host name hudson
System type register x00000022 Systype 34. (Regatta Family)
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000000
Event validity 1. O/S claims event is valid
Event severity 1. Severe Priority
Entry type 302. ASCII Panic Message Type
-1. - (minor class)
SWI Minor class 9. ASCII Message
SWI Minor sub class 1. Panic
ASCII Message panic (cpu 0): Emulex Adapter HW Error
detected
**** V3.3 ********************* ENTRY 17 ********************************
And near the end of the error entry :-
****************************************************************************
******
Read Status MBX Reg 3 x00000000 Transmit Byte Count.
Read Status MBX Reg 4 x00000000 Receive Byte Count.
Read Status MBX Reg 5 x00000000 Transmit Frame Count.
Read Status MBX Reg 6 x00000000 Receive Frame Count.
Read Status MBX Reg 7 x00000000 Transmit Sequence Count.
Read Status MBX Reg 8 x00000000 Receive Sequence Count.
Read Status MBX Reg 9 x00000000 Total Exchanges by this Adapter.
Read Status MBX Reg 10 x00000000 Total Exchanges - Adapter is Responder.
Read Status MBX Reg 11 x00000000 Number of P_busy Response Frames.
Read Status MBX Reg 12 x00000000 Number of F_busy Response Frames.
IOCB Word 0 x00000000
IOCB Word 1 x00000000
IOCB Word 2 x00000000
IOCB Word 3 x00000000
IOCB Word 4 x00000000
IOCB Word 5 x00000000
IOCB Word 6 x00000000
IOCB Word 7 x00000000 IOCB Command Status: x00000000
IOCB Command Type: x00000000
Driver Name KGPSA
Driver Revision 1.21
Module Name emx_log_adap_err
Error Message status 0x40000000: HW ERR:IBUS Parity
Error
Channel Address in Loop
****************************************************************************
*********
Does anyone know whythis is caused and how we can avoid this in the
future..????
Any help will be much appreciated
THanks in advance
Paul Sinclair
Legal Disclaimer : This e-mail is for the intended recipient only.
If an addressing or transmission error has misdirected this e-mail,
please notify the sender by replying to this e-mail. If you are not
the intended recipient you must not use, disclose, distribute, copy,
print or rely on this e-mail. The opinions expressed in this message
are those of the sender and not those of KSCL.
This footnote also confirms that this e-mail has been swept by
MIMEsweeper for the presence of computer viruses.
Received on Wed Sep 27 2000 - 08:50:41 NZST