[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:	FDDI - The Next Generation

Moderator:	NETCAD::STEFANI

Created:	Thu Apr 27 1989
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2259
Total number of notes:	8590

1087.0. "DEFZA Hard error code ?" by EVTAI1::GROSSETETE () Tue Sep 14 1993 07:26

    	Hi,
    
    	Could somebody provide the meaning of hardware error code
    seen on SDA show lan/full
    
    	Fatal error code 00000009
    
    	Patrick

T.R	Title	User	Personal Name	Date	Lines
1087.1		STAR::GAGNE	David Gagne - VMS/LAN Development	`Tue Sep 14 1993 09:14`	3
	Fatal error code 9 means that the hardware/device reported an error. Is there a value listed for LAST ERROR CSR? If so, that should supply more specific information about the error reported by the device.
1087.2	CSR is 0	PRSSOS::GROSSETETE		`Thu Sep 16 1993 08:23`	6
	Dave, Last error CSR is 0000000, so what can I check ? Patrick
1087.3	error code 9 again	KERNEL::LLOYDA	Don't worry... Be Happy ;^)	`Thu Mar 31 1994 04:50`	47
	Hi, The error code 9 seems to have been reported several times in different places in this conference. Is this really a hardware error ? The reason I'm asking this is because I have the following configuration and several machines are reporting the hardware error, all of them seem to be on one DECconcentrator. All of the nodes are VS4090's with FDDI adapters (DEFZA-AA's). VS0201 crashed on the 29-MAR-1994 @ 17:05 due to what appears to be pool corruption. An hour later VS0204 logged an error against FCA1: / PEA0 "Fatal error detected by Datalink". All of the nodes identified below have reported hardware failures on their FCA0 device, one of them has already had it's controller swapped but the problem has come back again. Can you mix 4-port and 6-port cards in the concentrator ? Is this is hardware problem with the concentrator ? Can FC driver report a hardware error when actually it's an error external to the device ? Any other ideas ? Thanks, Alan Lloyd. Config: ======= Option Ports Rev DEFCN-MB A 1 B 1 A02 ? ? DEFCN-NA M 1 M 2 M 3 M 4 A03 VS0201 VS0204 ? ? DEFCN-HA 1 2 3 4 5 6 A01 VS0205 VS0202 ? EMPTY ? ? ? Node VS2080 is also connected to the concentrator but we aren't sure what port it is on.
1087.4	Help !	KERNEL::LLOYDA	Don't worry... Be Happy ;^)	`Tue Apr 05 1994 17:06`	11
	Hiya, Can anyone confirm whether error code 9 is REALLY a hardware error on the controller ? Can a software bug cause it ? Can an external network event cause it ? Any ideas ? Alan. p.s. The crash dumps are unfortunately not available.
1087.5		STAR::GAGNE	David Gagne - VMS/LAN Development	`Tue Apr 05 1994 17:37`	6
	Since there is software involved with the recording of fatal error number 9, it could certainly be a software bug. However, the intent of fatal error number 9 is to record that the LAN driver found that the device reported an error where the device needed to be reset. Usually, we store some information in the LASTERRCSR field that may be useful in knowing what the device reported to the driver.
1087.6		STAR::GAGNE	David Gagne - VMS/LAN Development	`Tue Apr 05 1994 17:42`	9
	Since your LAST ERROR CSR field has a 0 in it, we cannot tell what the device reported to the LAN driver. Is the LAN driver recovering from the error? I so, then is the problem that the errors are being reported? Or are the upper protocols not working because of the error? Can you reproduce the problem? If so, would you like another driver that may provide more information?