From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 7 11:01:50 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4D6016A4D3 for ; Mon, 7 Feb 2005 11:01:50 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD39B43D48 for ; Mon, 7 Feb 2005 11:01:50 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j17B1ohp059371 for ; Mon, 7 Feb 2005 11:01:50 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j17B1nmp059365 for freebsd-scsi@freebsd.org; Mon, 7 Feb 2005 11:01:49 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 7 Feb 2005 11:01:49 GMT Message-Id: <200502071101.j17B1nmp059365@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 11:01:51 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2000/08/18] kern/20689 scsi Newbusified version of ncr driver does no f [2001/05/03] kern/27059 scsi (symbios) SCSI subsystem hangs under heav o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug f [2002/09/15] kern/42796 scsi NCR/SYM 53C825 driver detects scsi cdrom f [2002/11/25] kern/45713 scsi If you use the amr driver, it is impossib f [2002/12/09] kern/46152 scsi Panic in adw dumping to tape f [2003/05/16] kern/52331 scsi 4.7 to 4.8-REL upgrade: SCSI disks on sym f [2003/09/14] kern/56759 scsi [hang] System freezes when writing CD Adv f [2003/09/14] kern/56760 scsi [hang] system hangs at boot with adaptec f [2003/09/14] kern/56871 scsi dd can't write variable length data block f [2003/09/18] kern/56973 scsi SCSI errors from on-board Adaptec (AIC7xx s [2003/09/30] kern/57398 scsi Current fails to install on mly(4) based o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with a [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/09/15] kern/71778 scsi 5.3 BETA3 doesnt see Adaptec 2015S FW Rev o [2004/12/02] kern/74607 scsi FreeBSD 5.3 install CD crashes on SCSI de o [2004/12/29] kern/75603 scsi 5.3 kernel crash 19 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57468 scsi [patch] Quirk for Quantum LPS540S o [2003/10/01] kern/57469 scsi [patch] Quirk for Conner CP3500 o [2004/09/22] kern/72010 scsi [patch] mt -f /dev/rsa0.ctl comp off, or 8 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 16:45:27 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C6316A4CE for ; Tue, 8 Feb 2005 16:45:27 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 286B343D49 for ; Tue, 8 Feb 2005 16:45:27 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1CyYUO-0003tg-IT for freebsd-scsi@freebsd.org; Tue, 08 Feb 2005 18:45:24 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Feb 2005 18:45:24 +0200 From: Danny Braniss Message-ID: Subject: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 16:45:27 -0000 i have been writing a driver for the iSCSI, and am concentrating on the initiator side. So far i mannaged to get to first base, ie, managed to login onto a target, but now im stuck. After several hours of reading/searching, this is avoiding me: how can i get the CAM to probe for devices on this 'controller'? thanks, danny From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 17:14:36 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAC4516A4CE for ; Tue, 8 Feb 2005 17:14:36 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84EA343D39 for ; Tue, 8 Feb 2005 17:14:36 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id j18HETDb062440; Tue, 8 Feb 2005 10:14:29 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id j18HES3s062439; Tue, 8 Feb 2005 10:14:28 -0700 (MST) (envelope-from ken) Date: Tue, 8 Feb 2005 10:14:28 -0700 From: "Kenneth D. Merry" To: Danny Braniss Message-ID: <20050208171428.GA62414@nargothrond.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on nargothrond.kdm.org X-Virus-Status: Clean cc: freebsd-scsi@freebsd.org Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 17:14:37 -0000 On Tue, Feb 08, 2005 at 18:45:24 +0200, Danny Braniss wrote: > i have been writing a driver for the iSCSI, and am concentrating > on the initiator side. > So far i mannaged to get to first base, ie, managed to login onto a target, > but now im stuck. > After several hours of reading/searching, this is avoiding me: > how can i get the CAM to probe for devices on this 'controller'? camcontrol devlist [ find out which scbus number your controller is ] camcontrol rescan N [ where N is the number of the SCSI bus for your controller ] You can either do that, or just reboot, and your bus will get scanned when the transport layer cranks up. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 17:25:53 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32A9C16A4CE for ; Tue, 8 Feb 2005 17:25:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AE9343D2D for ; Tue, 8 Feb 2005 17:25:52 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j18HQCWs004314; Tue, 8 Feb 2005 10:26:12 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <4208F618.3000400@freebsd.org> Date: Tue, 08 Feb 2005 10:25:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 17:25:53 -0000 Danny Braniss wrote: > i have been writing a driver for the iSCSI, and am concentrating > on the initiator side. > So far i mannaged to get to first base, ie, managed to login onto a target, > but now im stuck. > After several hours of reading/searching, this is avoiding me: > how can i get the CAM to probe for devices on this 'controller'? > thanks, > danny > A scan is performed when CAM gets an XPT_SCAN_BUS command. This happens automatically during boot after the XPT_RESET_BUS command finishes. A driver or userland app can send an XPT_SCAN_BUS command at any time via various interfaces. However, you've just hit the first big blocker in iSCSI support. CAM is oriented around parallel SCSI, and in parallel SCSI you do a linear scan of targets from 0 to 7 or 15, depending on the bus width. LUNs are also scanned linearly on each target, though we need to implement the REPORT_LUNS feature so that we can efficiently detect high LUNs without needing a linear scan. Anyways, the linear scan of targets works because the range is very small and bounded. For iSCSI, this obviously won't work. CAM has no concept of iSCSI addresses, and even if it did, doing a linear scan of even a small subnet would be prohibitively expensive. What is really needed is a new XPT layer that understands iSCSI. By this, I mean a layer that understands how to properly scan and detect targets, how to log into them, etc. It should also have a certain amount of flexibility so that hardware-assisted solutions can plug in and pick-and-choose the pieces they need from the transport layer. Lucent did an iSCSI initiator for FreeBSD 4.x a while back and I think they got around all of this by telling CAM not to auto-scan at boot, followed by having the driver announce devices to CAM directly (look at the ATAPI-CAM code for an example of how to do this) and do all the detection and login work behind CAM's back. This really should only be considered a hack though. If you're interested, I might be able to dig up the link to it. We never pursued integrating it to the FreeBSD tree because of very restrictive licensing terms on it. I started some preliminary work last spring on cleaning up CAM to segregate parallel SCSI knowledge into its own module. This should eventually allow a system where multiple XPT modules can live together and each provide a different transport. At the end, I'd like to see transports for p-scsi, iscsi, sas, ata/sata, and fc. This is of course in my fantasy world of inifinite hacking time =-) If you're interested in helping, I'd love to talk to you some more offline. Please don't let this scare you away from what you're doing. iSCSI support is badly needed, and I'm thrilled that your working on it. If there is anything I can do to help, please ask. Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 17:50:37 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B404C16A4CE; Tue, 8 Feb 2005 17:50:37 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B011D43D46; Tue, 8 Feb 2005 17:50:36 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1CyZVQ-000668-Oi; Tue, 08 Feb 2005 19:50:32 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Scott Long In-Reply-To: Message from Scott Long of "Tue, 08 Feb 2005 10:25:44 MST." <4208F618.3000400@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Feb 2005 19:50:32 +0200 From: Danny Braniss Message-ID: cc: freebsd-scsi@freebsd.org Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 17:50:37 -0000 > Danny Braniss wrote: > > > i have been writing a driver for the iSCSI, and am concentrating > > on the initiator side. > > So far i mannaged to get to first base, ie, managed to login onto a target, > > but now im stuck. > > After several hours of reading/searching, this is avoiding me: > > how can i get the CAM to probe for devices on this 'controller'? > > thanks, > > danny > > > > A scan is performed when CAM gets an XPT_SCAN_BUS command. This happens > automatically during boot after the XPT_RESET_BUS command finishes. A > driver or userland app can send an XPT_SCAN_BUS command at any time via > various interfaces. > > However, you've just hit the first big blocker in iSCSI support. CAM is > oriented around parallel SCSI, and in parallel SCSI you do a linear scan > of targets from 0 to 7 or 15, depending on the bus width. LUNs are also > scanned linearly on each target, though we need to implement the > REPORT_LUNS feature so that we can efficiently detect high LUNs without > needing a linear scan. Anyways, the linear scan of targets works > because the range is very small and bounded. > > For iSCSI, this obviously won't work. CAM has no concept of iSCSI > addresses, and even if it did, doing a linear scan of even a small > subnet would be prohibitively expensive. What is really needed is a new > XPT layer that understands iSCSI. By this, I mean a layer that > understands how to properly scan and detect targets, how to log into > them, etc. It should also have a certain amount of flexibility so that > hardware-assisted solutions can plug in and pick-and-choose the pieces > they need from the transport layer. > i was thinking in tricking the CAM layer in thinking that the iSCSI is a HBA, with only one bus/target, at least till i can understand the protocol, then it will be time to see how many session/targets can be realized. > Lucent did an iSCSI initiator for FreeBSD 4.x a while back and I think > they got around all of this by telling CAM not to auto-scan at boot, > followed by having the driver announce devices to CAM directly (look at > the ATAPI-CAM code for an example of how to do this) and do all the > detection and login work behind CAM's back. This really should only be > considered a hack though. If you're interested, I might be able to dig > up the link to it. We never pursued integrating it to the FreeBSD tree > because of very restrictive licensing terms on it. > i got the lucent driver, if that's what you mean by digging up ... > I started some preliminary work last spring on cleaning up CAM to > segregate parallel SCSI knowledge into its own module. This should > eventually allow a system where multiple XPT modules can live together > and each provide a different transport. At the end, I'd like to see > transports for p-scsi, iscsi, sas, ata/sata, and fc. This is of course > in my fantasy world of inifinite hacking time =-) If you're interested > in helping, I'd love to talk to you some more offline. > sure! > Please don't let this scare you away from what you're doing. iSCSI > support is badly needed, and I'm thrilled that your working on it. If > there is anything I can do to help, please ask. im not scared, just can't see the wood because of the trees :-) i mean, trying to write a klm/iSCSI/CAM/SCSI/TCP-IP driver is fun, but can't expect to know SAM-n, sockets, threads/mutex/etc, etc. i'm trying to work with what there is, and in the way try to learn how iSCSI works. in doing so, trying to design the software. the next thing i need, and im looking now at the atapi-cam, is to figure out how i can tye my loose ends. > > Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 21:49:57 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93E4E16A4CE; Tue, 8 Feb 2005 21:49:57 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 042A943D41; Tue, 8 Feb 2005 21:49:57 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j18LnuHd090613; Tue, 8 Feb 2005 15:49:56 -0600 (CST) (envelope-from dan) Date: Tue, 8 Feb 2005 15:49:56 -0600 From: Dan Nelson To: Scott Long Message-ID: <20050208214956.GA3104@dan.emsphone.com> References: <4208F618.3000400@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4208F618.3000400@freebsd.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 21:49:57 -0000 In the last episode (Feb 08), Scott Long said: > For iSCSI, this obviously won't work. CAM has no concept of iSCSI > addresses, and even if it did, doing a linear scan of even a small > subnet would be prohibitively expensive. What is really needed is a > new XPT layer that understands iSCSI. By this, I mean a layer that > understands how to properly scan and detect targets, how to log into > them, etc. It should also have a certain amount of flexibility so > that hardware-assisted solutions can plug in and pick-and-choose the > pieces they need from the transport layer. > > Lucent did an iSCSI initiator for FreeBSD 4.x a while back and I > think they got around all of this by telling CAM not to auto-scan at > boot, followed by having the driver announce devices to CAM directly > (look at the ATAPI-CAM code for an example of how to do this) and do > all the detection and login work behind CAM's back. This really > should only be considered a hack though. If you're interested, I > might be able to dig up the link to it. We never pursued integrating > it to the FreeBSD tree because of very restrictive licensing terms on > it. The fibre-channel drivers (isp,mpt) must have been the first to have hit this problem; do they do the same thing as atapicam? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 22:10:13 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB3E016A4D0 for ; Tue, 8 Feb 2005 22:10:13 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 700A943D41 for ; Tue, 8 Feb 2005 22:10:13 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j18MAU8i005668; Tue, 8 Feb 2005 15:10:31 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <420938BC.6050800@freebsd.org> Date: Tue, 08 Feb 2005 15:10:04 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <4208F618.3000400@freebsd.org> <20050208214956.GA3104@dan.emsphone.com> In-Reply-To: <20050208214956.GA3104@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 22:10:14 -0000 Dan Nelson wrote: > In the last episode (Feb 08), Scott Long said: > >>For iSCSI, this obviously won't work. CAM has no concept of iSCSI >>addresses, and even if it did, doing a linear scan of even a small >>subnet would be prohibitively expensive. What is really needed is a >>new XPT layer that understands iSCSI. By this, I mean a layer that >>understands how to properly scan and detect targets, how to log into >>them, etc. It should also have a certain amount of flexibility so >>that hardware-assisted solutions can plug in and pick-and-choose the >>pieces they need from the transport layer. >> >>Lucent did an iSCSI initiator for FreeBSD 4.x a while back and I >>think they got around all of this by telling CAM not to auto-scan at >>boot, followed by having the driver announce devices to CAM directly >>(look at the ATAPI-CAM code for an example of how to do this) and do >>all the detection and login work behind CAM's back. This really >>should only be considered a hack though. If you're interested, I >>might be able to dig up the link to it. We never pursued integrating >>it to the FreeBSD tree because of very restrictive licensing terms on >>it. > > > The fibre-channel drivers (isp,mpt) must have been the first to have > hit this problem; do they do the same thing as atapicam? > Well, FC support in CAM is really limited to only simple arbitrated loops. Unless the driver and/or firmware gets involved and massages CAM's view of things, trying to do active-active loops and fabrics just isn't possible. Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 22:15:20 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9134616A4CE; Tue, 8 Feb 2005 22:15:20 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6561043D2F; Tue, 8 Feb 2005 22:15:20 +0000 (GMT) (envelope-from chuck_tuffli@agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 7A3C31FC9; Tue, 8 Feb 2005 15:15:17 -0700 (MST) Received: from wlvdvs01.lvld.agilent.com (wlvdvs01.lvld.agilent.com [148.5.6.4]) by relcos2.cos.agilent.com (Postfix) with ESMTP id BABA225F; Tue, 8 Feb 2005 15:15:19 -0700 (MST) Received: from rtl.rose.agilent.com ([130.30.179.189]) by wlvdvs01.lvld.agilent.com with InterScan Messaging Security Suite; Tue, 08 Feb 2005 15:15:18 -0700 Received: from [141.184.129.212] (cos1nai129212.cos.agilent.com [141.184.129.212])ESMTP id OAA22956; Tue, 8 Feb 2005 14:15:15 -0800 (PST) Received: from 127.0.0.1 (AVG SMTP 7.0.300 [265.8.6]); Tue, 08 Feb 2005 14:15:47 -0800 Message-ID: <42093A11.9040403@agilent.com> Date: Tue, 08 Feb 2005 14:15:45 -0800 From: Chuck Tuffli User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <4208F618.3000400@freebsd.org> <20050208214956.GA3104@dan.emsphone.com> In-Reply-To: <20050208214956.GA3104@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Scott Long Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 22:15:20 -0000 Dan Nelson wrote: ... > The fibre-channel drivers (isp,mpt) must have been the first to have > hit this problem; do they do the same thing as atapicam? If memory serves, the FC drivers take the results from loop/fabric discovery and then map each discovered device to a target_id. During boot, the driver stalls/sleeps waiting for discovery to complete before completing to the CAM. Later on if the loop/fabric changes, the user would need to force a re-scan to pick up the new devices. -- Chuck Tuffli Agilent Technologies From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 22:26:13 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F246E16A4CF for ; Tue, 8 Feb 2005 22:26:12 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8672743D1F for ; Tue, 8 Feb 2005 22:26:12 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j18MQSW1005756; Tue, 8 Feb 2005 15:26:28 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <42093C7A.3000704@freebsd.org> Date: Tue, 08 Feb 2005 15:26:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Tuffli References: <4208F618.3000400@freebsd.org> <20050208214956.GA3104@dan.emsphone.com> <42093A11.9040403@agilent.com> In-Reply-To: <42093A11.9040403@agilent.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-scsi@freebsd.org cc: Dan Nelson Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 22:26:13 -0000 Chuck Tuffli wrote: > Dan Nelson wrote: > ... > >> The fibre-channel drivers (isp,mpt) must have been the first to have >> hit this problem; do they do the same thing as atapicam? > > > If memory serves, the FC drivers take the results from loop/fabric > discovery and then map each discovered device to a target_id. During > boot, the driver stalls/sleeps waiting for discovery to complete before > completing to the CAM. Later on if the loop/fabric changes, the user > would need to force a re-scan to pick up the new devices. > That sounds about right. I couldn't remember exactly what the exsting drivers handle, so i was just playing it safe. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 10 02:45:54 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08BBC16A4CE for ; Thu, 10 Feb 2005 02:45:54 +0000 (GMT) Received: from dark.sinister.com (sinister.com [205.159.169.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 455B143D3F for ; Thu, 10 Feb 2005 02:45:53 +0000 (GMT) (envelope-from rkeyes@xa.net) Received: (qmail 16785 invoked by uid 1076); 10 Feb 2005 03:38:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 10 Feb 2005 03:38:29 -0000 Date: Wed, 9 Feb 2005 22:38:29 -0500 (EST) From: Robert keyes X-X-Sender: rkeyes@dark.sinister.com Cc: freebsd-scsi@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: MegaRaid 2m Giant Locked-up X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2005 02:45:54 -0000 This turned out to be a problem with my hardware, not a FreeBSD problem. Sorry to stir up trouble. The details: For some reason the system does not find the BIOS of the build-in SCSI controller, nor the Adaptec AHA-2940UW that I put in. I don't know why. I don't really feel like booting from floppy or IDE CD is going to be reliable, so I am going to try to replace the motherboard. Does anyone know where to find the ASUS TR-DLSR that it uses?