Many thanks to:
Dr. Tom Blinn [tpb_at_doctor.zk3.dec.com]
alan_at_nabeth.cxo.dec.com
and Roy Gregory (r.gregory_at_cqu.edu.au) who took the time to dig through the
archives, and found the specific information we needed to solve this problem
:)
[Solution]
By applying the following to the /etc/ddr.dbase file, all the cam errors and
kernel panacis have stopped!
SCSIDEVICE
#
Type = disk
Name = "QUANTUM" "FIREBALL ST6.4S"
#
PARAMETERS:
TaggedQueuing = disabled
Thanks to both Tom and Alan for puttting us on the right track, it would
seem that the 4.0f cam driver is a little more pedantic about compliancy
than 4.0b. Needless to say that the problem was solvable and we are now back
on the air.
Thanks Again
Adrian Yarrow - Unix Systems Manager
Information Technology Division
Central Queensland University
QLD Australia 4702
Ph 07 49309996
Email a.yarrow_at_cqu.edu.au
My original post:
Dear Managers,
Last Sunday (Australian EST) I upgraded an AS255 from 4.0b through 4.0e
to 4.0f, as per Compaq's update installation guidelines. As is required,
I applied 4.0f patch 1 and ensured that the AS255's firmware was updated
to ver 5.4. Since this upgrade we have been having no end of trouble with
the stablity of this sysem:
System configuration:
AlphaStation 255/300
RAM: 192.00 megabytes.
DISKS:
rz0 at scsi0 target 0 lun 0 (LID=0) (QUANTUM FIREBALL ST6.4S 0F0C)
rz1 at scsi0 target 1 lun 0 (LID=1) (DEC RZ29B (C) DEC 0016)
rz2 at scsi0 target 2 lun 0 (LID=2) (DEC RZ28M (C) DEC 0568)
rz3 at scsi0 target 3 lun 0 (LID=3) (DEC RZ29L-AS (C) DEC 0654)
rz4 at scsi0 target 4 lun 0 (LID=4) (DEC RRD45 (C) DEC 0436)
GRAPHICS: ZLXp2-E, Revision: 34
SECONDARY NIC: DEC TULIP (10/100) Ethernet Interface
DLT: TZ88 20/40
Note that rz0 (which contains the OS) is a Quantum disk. The system's
/etc/disktab has the folowing entry to enable the use of this disk:
quantum64|Quantum 6.4S:\
:ty=winchester:dt=SCSI:ns#63:nt#15:nc#13328:\
:oa#0:pa#262144:ba#8192:fa#1024:\
:ob#262144:pb#401408:bb#8192:fb#1024:\
:oc#0:pc#12594960:bc#8192:fc#1024:\
:od#663552:pd#4096000:bd#8192:fd#1024:\
:oe#4759552:pe#4096000:be#8192:fe#1024:\
:of#8855552:pf#3739408:bf#8192:ff#1024:\
:og#663552:pg#11931408:bg#8192:fg#1024:\
:oh#4468736:ph#3911344:bh#8192:fh#1024:
I orginally suspected this device to be causing the crashes as and have
since replaced it with another. and yet the crashing continues.
NOTE: We have two other system's which are identically configured the same
as this one. Those two are still running 4.0b and we are having no
difficulties at all. This was also the case with this system prior to the
4.0f upgrade last Sunday.
Looking at the logged events using dia, there are numerous entries
pertaining to CAM errors (some specifically pertaining to the Quantum
Drive, some just general CAM time outs). If anyone is keen to have a look
at them I can email them to you instead of making the communique any
longer :)
What have I missed ? Is there anything else I should do under 4.0f beside
a disktab entry for the quantum drive ?
I would really appreciate any suggestions that People can offer and will
tabulate a summary to the list.
Received on Wed Aug 25 1999 - 23:02:08 NZST