Date: Thu, 19 Feb 2004 17:58:27 -0300 From: Cristiano Duarte <cunha17@uol.com.br> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: aic7xxx@freebsd.org Subject: Re: BUG introduced in kernels above 2.4.18 ? Message-ID: <40352373.1080201@uol.com.br> In-Reply-To: <403520000.1077219848@aslan.btc.adaptec.com> References: <4034D259.5050001@uol.com.br> <370790000.1077213725@aslan.btc.adaptec.com> <40350174.7000305@uol.com.br> <403520000.1077219848@aslan.btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Justin, Justin T. Gibbs escreveu: > The protocol violations were not checked for in earlier driver versions. > The driver has no way to know if the violation will cause harm or not. > In your situation, it may be safe to proceed, but the driver errs on > the side of safety and aborts the command instead. This is why your > scanner is not functional with later versions of the driver. I don't want to bother you, but even the kernel(aic7xxx) doesn't recognizes the scanner anymore, so IMHO that's nothing to do with SANE, am I right ? If the kernel can't recognize the scsi device, there are three points of error: the kernel, the controller or the scsi device. Is it possible that a scsi device that works on Windows, works with Adaptec Controller BIOS(it is detected by the BIOS), kernel versions 2.4.18 and before makes a protocol violation? Even if windows scsi layer doesn't check for protocol integrity, maybe the Adaptec BIOS does, and I get no errors from it. I'm so confused because the scanner works with windows, is detected by Adaptec BIOS and worked with Linux before. I don't think that the scanner has problems and there is no "driver" between the scanner and the kernel(aic7xxx). Do you still think that's a hardware problem? Is there a way to debug(or trace) the scsi protocol? Best Regards, Cristiano Duarte
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40352373.1080201>