[684] in linux-scsi channel archive
Re: Serious problem with SCSI error handling
daemon@ATHENA.MIT.EDU (Angelo Haritsis)
Wed Oct 11 23:03:13 1995
From: Angelo Haritsis <ah@doc.ic.ac.uk>
To: ncr53c810@mroe.cs.colorado.edu, linux-scsi@vger.rutgers.edu
Date: Wed, 11 Oct 1995 20:19:00 +0100 (BST)
In-Reply-To: <199510111633.MAA20527@orixa.mtholyoke.edu> from "Jurgen Botz" at Oct 11, 95 12:32:55 pm
> Conclusion: the SCSI code has a bug (or bugs) that throw things into
> a bad state on certain disk errors that it *should* be able to recover
> from. This does not appear to be in the NCR driver, but more likely
> in the higher level SCSI disk code, since Dave saw the same problem
> with a different controller. The problem seems to exist in kernel
> versions at least 1.2.x through 1.3.32.
I have also discovered problems with scsi code in relation to bad
sectors on CDROM. Well yes I did have a "bad" cdrom which can
be easily created by you at any time by somehow covering a small
part of its useful surface (in my case it was simply a finger print).
The cdrom's bad blocks caused a total hang of the system (ncr53c810).
The errors were coming from the middle level scsi code if I remember
well. But feel free to try it yourselves!
BTW, the same cdrom was use under DOS; when reads reached the "bad" area
I got the familiar "Abort Retry Ignore" error. But no hang.
Angelo
--
#include <standard.disclaimer.h>
Angelo Haritsis, Applied Systems Section
s-mail: Dpt of Computing,Imperial College, 180 Queen's Gate, London SW7 2BZ, UK
e-mail: ah@doc.ic.ac.uk - tel:+44 171 594 8390 - fax:+44 171 581 8024
