From owner-freebsd-scsi  Sun May 25 18:59:39 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA21486
          for freebsd-scsi-outgoing; Sun, 25 May 1997 18:59:39 -0700 (PDT)
Received: from cicerone.uunet.ca (cicerone.uunet.ca [142.77.1.11])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21477
          for <scsi@FreeBSD.ORG>; Sun, 25 May 1997 18:59:34 -0700 (PDT)
Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115296-16811>; Sun, 25 May 1997 21:57:26 -0400
Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id VAA02457; Sun, 25 May 1997 21:57:18 -0400 (EDT)
Date: Sun, 25 May 1997 21:57:17 -0400
From: Andrew Herdman <andrew@why.whine.com>
X-Sender: andrew@why
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: scsi@FreeBSD.ORG, Andrew Herdman <andrew@why.whine.com>
Subject: Re: Oddness with NCR53C810
In-Reply-To: <19970524102943.GO37893@uriah.heep.sax.de>
Message-ID: <Pine.BSF.3.95.970525215538.2439A-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 24 May 1997, J Wunsch wrote:

> As Andrew Herdman wrote:
> 
> > ncr0 <ncr 53c810a scsi> rev 17 int a irq 12 on pci0:11:0
> > ncr0 waiting for scsi devices to settle
> > scbus1 at ncr0 bus 0
> > ^^^^^
> >   This is it... it stops here.
> 
> Do you have scbus1 hardwired to ncr0 in your kernel?
> 
> ncr0 <ncr 53c810a scsi> rev 18 int a irq 12 on pci0:9:0
> scbus0 at ncr0 bus 0
> ...
> ncr1 <ncr 53c810 scsi> rev 2 int a irq 11 on pci0:12:0
> scbus1 at ncr1 bus 0

Yes, this is the relevant kernel config:

controller      bt0
controller      ncr0
controller      scbus0  at bt0
controller      scbus1  at ncr0

> Mine are working.  scbus1 used to be on an AHA2940 until i had to free
> up the Adaptec for other purposes.  Interesting, i never noticed i've
> got two different NCRs until now. :)
> 
> Maybe boot -v would show you some more messages.

Boot -v does show more information, but the hang still happens at the
exact same spot.

Thanks 
  Andrew