Re: aha1542 vs. DAT vs. kernel 2.0.x

[Eric Youngdale]

> I have a number of devices on my 1542 bus.  Several of them are cdroms, > and if I can manage to trigger behavior that slows them down enough, > I get bus resets.  Actually, I get bus resets on anything that should > probably have been an I/O error.  I've never seen an I/O error, however. > Things don't return after a bus reset to give an I/O error.     One of the bugs I fixed in the patchset that I mailed out would cause the error handling code to incorrectly try and issue bus resets in the event of a media error.  After some number of retries, it should just pass the I/O error up to the upper level driver and be done with it.  Instead it was waking up the error handler, and as I recall it started trying to reset the bus.   Pretty pointless. > I think perhaps there are at least two bugs here--the one that caused > the (unnecessary?) reset, and the one that didn't properly clean up > the device after the reset.     The first one I think I already got.  The second one I don't know about.  That is why I was thinking I should try adding a disk to the bus with the screwy cdrom, and see whether the disk is usable after the cdrom is taken offline. > (BTW: the changer dies randomly if I stick in certain commercial mixed > multisession cd's.  It seems to get confused; it works if I read things > in a certain order, but just thrashes forever trying to find the TOC if I > ask for the wrong thing first.  The bus reset DOES reset it.  Sometimes.) -Eric