From owner-freebsd-questions Sun Feb 28 2: 7:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id D9366151EE for ; Sun, 28 Feb 1999 02:07:42 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA64375; Sun, 28 Feb 1999 10:45:37 +0100 (CET) Message-Id: <199902280945.KAA64375@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: zdenko@CS.UH.EDU Cc: freebsd-questions@FreeBSD.ORG Subject: Re: several scsi controllers --> one bus? Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 27 Feb 1999 22:42:59 CST." <9902280442.AA07863@CS.UH.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 10:45:37 +0100 From: Gary Jennejohn Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Zdenko Tomasic writes: >Hi, > >I have all scsi system running 3.1S. There are 3 scsi controllers in 2 >pci cards: Adaptec 2940UW in the first card and Diamond Fireport40 Dual >(ncr controllers) in the second card. It appears that FBSD thinks that >there is only 1 scsi bus on all 3 controllers which I find very >confusing and odd given that there are separate scsi cables on each >card. In practice it means that I cannot have a disk on aha with ID 0 >and another one on ncr with ID 0, as that counts as conflict and at >least one of these two won't be visible. SCAM if enabled, will keep ID >all different regardless of a particular controller. I don't know if I >really managed to misconfigure my disk but my kernel config file has >only lines there are straightforward copies of LINT file and I do use >separate scbus? identifiers, but they obvuisly means something else >than what kernel prints in the dmesg file. (I don't have a copy of my >kernel config file handy, but will get it). > [dmesg output snipped] I think you're confused. The bus number is related to the controller, not the entire SCSI bus. Look more closely at your dmesg output. Here's a snippet from my dmesg. Not that ahc0 and ahc1 both have a target 4. The CAM software can easily tell them apart because they're on different controllers. Waiting 2 seconds for SCSI devices to settle sa0 at ahc1 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2049MB (4197520 512 byte sectors: 64H 32S/T 2049C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2049MB (4197520 512 byte sectors: 64H 32S/T 2049C) da3 at ahc0 bus 0 target 4 lun 0 <=== here da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2007MB (4110480 512 byte sectors: 64H 32S/T 2007C) da5 at ahc0 bus 0 target 6 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da5: 1001MB (2050860 512 byte sectors: 64H 32S/T 1001C) da4 at ahc0 bus 0 target 5 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 4340MB (8890029 512 byte sectors: 64H 32S/T 4340C) cd0 at ahc1 bus 0 target 4 lun 0 <=== and here cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 64H 32S/T 4134C) --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message