Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 5 Sep 1999 20:45:42 +0200 (CEST)
From:      Wilko Bulte <wilko@yedi.iaf.nl>
To:        ken@kdm.org (Kenneth D. Merry)
Cc:        rene@canyon.demon.nl, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject:   Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic
Message-ID:  <199909051845.UAA05110@yedi.iaf.nl>
In-Reply-To: <199909042352.RAA27822@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 4, 1999  5:52:47 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
As Kenneth D. Merry wrote ...
> Rene de Vries wrote...
> > Hi,
> > 
> > Today I bought a Umax 1220S scanner and tried to connect this to my FreeBSD
> > Stable (3.3RC) system. I added a NCR810 specially for the scanner (I don't
> > want such a device on the same bus as my root disk which is on an aic7890).
> > The kernel boots perfectly with both scsi adapters configured
> > (as expected ;-), but as soon as the scanner is connected to the NCR810
> > the kernel panics.
> > The scanner is the only device on that bus and termination is ok.
> > The message is: "cam_periph_error: scsi status of CHECK COND returned but no
> > sense information is availible. Controller should have returned
> > CAM_AUTOSENSE_FAILED" (line 1441 of cam_periph.c). As far as understand the
> > comments there, this means that the ncr810 driver did something cam did not
> > expect. (This all happens during booting, at the time when the devices are
> > probed.)
> > For now I've connected the scanner to my other PC running W95 where its
> > seems to work as expected.
> > I hope someone can help me finding what the problem is and how to fix it.
> 
> It sounds like there may be a couple of things going on.  First, your
> scanner may not be returning sense information properly.
> 
> Second, the NCR driver may be doing something wrong.
> 
> It would be helpful if you could hook this up to your 7890 controller and
> see what happens.  In general, the Adaptec driver behaves a little better
> than the NCR driver.

The relevant code snippet is:

 } else if (ccb->csio.scsi_status ==
                                   SCSI_STATUS_CHECK_COND
                                && status != CAM_AUTOSENSE_FAIL) {
                                /* no point in decrementing the retry count
*/
                                panic("cam_periph_error: scsi status of "
                                      "CHECK COND returned but no sense "
                                      "information is availible.  "
                                      "Controller should have returned "
                                      "CAM_AUTOSENSE_FAILED");
                                /* NOTREACHED */
                                error = EIO;

Even if we assume the scanner yelled for attention and/or the ncr
driver is at fault I don't really understand why the cam layer 
decides to panic the machine. Wouldn't it be sufficient to return
EIO, or maybe just whine on the console? 

IIRC I've seen systems report 'no sense' in their log files in situations
like this (non-FreeBSD systems that is). So I *guess* there are 
SCSI devices out there that exhibit this behaviour..

Wilko
-- 
|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909051845.UAA05110>