| Title: | TurboLaser Notesfile - AlphaServer 8200 and 8400 systems |
| Notice: | Welcome to WONDER::TURBOLASER in it's new home shortly |
| Moderator: | LANDO::DROBNER |
| Created: | Tue Dec 20 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1218 |
| Total number of notes: | 4645 |
I need some help in deciphering a uerf entry. This showed up on an
8200 on 3.2d-1 after a tape drive had an error. Once this happened the
tape drive could not be accessed and a "file" command on any device
special file in /dev would hang the process. An someone explain what
this entry is trying to tell me and if it might be related to not being
to touch any devices with the file command? Any help appreciated
Thanks in advance,
Douglas Klimas
MCI Mission Critical Support
******************************** ENTRY 1
********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 1774.
Timestamp of occurrence 07-APR-1997 20:39:29
Host name mtymsftel01
System type register x0000000C AlphaServer 8x00
Number of CPUs (mpnum) x00000002
CPU logging event (mperr) x0000000C
Event validity 1. O/S claims event is valid
Event severity 1. Severe Priority
Entry type 199. CAM SCSI Event Type
------- Unit Info -------
Bus Number 1.
Unit Number x0068 Target = 5.
LUN = 0.
------- CAM Data -------
Class x22 DEC SIM - SCSI Interface Module
Subsystem x22 DEC SIM - SCSI Interface Module
Number of Packets 2.
------ Packet Type ------ 258. Module Name String
Routine Name ss_abort_done
------ Packet Type ------ 256. Generic String
SCSI abort has been performed
******************************** ENTRY 2
********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 1773.
Timestamp of occurrence 07-APR-1997 20:39:29
Host name mtymsftel01
System type register x0000000C AlphaServer 8x00
Number of CPUs (mpnum) x00000002
CPU logging event (mperr) x0000000C
Event validity 1. O/S claims event is valid
Event severity 5. Low Priority
Entry type 199. CAM SCSI Event Type
------- Unit Info -------
Bus Number 1.
Unit Number x0068 Target = 5.
LUN = 0.
------- CAM Data -------
Class x00 Disk
Subsystem x00 Disk
Number of Packets 3.
------ Packet Type ------ 258. Module Name String
Routine Name isp_termio_abort_bdr
------ Packet Type ------ 256. Generic String
Specified IO transaction aborted
------ Packet Type ------ 1038. SIM Working Set(SIM_WS)
Packet Revision 2.
*flink xFFFFFFFF805DA2C0
*blink xFFFFFFFF805DA2C0
Controller # for HBA 1.
Target ID 5.
LUN 0.
Cam Status x0B Command Timeout
TAG x00000000
Sequence Number 55016.
Time Stamp x00000000
*nexus xFFFFFFFF805DA2C0
*it_nexus xFFFFFFFF805DAE08
*sim_sc xFFFFFFFF805D9000
*ccb xFFFFFC001C140F28
Phase Bits x00000000
Misc Flags x000A0402 Abort initiated on this request
Command has completed
SIM expects bus free phase
Timeout
Cam Flags x00004460 Disable the SIM Queue Frozen State
Attempt Sync Data Xfer - SDTR
Error Recovery x00000080 SIM_WS in process of being timed
out
Recovery Status x00000000
(*as_callback)() x0000000000000000
*as_ccb x0000000000000000
(*tmo_fn)() xFFFFFC0000548350
*tmo_arg xFFFFFC001C140D00
Rest of SIM_WS ** Not Printed **
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1164.1 | The Device at ID 5 quit responding to commands | CSC32::B_HIBBERT | When in doubt, PANIC | Tue Apr 08 1997 13:49 | 13 |
Hi Doug,
It look like the device at SCSI id 5 on bus 1 quit responding to the
system. I assume this is the tape drive that had the error.
If this is the tape drive, I would look at the tape errors that you
said occured before this event and consider replacing the drive. If
this is not the tape drive, then the device is still suspect, but I
would also consider the possibility that some other device on the bus
or a configuration problem may have caused a bus hang.
Brian Hibbert
| |||||
| 1164.2 | other busses on kftia had same problem | CSC32::KLIMAS | Tue Apr 08 1997 18:13 | 12 | |
Thanks for the reply. I thought it might be something like that but
just wanted clarification. I did not want to put in too much detail
but the only other strange thing was the tape drive is on a separate
dwzza off of a kftia and we could not issue a file command on the
devices attached to the other dwzza's off the kftia module either. A
reboot seems to have fixed it, as I expected, but I don't know what
would cause the file command to hang on the other buses too.
Thanks again for your previous response.
Doug
| |||||