[snip]
> The system, however, still locks up for 30 seconds to several minutes
> several times a day. After three weeks of trying to find some solution
> to the problem, I'm running out of things to try. My last attempt was to
> lower the CPU Bus speed from 100.3 to 88.3 (which required underclocking
> the PII CPU from 400Mhz to 333Mhz). Still, no luck.
>
> I'd really appreciate any suggestions. After three weeks of this, I'm
> just at a dead end.
[snip]
Please accept these suggestions in the spirit in which you asked,
not as the well-thought-out advise of an expert. ('Cause I ain't).
I feel your pain. As usual for ventures in SCSI-land, we'll assume
you've made appropriate ritual sacrifices & etc.
Regarding the "built in terminator" you mentioned
in your original posting. Any possibility of swapping out
that cable, perhaps adding a discrete terminator?
Have you played around in the 'SCSI-select' BIOS utility,
and if so what can you report about those settings? What happens
when you drop the scsi bus to half speed?
Do the drive cases themselves get _hot_? It's almost
conceivable that one of the drives is trying to do a 'thermal
recalibration' because of inadequate cooling... ?
Next thing, can you make the trouble happen more frequently, say,
by running kernel compilations in the background?
Speaking of compiling the kernel, is SCSI logging turned on _and_ enabled?
>From the Configuration.help file (2.2.14):
CONFIG_SCSI_LOGGING
This turns on a logging facility that can be used to debug a number
of SCSI related problems.
If you say Y here, no logging output will appear by default, but you
can enable logging by saying Y to "/proc filesystem support" and
"Sysctl support" below and executing the command
echo "scsi log token [level]" /proc/scsi/scsi
at boot time after the /proc filesystem has been mounted.
There are a number of things that can be used for 'token' (you can
find them in the source: drivers/scsi/scsi.c), and this allows you
to select the types of information you want, and the level allows
you to select the level of verbosity.
If you say N here, it may be harder to track down some types of SCSI
problems. If you say Y here your kernel will be somewhat larger, but
there should be no noticeable performance impact as long as you have
logging turned off.
If you have the luxury of running _without_ RAID configured,
and if so, do you still see these symptoms?
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
