Ok.
I have found a difference in the timeouts. V1 driver it is 275ms, V2
driver it is 250ms. It looks like that extra 25ms is needed on the sun4c
:).
I will do a quick test with the existing setup as a modular ESP and then
re-build with a 275ms timeout and see if that fixes the problem.
Regards
Mark Fortescue.
On Fri, 20 Jul 2007, James Bottomley wrote:
On Fri, 2007-07-20 at 16:22 +0100, Mark Fortescue wrote:
Thansk for the info. I will try some experiments and see if I can work
out where the scsi commands/responses are getting lost.
Actually, for ESP it looks like you can alter the timeout ... it's the
parameter ESP_BUS_TIMEOUT in drivers/scsi/esp_scsi.h
It could be that the register calculation is off here ... but someone
who knows the device would have to look at it (or you could time it, I
suppose).
I do not beleave the issue with the ESP is a hardware problem. The PROM
and SunOS-4.1.1 have no problem finding/accessing the disk on the ESP and
I did not observe any issues prior to testing Linux v2.6.22. The V1 ESP
SCSI driver never failed to find the ESP disk (on kernels that got that
far) but I have not done as much testing with the V2 ESP driver as memory
problems post v2.6.21 needed to be fixed to get things up and running.
James
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
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
