[1009] in linux-scsi channel archive
Re: ncr53c8xx panic
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Sun Nov 24 06:35:27 1996
Date: Sun, 24 Nov 1996 13:33:33 +0000 (GMT)
From: Gerard Roudier <groudier@club-internet.fr>
To: Dan Hollis <goemon@sasami.anime.net>
cc: linux-scsi@vger.rutgers.edu, linux-raid@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.95L01at.961123160715.23040C-100000@sasami.anime.net>
On Sat, 23 Nov 1996, Dan Hollis wrote:
> We have tried several cables and terminators. The system runs fine for
> some time (days) then crashes.
It is easier to fix a problem that appends every minute than a problem
that happens every month. The difference is that it is possible to live
with the second one.
> Isn't there any better error recovery than to blow up completely on the
> first error? The Buslogic driver seems to handle error conditions much
> better, in that it actually tries very hard to recover (resetting
> individual devices, then resorting to scsi bus resets, etc).
The error recovery of Leonard's BusLogic driver is probably better than
error recovery of the ncr53c8xx driver and in my opinion, better than
error recovery of other low-level scsi drivers.
In my opinion, the reasons are the following:
1) Leonard is cleverer than Gerard :)
2) Gerard is more lazzy than Leonard :)
I am kidding.
Error recovery is probably the hardest thing to design, implement and test.
Leonard has done a very good work about this in his driver.
Error recovery is not only the busyness of low-level drivers.
Middle and upper scsi drivers are involved and the kernel too.
My opinion is that the current scsi code have silly error recovery
procedures.
Severall months ago, a theard about rewrite of the scsi code let me think
that Linux community had lots of volunteers for doing this work.
I decided to wait for this improvement prior to spending time for error
recovery improvement in the ncr53c8xx driver.
Seems now that this thread was just blablablas ...
Error recovery improvement in the ncr53c8xx driver and rewrite of the
linux scsi code will be done for the 2.2.
It is only a question of priorities and time.
Gerard.
