On Feb 7, 2007, at 3:11 AM, Darrick J. Wong wrote:
Wu, Gilbert wrote:
Hi James,
We are investigating this issue here. We will update the status
when
we can duplicate the problem here and root cause.
FWIW,
v17 looks good for both SAS/SATA load testing. The 24-disk x260 seems
to have crapped out after about 800 rounds of load/unload due to the
phys reporting devices, then no devices about 10s later, and then
having
the module unloaded before the dead SAS commands finished returning.
Not sure what that's about, though I might also have borked the
x260 :(
Though who really is going to reboot the machine 800 times in rapid-
fire
succession???
(I'm not trying to slam the v28 sequencer, I'm merely providing a
baseline for comparison between the two. It may very well be the case
that all the bugs we used to observe with v17 were merely a result
of us
poking the sequencer the wrong way....)
My understanding is that the new sequencer has moved some registers
and so each version of the sequencer would have to be run with a
driver coded for that particular version of the sequencer. If you are
trying to use the same driver with both versions of the sequencer,
bad things will happen unless you have a driver that can recognize
both versions and handle each appropriately. I don't think that the
aic94xx driver as it exists can do that.
Please excuse me if you were already aware of this, but if you
weren't I wanted to try to short-circuit some of your head-banging.
--
Mark Rustad, MRustad@xxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
