> - check all the cables, they should be the shorter you can
> - Use an active terminator
> - check the termination power on the disk
I've been getting these for a while too. They only started after 2.0.12
and seem to be related to the rewrite of aic7xxx code.
If I enable scb paging and tagged queuing, the machine goes down in a
screaming heap about 24-26 hours later from 2.0.13 thru to 2.0.24 but is
relatively stable if they're not enabled. The symptom is a continuous
message "aiee scheduling in interrupt". If not compiled with these
options enabled the machine lasts 3-5 days before crashing.
2.0.25-2.0.27 have the same timeout error report as Michael has seen and
if tscb paging/tagged queuing are enbled I get pretty well equal
instances of timeouts and interrupt errors.
The machine is a news box and the scsi bus is _VERY_ busy. We're talking
5-8 writes per second on average, with peaks up to 20 writes per second.
Reads run at about 5-6 times the number of writes.
I've checked cabling, terminators and termination power. They all seem OK
and I've made no changes to the setup for 6 months in any case.
Running Adaptec bios tests on the drives shows them as being fine. No bad
sectors or odd errors reported at all at that level.
Michael, are you running on a Saturn PCI chipset?
AB
-- Junk email returned, in bulk, back to sender; w/copies to all postmasters.