Date: Tue, 11 Feb 1997 20:23:35 +0100 From: se@freebsd.org (Stefan Esser) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: robsch@robkaos.ruhr.de (Robert Schien), freebsd-scsi@freebsd.org Subject: Re: Problem with 3701B CD-ROM Message-ID: <19970211202335.YC36261@x14.mi.uni-koeln.de> In-Reply-To: <Mutt.19970211015120.j@uriah.heep.sax.de>; from J Wunsch on Feb 11, 1997 01:51:20 %2B0100 References: <m0vtw81-00065tC@robkaos.ruhr.de> <Mutt.19970211015120.j@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 11, j@uriah.heep.sax.de (J Wunsch) wrote: > As Robert Schien wrote: > > > /kernel: cd0 at scbus0 target 2 lun 0: COMMAND FAILED (9 0) @f20ba800. > > /kernel: cd0 at scbus0 target 2 lun 0: extraneous data discarded. > > > > The errors disappear when the kernel option FAILSAFE is set. > > That would mean they don't grok tagged queuing. Like just about any CDROM drive on the market today :) I've never had a single problem with my Toshiba 3601, and I think the error is caused by some application sending an invalid request. What program did access the CDROM drive at that time ? > When reviewing Mark Gourney's (sp?) various SCSI-related section 9 > manpages, i learned that we support quirk entries for drives that > don't grok tagged commands. Perhaps we should start populating > scsiconf.c with entries for ``known rogues''. Well, I did the "NEW_SCSICONF" changes back in September 1994, in part to move some of the code that dealt with buggy devices out of the NCR driver. No driver (writer) took notice, even after you made the new code the default (in December 1995). Justin Gibbs' new generic SCSI code will take care of tagged commands, and I suggest to just wait for him to complete his interfaces, before any driver is modified ... Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970211202335.YC36261>