Subject: Re: Time to delete ncr.c?
To: Frank van der Linden <fvdl@wasabisystems.com>
From: Chuck Silvers <chuq@chuq.com>
List: current-users
Date: 11/19/2000 19:56:27
On Sun, Nov 19, 2000 at 01:42:05PM +0100, Frank van der Linden wrote:
> On Thu, Nov 16, 2000 at 11:06:46PM -0800, Chuck Silvers wrote:
> > I tried it again with -current from today.  (the problem with the card
> > was some kind of conflict with the adaptec scsi on the motherboard.
> > disabling the built-in scsi made the symbios card happier.)
> > now I can play audio, but I can't rip audio to disk with tosha.
> > tosha works fine with the ncr driver.  the symptoms are the same
> > as before.  on the console there is:
> 
> This was an error in the interaction between the tosha and libscsi
> packages. libscsi resets the timeout in its scsi_build() function,
> but tosha was setting the timeout before calling scsi_build(), and
> hence never got the intended 10s timeout, but always 2s.
> 
> Ripping audio does need a somewhat larger timeout sometimes, it is
> not strange that with a 2s timeout things would time out depending
> on system load, SCSI bus state, device state and phase of the moon.
> 
> I fixed the package, so if you re-install the tosha pkg it should
> be ok, and both your PRs can be closed.

yup, tosha works now.  I've closed the PRs.
it did occur to me that the problem might be in tosha,
but I couldn't get any other rippers to work at all with any driver.
tosha always worked with ncr and always failed with siop and ahc...

at any rate, my concern with removing the ncr driver is resolved.
thanks!


> A seperate matter is, if SCIOCCOMMAND ioctls that come from userspace
> should trigger drivers into resetting devices or the whole bus. Shouldn't
> it just pass back the timeout to the application, letting it deal
> with it? I believe in our current SCSI layer that would be to
> set XS_NOERROR. Well, anyway.

that sounds reasonable to me, but I'll let you wrangle with the other
usual scsi folk on error-handling policy.

-Chuck