From owner-freebsd-scsi Fri Jun 11 10: 5:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id 6EC4E14CB5 for ; Fri, 11 Jun 1999 10:05:51 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 42065 invoked by uid 1003); 11 Jun 1999 17:05:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 Jun 1999 17:05:50 -0000 Date: Fri, 11 Jun 1999 13:05:50 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Steve Bishop Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: scsi probe at boot time In-Reply-To: <37614186.383B1A01@iserver.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 11 Jun 1999, Steve Bishop wrote: > The SCSI Controller (host adapter) resets the bus, and then scans it, and sees > everything. It is the OS that locks up the changer with a bus reset, and then > just sees the drives. The bus reset seems to lock the changer up immediately, so > that as soon as the SCSI_DELAY period begins, it's already locked up. > > This, of course, points to this being a Spectralogic problem since the bus > reset causes the changer to lock up regardless of whether it's the OS, or > the SCSI controller. > > I don't remember seeing this problem with Solaris, but maybe it doesn't do > a bus reset during boot. > Unfortunately, we never put one of these on a FreeBSD system; but they seemed ok on other Unices (and Windoze NT for that matter). On occasion, they would lock during the probes and not be seem by the OS, but it wasn't consistent. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message