From owner-freebsd-scsi  Mon Sep  6 14:32:19 1999
Delivered-To: freebsd-scsi@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP
	id 42DD315564; Mon,  6 Sep 1999 14:32:00 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA11273;
	  Mon, 6 Sep 1999 23:19:58 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id XAA03179;
	Mon, 6 Sep 1999 23:19:07 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199909062119.XAA03179@yedi.iaf.nl>
Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic
In-Reply-To: <199909060520.XAA34103@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 5, 1999 11:20:25 pm"
To: ken@kdm.org (Kenneth D. Merry)
Date: Mon, 6 Sep 1999 23:19:07 +0200 (CEST)
Cc: rene@canyon.demon.nl, freebsd-scsi@FreeBSD.ORG,
	freebsd-hackers@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

As Kenneth D. Merry wrote ...
> Wilko Bulte wrote...
> > As Kenneth D. Merry wrote ...
...
> > 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? 
> 
> Well, perhaps.  My guess is that the intent was to catch problems with
> incorrectly written device drivers.  It looks like it may have caught a
> problem in the NCR driver somewhere. I can't remember the rationale behind
> having a panic instead of a printf at the moment.
> 
> > 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..
> 
> Apparantly so.  I sent Rene a patch to turn the panic into a printf.  The
> idea is that the error will get propagated back up, and we may be able to
> get a better idea of just what is failing.

Just had him on the phone. No luck. The driver does see 'something' out
there, but attaches it as a da device. Blurk. Sounds like completely
bogus plumbing to me. Or something just as drastic as that. On W95
with scsi board that came with the scanner things work OK, including
a sensible inquire string etc. 

So, looks like hardware to me. At least for now. The NCR810 is known
good, as is the scanner. Leaves the cable. I'm suspicious about the
HD50 to SubD25 cable (how wonderful these non-standard connectors..)

Time permitting more investigation to follow coming weekend.

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