From owner-freebsd-scsi Sun Nov 17 21:22:52 2002 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 07F5E37B401 for ; Sun, 17 Nov 2002 21:22:52 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1944443E88 for ; Sun, 17 Nov 2002 21:22:50 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id B74591D08 for ; Sun, 17 Nov 2002 22:22:39 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 3D5EA15 for ; Sun, 17 Nov 2002 22:22:39 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id VAA11832 for ; Sun, 17 Nov 2002 21:22:38 -0800 (PST) Received: from thegrail (anu.rose.agilent.com [156.140.225.186]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAAE02 for ; Sun, 17 Nov 2002 21:22:35 -0800 Received: by thegrail (Postfix, from userid 1001) id 2FC678470A; Sun, 17 Nov 2002 21:18:32 -0800 (PST) Date: Sun, 17 Nov 2002 21:18:32 -0800 From: Chuck Tuffli To: freebsd-scsi@freebsd.org Subject: SIM as loadable module? Message-ID: <20021118051831.GA1083@thegrail.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm writting a SIM driver as a loadable module and am running into a strange problem. I register with the CAM and receive a XPT_PATH_INQ, but don't receive any other commands. This is on FreeBSD 4.7-RELEASE. The only things the driver sets out of the (maybe) ordinary are cpi->hba_misc = PIM_NOBUSRESET; /* no reset for Fibre Channel */ cpi->hba_inquiry = PI_TAG_ABLE; Does any of this ring a bell? Thanks! -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 17 22:31:19 2002 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 105A737B401 for ; Sun, 17 Nov 2002 22:31:19 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAFEA43E4A for ; Sun, 17 Nov 2002 22:31:18 -0800 (PST) (envelope-from Scott_Long@adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gAI6VIj23774; Sun, 17 Nov 2002 22:31:18 -0800 (PST) Received: from OTCEXC01.otc.adaptec.com (otcexc01.otc.adaptec.com [10.12.1.27]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id WAA29453; Sun, 17 Nov 2002 22:31:17 -0800 (PST) Received: by otcexc01.otc.adaptec.com with Internet Mail Service (5.5.2653.19) id <4TQCXW6F>; Mon, 18 Nov 2002 01:31:15 -0500 Message-ID: <6100BCEB85F8E244959C756C04E0EDD161CB79@otcexc01.otc.adaptec.com> From: "Long, Scott" To: "'Chuck Tuffli'" , freebsd-scsi@FreeBSD.ORG Subject: RE: SIM as loadable module? Date: Mon, 18 Nov 2002 01:31:14 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > I'm writting a SIM driver as a loadable module and am running into a > strange problem. I register with the CAM and receive a XPT_PATH_INQ, > but don't receive any other commands. This is on FreeBSD 4.7-RELEASE. > The only things the driver sets out of the (maybe) ordinary are > > cpi->hba_misc = PIM_NOBUSRESET; /* no reset for Fibre Channel */ > cpi->hba_inquiry = PI_TAG_ABLE; > > Does any of this ring a bell? Thanks! > What are you setting ccb->ccb_h.status to? Can you share the body of your action method, or at least the XPT_PATH_INQ portions? Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 17 22:52:34 2002 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 9992737B431 for ; Sun, 17 Nov 2002 22:52:32 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A8A943ED8 for ; Sun, 17 Nov 2002 22:52:13 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id C0BCA8A4B for ; Sun, 17 Nov 2002 23:52:12 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 43C7656E for ; Sun, 17 Nov 2002 23:52:12 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id WAA12048 for ; Sun, 17 Nov 2002 22:52:11 -0800 (PST) Received: from thegrail (anu.rose.agilent.com [156.140.225.186]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA1764; Sun, 17 Nov 2002 22:52:07 -0800 Received: by thegrail (Postfix, from userid 1001) id 37E638470F; Sun, 17 Nov 2002 22:48:07 -0800 (PST) Date: Sun, 17 Nov 2002 22:48:06 -0800 From: Chuck Tuffli To: "Long, Scott" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021118064805.GA7533@thegrail.rose.agilent.com> References: <6100BCEB85F8E244959C756C04E0EDD161CB79@otcexc01.otc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6100BCEB85F8E244959C756C04E0EDD161CB79@otcexc01.otc.adaptec.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 18, 2002 at 01:31:14AM -0500, Long, Scott wrote: > > What are you setting ccb->ccb_h.status to? Can you share the body of > your action method, or at least the XPT_PATH_INQ portions? case XPT_PATH_INQ: { /* get properties of the SIM driver and HBA */ struct ccb_pathinq *cpi = &ccb->cpi; hpFCPortInfo_t fpi; cpi->version_num = 1; /* all drivers use version 1 */ cpi->target_sprt = 0; /* initiator only */ cpi->hba_eng_cnt = 0; cpi->bus_id = bus; cpi->max_target = TACH_MAX_DISKS - 1; cpi->max_lun = TACH_MAX_LUN - 1; cpi->hba_misc = PIM_NOBUSRESET; cpi->hba_inquiry = PI_TAG_ABLE; cpi->initiator_id = cpi->max_target + 1; fcPortGetInfo(&(ini->tach->root), &fpi); if (fpi.PortSpeed == 0) { cpi->base_transfer_speed = 100000; } else { cpi->base_transfer_speed = 200000; } strncpy(cpi->sim_vid, "FreeBSD", SIM_IDLEN); strncpy(cpi->hba_vid, "Agilent", HBA_IDLEN); strncpy(cpi->dev_name, cam_sim_name(sim), DEV_IDLEN); cpi->unit_number = unit; cpi->ccb_h.status = CAM_REQ_CMP; xpt_done(ccb); break; } -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 11: 1: 8 2002 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 CFF5537B401 for ; Mon, 18 Nov 2002 11:01:07 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC4043F5F for ; Mon, 18 Nov 2002 11:00:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gAIJ0fx3078408 for ; Mon, 18 Nov 2002 11:00:41 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gAIJ0fnm078406 for scsi@freebsd.org; Mon, 18 Nov 2002 11:00:41 -0800 (PST) Date: Mon, 18 Nov 2002 11:00:41 -0800 (PST) Message-Id: <200211181900.gAIJ0fnm078406@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 11: 5: 7 2002 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 A0A7037B401 for ; Mon, 18 Nov 2002 11:05:05 -0800 (PST) Received: from c0mailgw03.prontomail.com (mailgw.prontomail.com [209.185.149.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2489B43E4A for ; Mon, 18 Nov 2002 11:05:05 -0800 (PST) (envelope-from xxxlucasxxx@canoemail.com) Received: from c0web112 (209.185.149.10) by c0mailgw03.prontomail.com (NPlex 6.0.045) id 3DD932A000000F06 for freebsd-scsi@freebsd.org; Mon, 18 Nov 2002 11:05:37 -0800 X-Version: canoe 6.2.2329.0 From: xxxlucasxxx@canoemail.com Message-Id: <594B1F70C5F7D8947BB58F869F32E33A@xxxlucasxxx.canoemail.com> Date: Mon, 18 Nov 2002 14:04:54 -0500 X-Priority: Normal Content-Type: text/plain; charset=iso-8859-1 To: freebsd-scsi@freebsd.org Subject: Initializing SCSI drive ST15150W X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am having a problem getting two seagate (compaq) ST15150W drives initialized at boot. dmesg gives me the bellow message for the SCSI card and drive (I am trying one at a time not to confuse matters). In this case I have set the drive as bootable in the SCSI BIOS. I have also tried it as not bootable. I have tried another drive that has the device ID 0, in this case it is device 2. All attemps have lead to nothing more then the below. With the device set as not bootable the "SCAN AT BOOT" message includes the target 2. The drive and card do work, I have tested them on a W2K system without any problems other then being on a W2K system. Any clues, a good schooling and taunts are welcome. -------------------- . . . sym0: <875> port 0xe000-0xe0ff mem 0xe5001000-0xe5001fff,0xe5000000-0xe50000ff irq 11 at device 13.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: SCAN AT BOOT disabled for targets 0 1 3 4 5 6 8 9 10 11 12 13 14 15. . . . Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (probe2:sym0:0:2:0): extraneous data discarded. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 1). (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). -------------------- Thanks in advance for any help. Lucas Sign up today for your Free E-mail at: http://www.canoe.ca/CanoeMail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 11: 9: 6 2002 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 9319537B404 for ; Mon, 18 Nov 2002 11:09:05 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0261F43E42 for ; Mon, 18 Nov 2002 11:09:05 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gAIJ94x3087237 for ; Mon, 18 Nov 2002 11:09:04 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gAIJ94HV087231 for scsi@freebsd.org; Mon, 18 Nov 2002 11:09:04 -0800 (PST) Date: Mon, 18 Nov 2002 11:09:04 -0800 (PST) Message-Id: <200211181909.gAIJ94HV087231@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2002/02/18] kern/35082 scsi IBM Intellistation will not reboot with S 1 problem total. Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 20:47:18 2002 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 2A47C37B401; Mon, 18 Nov 2002 20:47:17 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD78D43E97; Mon, 18 Nov 2002 20:47:16 -0800 (PST) (envelope-from Scott_Long@adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gAJ4lGj05768; Mon, 18 Nov 2002 20:47:16 -0800 (PST) Received: from OTCEXC01.otc.adaptec.com (otcexc01.otc.adaptec.com [10.12.1.27]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id UAA24639; Mon, 18 Nov 2002 20:47:15 -0800 (PST) Received: by otcexc01.otc.adaptec.com with Internet Mail Service (5.5.2653.19) id <4TQCXXTH>; Mon, 18 Nov 2002 23:47:14 -0500 Message-ID: <6100BCEB85F8E244959C756C04E0EDD161CB7F@otcexc01.otc.adaptec.com> From: "Long, Scott" To: "'Chuck Tuffli'" , "Long, Scott" Cc: freebsd-scsi@FreeBSD.ORG, "'ken@freebsd.org'" Subject: RE: SIM as loadable module? Date: Mon, 18 Nov 2002 23:47:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > On Mon, Nov 18, 2002 at 01:31:14AM -0500, Long, Scott wrote: > > > > What are you setting ccb->ccb_h.status to? Can you share > the body of > > your action method, or at least the XPT_PATH_INQ portions? > > case XPT_PATH_INQ: > { > /* get properties of the SIM driver and HBA */ > struct ccb_pathinq *cpi = &ccb->cpi; > hpFCPortInfo_t fpi; > > cpi->version_num = 1; /* all drivers use version 1 */ > cpi->target_sprt = 0; /* initiator only */ > cpi->hba_eng_cnt = 0; > cpi->bus_id = bus; > cpi->max_target = TACH_MAX_DISKS - 1; > cpi->max_lun = TACH_MAX_LUN - 1; > cpi->hba_misc = PIM_NOBUSRESET; > cpi->hba_inquiry = PI_TAG_ABLE; > > cpi->initiator_id = cpi->max_target + 1; > > fcPortGetInfo(&(ini->tach->root), &fpi); > if (fpi.PortSpeed == 0) { > cpi->base_transfer_speed = 100000; > } else { > cpi->base_transfer_speed = 200000; > } > strncpy(cpi->sim_vid, "FreeBSD", SIM_IDLEN); > strncpy(cpi->hba_vid, "Agilent", HBA_IDLEN); > strncpy(cpi->dev_name, cam_sim_name(sim), DEV_IDLEN); > cpi->unit_number = unit; > cpi->ccb_h.status = CAM_REQ_CMP; > xpt_done(ccb); > break; > } > Nothing in here is jumping out at me as being wrong, sssuming that ccb->ccb_h.status isn't being changed before you return. Try emailing Ken Merry (ken@freebsd.org) directly to see what he thinks. I'm impressed that Agilent is doing a FreeBSD driver for the Tachyon. Will it be fully open source or half open/half closed? Also, will it do fabrics or just AL? Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 21:16:27 2002 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 AA51337B401 for ; Mon, 18 Nov 2002 21:16:25 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE19943E42 for ; Mon, 18 Nov 2002 21:16:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id gAJ5G6KD036804; Mon, 18 Nov 2002 22:16:06 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id gAJ5G6G0036803; Mon, 18 Nov 2002 22:16:06 -0700 (MST) (envelope-from ken) Date: Mon, 18 Nov 2002 22:16:06 -0700 From: "Kenneth D. Merry" To: "Long, Scott" Cc: "'Chuck Tuffli'" , freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021118221606.A36763@panzer.kdm.org> References: <6100BCEB85F8E244959C756C04E0EDD161CB7F@otcexc01.otc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <6100BCEB85F8E244959C756C04E0EDD161CB7F@otcexc01.otc.adaptec.com>; from Scott_Long@adaptec.com on Mon, Nov 18, 2002 at 11:47:13PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 18, 2002 at 23:47:13 -0500, Long, Scott wrote: > > On Mon, Nov 18, 2002 at 01:31:14AM -0500, Long, Scott wrote: > > > > > > What are you setting ccb->ccb_h.status to? Can you share > > the body of > > > your action method, or at least the XPT_PATH_INQ portions? > > > > case XPT_PATH_INQ: > > { > > /* get properties of the SIM driver and HBA */ > > struct ccb_pathinq *cpi = &ccb->cpi; > > hpFCPortInfo_t fpi; > > > > cpi->version_num = 1; /* all drivers use version 1 */ > > cpi->target_sprt = 0; /* initiator only */ > > cpi->hba_eng_cnt = 0; > > cpi->bus_id = bus; > > cpi->max_target = TACH_MAX_DISKS - 1; > > cpi->max_lun = TACH_MAX_LUN - 1; > > cpi->hba_misc = PIM_NOBUSRESET; > > cpi->hba_inquiry = PI_TAG_ABLE; > > > > cpi->initiator_id = cpi->max_target + 1; > > > > fcPortGetInfo(&(ini->tach->root), &fpi); > > if (fpi.PortSpeed == 0) { > > cpi->base_transfer_speed = 100000; > > } else { > > cpi->base_transfer_speed = 200000; > > } > > strncpy(cpi->sim_vid, "FreeBSD", SIM_IDLEN); > > strncpy(cpi->hba_vid, "Agilent", HBA_IDLEN); > > strncpy(cpi->dev_name, cam_sim_name(sim), DEV_IDLEN); > > cpi->unit_number = unit; > > cpi->ccb_h.status = CAM_REQ_CMP; > > xpt_done(ccb); > > break; > > } > > > > Nothing in here is jumping out at me as being wrong, sssuming that > ccb->ccb_h.status isn't being changed before you return. Try > emailing Ken Merry (ken@freebsd.org) directly to see what he thinks. One question is whether the card gets probed when you statically compile the driver into the kernel. Another is, what happens when you rescan that bus? (camcontrol devlist -v should show which SCSI bus is allocated to your driver.) A path inquiry gets sent out when you register the bus (xpt_bus_register()), so that's probably what you're seeing. > I'm impressed that Agilent is doing a FreeBSD driver for the Tachyon. > Will it be fully open source or half open/half closed? Also, will it > do fabrics or just AL? Yep, it'll be nice to have a Tachyon driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 18 23:10:15 2002 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 3859037B401 for ; Mon, 18 Nov 2002 23:10:14 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BED443E6E for ; Mon, 18 Nov 2002 23:10:12 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id IAA25307; Tue, 19 Nov 2002 08:10:02 +0100 (CET) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.5/8.12.5) with ESMTP id gAJ71OWc007180; Tue, 19 Nov 2002 08:01:24 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.5/8.12.5/Submit) id gAJ71Nns007179; Tue, 19 Nov 2002 08:01:23 +0100 (MET) (envelope-from j) Date: Tue, 19 Nov 2002 08:01:23 +0100 (MET) Message-Id: <200211190701.gAJ71Nns007179@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <594B1F70C5F7D8947BB58F869F32E33A@xxxlucasxxx.canoemail.com> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Initializing SCSI drive ST15150W X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: xxxlucasxxx@canoemail.com Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org xxxlucasxxx@canoemail.com wrote: > Waiting 15 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (probe2:sym0:0:2:0): extraneous data discarded. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 1). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. ISTR that you can patch the sym driver to not complain about this. However, last time we've been discussing it, it turned out that this is usually an indication of a firmware bug in the drive. Is it possible for you to upgrade the drive firmware? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 19 8:45: 1 2002 Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8677937B401; Tue, 19 Nov 2002 08:45:00 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 356AF43E77; Tue, 19 Nov 2002 08:45:00 -0800 (PST) (envelope-from scottl@FreeBSD.org) Received: from freefall.freebsd.org (scottl@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gAJGj0x3022464; Tue, 19 Nov 2002 08:45:00 -0800 (PST) (envelope-from scottl@freefall.freebsd.org) Received: (from scottl@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gAJGiwY4022460; Tue, 19 Nov 2002 08:44:58 -0800 (PST) Date: Tue, 19 Nov 2002 08:44:58 -0800 (PST) From: Scott Long Message-Id: <200211191644.gAJGiwY4022460@freefall.freebsd.org> To: cst@nty.ch, scottl@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: misc/32194: Adaptec SCSI RAID 2100 fails by reboot Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Adaptec SCSI RAID 2100 fails by reboot State-Changed-From-To: feedback->closed State-Changed-By: scottl State-Changed-When: Tue Nov 19 08:41:52 PST 2002 State-Changed-Why: This does not appear to be a driver problem. Adaptec Tech Support can provide support for this as they do support FreeBSD. Please contact them via their toll free support number. http://www.freebsd.org/cgi/query-pr.cgi?pr=32194 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 19 9:41:17 2002 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 65EFE37B401 for ; Tue, 19 Nov 2002 09:41:16 -0800 (PST) Received: from siralan.org (12-222-67-235.client.insightBB.com [12.222.67.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F8B143E6E for ; Tue, 19 Nov 2002 09:41:15 -0800 (PST) (envelope-from mikes@siralan.org) Received: from siralan.org (localhost [127.0.0.1]) by siralan.org (8.12.6/8.12.6) with ESMTP id gAJHf9lE009011 for ; Tue, 19 Nov 2002 12:41:09 -0500 (EST) (envelope-from mikes@siralan.org) Received: (from mikes@localhost) by siralan.org (8.12.6/8.12.6/Submit) id gAJHf86Y009010 for freebsd-scsi@freebsd.org; Tue, 19 Nov 2002 12:41:08 -0500 (EST) From: "Michael L. Squires" Message-Id: <200211191741.gAJHf86Y009010@siralan.org> Subject: Re: Initializing SCSI drive ST15150W In-Reply-To: <200211190701.gAJ71Nns007179@uriah.heep.sax.de> "from Joerg Wunsch at Nov 19, 2002 08:01:23 am" To: FreeBSD SCSI Date: Tue, 19 Nov 2002 12:41:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > ISTR that you can patch the sym driver to not complain about > this. However, last time we've been discussing it, it turned > out that this is usually an indication of a firmware bug in the > drive. Is it possible for you to upgrade the drive firmware? Seagate does not usually allow end-users to update firmware. SCSITOOL can update firmware and the author indicates that he does have some Seagate firmware updates: http://www.nu2.nu/scsitool Mike Squires To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 19 11: 6: 9 2002 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 DE0A937B401 for ; Tue, 19 Nov 2002 11:06:08 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A13343E42 for ; Tue, 19 Nov 2002 11:06:04 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 61185 invoked by uid 1000); 19 Nov 2002 19:06:04 -0000 Date: Tue, 19 Nov 2002 11:06:04 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? In-Reply-To: <20021118064805.GA7533@thegrail.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 17 Nov 2002, Chuck Tuffli wrote: > case XPT_PATH_INQ: > { > ... > cpi->bus_id = bus; Shouldn't this be: cpi->bus_id = cam_sim_bus(sim); (of course, I don't know what the type of "bus" is in this context) > cpi->initiator_id = cpi->max_target + 1; Does this accurately reflect the card's settings? Some SIMs I've seen do a device-specific call to read the card's id (in your case, fcPortGetInfo?). I guess your approach should be necessary in the FC case since your position in the chain can change when you get a LIP. The rest looks fine. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 2:29:51 2002 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 6EF5237B401 for ; Wed, 20 Nov 2002 02:29:50 -0800 (PST) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B626043E6E for ; Wed, 20 Nov 2002 02:29:48 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id gAKATfg28184; Wed, 20 Nov 2002 11:29:41 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id gAKATeU03083; Wed, 20 Nov 2002 11:29:41 +0100 (MET) Received: (from localhost) by curry.mchp.siemens.de (8.12.6/8.12.6) id gAKATeWt067854; Date: Wed, 20 Nov 2002 11:29:40 +0100 From: Andre Albsmeier To: "Michael L. Squires" Cc: FreeBSD SCSI Subject: Re: Initializing SCSI drive ST15150W Message-ID: <20021120112940.A68686@curry.mchp.siemens.de> References: <200211190701.gAJ71Nns007179@uriah.heep.sax.de> <200211191741.gAJHf86Y009010@siralan.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200211191741.gAJHf86Y009010@siralan.org>; from mikes@siralan.org on Tue, Nov 19, 2002 at 12:41:08PM -0500 X-Echelon: jihad, 707, detonator, KLM, Osama Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 19-Nov-2002 at 12:41:08 -0500, Michael L. Squires wrote: > > ISTR that you can patch the sym driver to not complain about > > this. However, last time we've been discussing it, it turned > > out that this is usually an indication of a firmware bug in the > > drive. Is it possible for you to upgrade the drive firmware? > > Seagate does not usually allow end-users to update firmware. Hmm, I have received several firmware images from Seagate already. I have been in contact with them using the company email address as well as with my private address. In both cases, they were very helpful and responded very quickly. BTW, I have two firmware images for the ST15150N (!W). The first one brings it two something like V 1.24. The second one takes it to V 2.23. I have not been able to beam my old V 1.xx directly to 2.23; I had to install the 1.24 first. > SCSITOOL can update firmware and the author indicates that he > does have some Seagate firmware updates: I have written a small tool for FreeBSD which does this for SCSI devices. Yes, I updated my ST15150N with it years ago. In case s.o. is interested drop me a note. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 6: 0:23 2002 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 4D40C37B401 for ; Wed, 20 Nov 2002 06:00:22 -0800 (PST) Received: from c0mailgw04.prontomail.com (mailgw.prontomail.com [209.185.149.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CEA943E42 for ; Wed, 20 Nov 2002 06:00:22 -0800 (PST) (envelope-from xxxlucasxxx@canoemail.com) Received: from c0web111 (209.185.149.10) by c0mailgw04.prontomail.com (NPlex 6.0.045) id 3DDB91E70000054C; Wed, 20 Nov 2002 06:01:03 -0800 X-Version: canoe 6.2.2329.0 From: "Lucas" Message-Id: <86DBB58B94E51AB4B949DFDE68EE2952@xxxlucasxxx.canoemail.com> Date: Wed, 20 Nov 2002 09:00:19 -0500 X-Priority: Normal Content-Type: text/plain; charset=iso-8859-1 To: freebsd-scsi@freebsd.org Subject: Re: Initializing SCSI drive ST15150W Cc: joerg_wunsch@uriah.heep.sax.de X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Just to note. I have figured out the problem. The SCSI controller I am using is an ASUS SC875 (which if I put in the post probably would have helped some). The sym driver recognizes it, but really isn't able to play with the devices attached to it. I tried the ncr driver which recognizes the controller and the hd attached to it. As noted the sym driver will require some patch for the drive to play with the hd which currently is a bit beyond my abilities (and time). Lucas ---- Begin Original Message ---- From: j@uriah.heep.sax.de (Joerg Wunsch) Sent: Tue, 19 Nov 2002 08:01:23 +0100 (MET) To: freebsd-scsi@freebsd.org CC: xxxlucasxxx@canoemail.com Subject: Re: Initializing SCSI drive ST15150W xxxlucasxxx@canoemail.com wrote: > Waiting 15 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (probe2:sym0:0:2:0): extraneous data discarded. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 1). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. ISTR that you can patch the sym driver to not complain about this. However, last time we've been discussing it, it turned out that this is usually an indication of a firmware bug in the drive. Is it possible for you to upgrade the drive firmware? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ---- End Original Message ---- Sign up today for your Free E-mail at: http://www.canoe.ca/CanoeMail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 11:53:37 2002 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 392A937B401 for ; Wed, 20 Nov 2002 11:53:36 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93FA143E4A for ; Wed, 20 Nov 2002 11:53:35 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 2A3592309 for ; Wed, 20 Nov 2002 12:53:21 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 759225A2 for ; Wed, 20 Nov 2002 12:53:07 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id LAA07847 for ; Wed, 20 Nov 2002 11:53:00 -0800 (PST) Received: from cre85086tuf (cre85086tuf.rose.agilent.com [130.30.178.1]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA4560; Wed, 20 Nov 2002 11:52:57 -0800 Received: by cre85086tuf (Postfix, from userid 1001) id 9194719DD64; Wed, 20 Nov 2002 11:52:26 -0800 (PST) Date: Wed, 20 Nov 2002 11:52:26 -0800 From: Chuck Tuffli To: "Kenneth D. Merry" Cc: "Long, Scott" , freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021120195226.GA35733@cre85086tuf.rose.agilent.com> References: <6100BCEB85F8E244959C756C04E0EDD161CB7F@otcexc01.otc.adaptec.com> <20021118221606.A36763@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021118221606.A36763@panzer.kdm.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Nov 18, 2002 at 10:16:06PM -0700, Kenneth D. Merry wrote: > On Mon, Nov 18, 2002 at 23:47:13 -0500, Long, Scott wrote: > > One question is whether the card gets probed when you statically compile > the driver into the kernel. I haven't tried this yet. Maybe the question I'm asking is does the CAM automatically scan new buses or is a scan initiated by camcontrol for loadable modules. > Another is, what happens when you rescan that bus? (camcontrol devlist -v > should show which SCSI bus is allocated to your driver.) smallrocks# camcontrol devlist -v scbus0 on tach0 bus 0: < > at scbus0 target -1 lun -1 () scbus1 on tach1 bus 0: < > at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) > A path inquiry gets sent out when you register the bus > (xpt_bus_register()), so that's probably what you're seeing. > > > I'm impressed that Agilent is doing a FreeBSD driver for the Tachyon. > > Will it be fully open source or half open/half closed? Also, will it > > do fabrics or just AL? > > Yep, it'll be nice to have a Tachyon driver. I'll see what I can do. Releasing a binary only driver is probably a no brainer. Half open/closed might be possible too if people were interested. All open could happen too, but it would be a separate effort from what I'm doing now. -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 12: 0:40 2002 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 23E1837B413 for ; Wed, 20 Nov 2002 12:00:39 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A66D43E3B for ; Wed, 20 Nov 2002 12:00:38 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 56BF8212D for ; Wed, 20 Nov 2002 13:00:36 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 54134546 for ; Wed, 20 Nov 2002 13:00:32 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id MAA08111 for ; Wed, 20 Nov 2002 12:00:30 -0800 (PST) Received: from cre85086tuf (cre85086tuf.rose.agilent.com [130.30.178.1]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA4628; Wed, 20 Nov 2002 12:00:27 -0800 Received: by cre85086tuf (Postfix, from userid 1001) id 28B7F19DD64; Wed, 20 Nov 2002 11:59:57 -0800 (PST) Date: Wed, 20 Nov 2002 11:59:57 -0800 From: Chuck Tuffli To: Nate Lawson Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021120195956.GB35733@cre85086tuf.rose.agilent.com> References: <20021118064805.GA7533@thegrail.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Nov 19, 2002 at 11:06:04AM -0800, Nate Lawson wrote: > On Sun, 17 Nov 2002, Chuck Tuffli wrote: > > case XPT_PATH_INQ: > > { > > ... > > cpi->bus_id = bus; > > Shouldn't this be: > cpi->bus_id = cam_sim_bus(sim); > (of course, I don't know what the type of "bus" is in this context) Earlier in the function: int bus = cam_sim_bus(sim); > > cpi->initiator_id = cpi->max_target + 1; > > Does this accurately reflect the card's settings? Some SIMs I've seen do > a device-specific call to read the card's id (in your case, For this, I was mimicing what the isp and mpt were doing although I wasn't 100% sure why there was a distinction. My guess was that by setting the HBA's ID higher than max_target, the CAM wouldn't send INQUIRY. > fcPortGetInfo?). I guess your approach should be necessary in the FC case > since your position in the chain can change when you get a LIP. Wouldn't the driver want to insulate the CAM from this kind of event? I was thinking that the CAM's view of TID should be independent from FC's view of NPort_ID. The intent would be that the WWN of TID x should be the same before and after a LIP, but the mapping of TID to NPort_ID may change. -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 13:16:58 2002 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 B1CD237B401 for ; Wed, 20 Nov 2002 13:16:57 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2FD9043E8A for ; Wed, 20 Nov 2002 13:16:57 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 65023 invoked by uid 1000); 20 Nov 2002 21:16:58 -0000 Date: Wed, 20 Nov 2002 13:16:58 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? In-Reply-To: <20021120195226.GA35733@cre85086tuf.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Nov 2002, Chuck Tuffli wrote: > On Mon, Nov 18, 2002 at 10:16:06PM -0700, Kenneth D. Merry wrote: > > On Mon, Nov 18, 2002 at 23:47:13 -0500, Long, Scott wrote: > > > > One question is whether the card gets probed when you statically compile > > the driver into the kernel. > > I haven't tried this yet. Maybe the question I'm asking is does the > CAM automatically scan new buses or is a scan initiated by camcontrol > for loadable modules. It gets scanned on boot. If you load a module, it does not start a rescan automatically although the periph drivers are notified by an async callback. > > Another is, what happens when you rescan that bus? (camcontrol devlist -v > > should show which SCSI bus is allocated to your driver.) > > smallrocks# camcontrol devlist -v > scbus0 on tach0 bus 0: > < > at scbus0 target -1 lun -1 () > scbus1 on tach1 bus 0: > < > at scbus1 target -1 lun -1 () > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) This looks like it's attaching but the target id is invalid. Can you show your tach_attach routine where you set up the SIM and then register? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 13:18:41 2002 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 AC57A37B404 for ; Wed, 20 Nov 2002 13:18:40 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E29E43E97 for ; Wed, 20 Nov 2002 13:18:40 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 65034 invoked by uid 1000); 20 Nov 2002 21:18:41 -0000 Date: Wed, 20 Nov 2002 13:18:41 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? In-Reply-To: <20021120195956.GB35733@cre85086tuf.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Nov 2002, Chuck Tuffli wrote: > On Tue, Nov 19, 2002 at 11:06:04AM -0800, Nate Lawson wrote: > > fcPortGetInfo?). I guess your approach should be necessary in the FC case > > since your position in the chain can change when you get a LIP. > > Wouldn't the driver want to insulate the CAM from this kind of event? > I was thinking that the CAM's view of TID should be independent from > FC's view of NPort_ID. The intent would be that the WWN of TID x > should be the same before and after a LIP, but the mapping of TID to > NPort_ID may change. You might want to check with Matt. IIRC, isp allows target order to change when a LIP occurs. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 13:42:45 2002 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 0905C37B401 for ; Wed, 20 Nov 2002 13:42:43 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41BA143E42 for ; Wed, 20 Nov 2002 13:42:42 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id CE1E72217 for ; Wed, 20 Nov 2002 14:42:36 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 766EA17 for ; Wed, 20 Nov 2002 14:42:34 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id NAA11223 for ; Wed, 20 Nov 2002 13:42:33 -0800 (PST) Received: from cre85086tuf (cre85086tuf.rose.agilent.com [130.30.178.1]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA516E; Wed, 20 Nov 2002 13:42:30 -0800 Received: by cre85086tuf (Postfix, from userid 1001) id 7F4E719DD64; Wed, 20 Nov 2002 13:41:59 -0800 (PST) Date: Wed, 20 Nov 2002 13:41:59 -0800 From: Chuck Tuffli To: Nate Lawson Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021120214159.GA36070@cre85086tuf.rose.agilent.com> References: <20021120195226.GA35733@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Nov 20, 2002 at 01:16:58PM -0800, Nate Lawson wrote: [snip] > > smallrocks# camcontrol devlist -v > > scbus0 on tach0 bus 0: > > < > at scbus0 target -1 lun -1 () > > scbus1 on tach1 bus 0: > > < > at scbus1 target -1 lun -1 () > > scbus-1 on xpt0 bus 0: > > < > at scbus-1 target -1 lun -1 (xpt0) > > This looks like it's attaching but the target id is invalid. Can you show > your tach_attach routine where you set up the SIM and then register? if (NULL == (devq = cam_simq_alloc(TACH_MAX_EXCHANGES))) { device_printf(tach->dev, "cam_simq_alloc failed\n"); goto tach_app_attach_fail; } if (NULL == (sim = cam_sim_alloc(tach_action, tach_poll, "tach", ini, device_get_unit(tach->dev), 1, TACH_MAX_EXCHANGES, devq))) { device_printf(tach->dev, "cam_sim_alloc failed\n"); goto tach_app_attach_fail; } ini->sim = sim; if (xpt_bus_register(sim, 0) != CAM_SUCCESS) { device_printf(tach->dev, "xpt_bus_register failed\n"); goto tach_app_attach_fail; } if (xpt_create_path(&path, NULL, cam_sim_path(sim), CAM_TARGET_WILDCARD, CAM_LUN_WILDCARD) != CAM_REQ_CMP) { device_printf(tach->dev, "xpt_create_path failed\n"); goto tach_app_attach_fail; } ini->path = path; device_printf(tach->dev, "attached to CAM\n"); return; The relevant dmesg stuff tach0: Agilent Tachyon Driver Version 3.1 tach0: port 0x1400-0x14ff,0x1800-0x18ff mem 0xf4140000-0xf417ffff,0xf4121400-0xf41215ff irq 10 at device 16.0 on pci0 tach0: osPortCB(osFCPortLinkDown) (noperiph:tach0:0:-1:-1): xpt_compile_path (noperiph:tach0:0:-1:-1): xpt_setup_ccb (noperiph:tach0:0:-1:-1): xpt_action (noperiph:tach0:0:-1:-1): xpt_done (noperiph:tach0:0:-1:-1): xpt_release_path (noperiph:tach0:0:-1:-1): xpt_compile_path tach0: attached to CAM tach1: port 0x2000-0x20ff,0x2400-0x24ff mem 0xf4100000-0xf411ffff,0xf4121800-0xf41219ff irq 5 at device 18.0 on pci0 tach1: osPortCB(osFCPortLinkDown) (noperiph:tach1:0:-1:-1): xpt_compile_path (noperiph:tach1:0:-1:-1): xpt_setup_ccb (noperiph:tach1:0:-1:-1): xpt_action (noperiph:tach1:0:-1:-1): xpt_done (noperiph:tach1:0:-1:-1): xpt_release_path (noperiph:tach1:0:-1:-1): xpt_compile_path tach1: attached to CAM -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 13:45:38 2002 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 E865937B401 for ; Wed, 20 Nov 2002 13:45:36 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685D443E3B for ; Wed, 20 Nov 2002 13:45:36 -0800 (PST) (envelope-from Scott_Long@adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gAKLjZj21862; Wed, 20 Nov 2002 13:45:35 -0800 (PST) Received: from OTCEXC01.otc.adaptec.com (otcexc01.otc.adaptec.com [10.12.1.27]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id NAA09523; Wed, 20 Nov 2002 13:45:34 -0800 (PST) Received: by otcexc01.otc.adaptec.com with Internet Mail Service (5.5.2653.19) id <4TQCXY5Y>; Wed, 20 Nov 2002 16:45:34 -0500 Message-ID: <6100BCEB85F8E244959C756C04E0EDD161CB94@otcexc01.otc.adaptec.com> From: "Long, Scott" To: "'Nate Lawson'" , Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: SIM as loadable module? Date: Wed, 20 Nov 2002 16:45:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok, I'm getting really confused. Chuck, is the problem that the bus doesn't get scanned at all, ever, or that it doesn't get scanned when loaded as a module? Have you tried doing a 'camcontrol rescan' on the bus after loading the module? See below... > > On Wed, 20 Nov 2002, Chuck Tuffli wrote: > > On Mon, Nov 18, 2002 at 10:16:06PM -0700, Kenneth D. Merry wrote: > > > On Mon, Nov 18, 2002 at 23:47:13 -0500, Long, Scott wrote: > > > > > > One question is whether the card gets probed when you > statically compile > > > the driver into the kernel. > > > > I haven't tried this yet. Maybe the question I'm asking is does the > > CAM automatically scan new buses or is a scan initiated by > camcontrol > > for loadable modules. > > It gets scanned on boot. If you load a module, it does not start a > rescan automatically although the periph drivers are notified > by an async > callback. > > > > Another is, what happens when you rescan that bus? > (camcontrol devlist -v > > > should show which SCSI bus is allocated to your driver.) > > > > smallrocks# camcontrol devlist -v > > scbus0 on tach0 bus 0: > > < > at scbus0 target -1 lun -1 () > > scbus1 on tach1 bus 0: > > < > at scbus1 target -1 lun -1 () > > scbus-1 on xpt0 bus 0: > > < > at scbus-1 target -1 lun > -1 (xpt0) > > This looks like it's attaching but the target id is invalid. > Can you show > your tach_attach routine where you set up the SIM and then register? This devlist output is correct. The target id for each bus is displayed as -1 on SCSI also. Now, this output only verifies that the SIM is being registered, not that your SIM action method is actually working. You can write a trivial bit of code to send a PATH_INQ to one of these busses and see if that is working. As for how to handle the target id assignment of the SIM's bus, I think that you're making it more complicated that it needs to be. CAM's bus scan algorithm is smart enough to not attempt to probe the target number that you've specified as belonging to the host. I'm not sure if setting it to cpi->max_target + 1 will confuse CAM or not, but I highly doubt it. The bus_id number is another thing that CAM doesn't really care about, so as long as you provide a number that the user/applications agree is logical, everything is fine. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 20 14:55:48 2002 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 7FA5537B401 for ; Wed, 20 Nov 2002 14:55:47 -0800 (PST) Received: from volcano.planet.it (volcano.planet.it [212.110.160.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97A2543E3B for ; Wed, 20 Nov 2002 14:55:46 -0800 (PST) (envelope-from olgeni@uli.it) Received: from olgeni.olgeni (ppp-191.dial6.ctonet.it [212.110.181.191]) by volcano.planet.it (Postfix) with ESMTP id 7600B11FD8A for ; Wed, 20 Nov 2002 23:55:30 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by olgeni.olgeni (8.12.6/8.12.6) with ESMTP id gAKMsuoh006654 for ; Wed, 20 Nov 2002 23:54:56 +0100 (CET) (envelope-from olgeni@uli.it) Date: Wed, 20 Nov 2002 23:54:55 +0100 (CET) From: Jimmy Olgeni X-X-Sender: olgeni@olgeni.olgeni To: freebsd-scsi@FreeBSD.org Subject: ciss&tape Message-ID: <20021120235302.P86231-100000@olgeni.olgeni> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! Does anybody know if there are any plans to add external SCSI support to the CISS driver? Right now I'm stuck with a redundant array of expensive doorstops :o) -- jimmy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 21 8:30:20 2002 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 0EC9937B401 for ; Thu, 21 Nov 2002 08:30:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33C4A43E3B for ; Thu, 21 Nov 2002 08:30:14 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id RAA01228 for freebsd-scsi@freebsd.org; Thu, 21 Nov 2002 17:30:02 +0100 (CET) Received: from uriah.heep.sax.de (localhost.heep.sax.de [127.0.0.1]) by uriah.heep.sax.de (8.12.5/8.12.5) with ESMTP id gALGNcWc077680 for ; Thu, 21 Nov 2002 17:23:38 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.12.5/8.12.5/Submit) id gALGNce4077679; Thu, 21 Nov 2002 17:23:38 +0100 (MET) (envelope-from j) Date: Thu, 21 Nov 2002 17:23:38 +0100 (MET) Message-Id: <200211211623.gALGNce4077679@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <86DBB58B94E51AB4B949DFDE68EE2952@xxxlucasxxx.canoemail.com> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Initializing SCSI drive ST15150W X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Lucas" wrote: > The sym driver recognizes it, but really isn't able to play with the > devices attached to it. I tried the ncr driver which recognizes the > controller and the hd attached to it. The ncr driver didn't check for this condition either. You could also hack the check out of the sym driver, but in the long run, it's certainly better to get bug-free firmware instead. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 21 9:47:51 2002 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 A288537B401 for ; Thu, 21 Nov 2002 09:47:50 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD29A43E97 for ; Thu, 21 Nov 2002 09:47:48 -0800 (PST) (envelope-from ctuffli@rose.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 7927AE1AA for ; Thu, 21 Nov 2002 10:47:43 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id BA2492F7 for ; Thu, 21 Nov 2002 10:47:42 -0700 (MST) Received: from mail.rose.agilent.com (mailsrv@bellhop [130.30.179.19]) by rtl.rose.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.1.0) with ESMTP id JAA13099 for ; Thu, 21 Nov 2002 09:47:41 -0800 (PST) Received: from thegrail (anu.rose.agilent.com [156.140.225.186]) by mail.rose.agilent.com (Netscape Messaging Server 3.6) with ESMTP id AAA5E6D; Thu, 21 Nov 2002 09:47:38 -0800 Received: by thegrail (Postfix, from userid 1001) id 77437848B8; Thu, 21 Nov 2002 09:43:34 -0800 (PST) Date: Thu, 21 Nov 2002 09:43:34 -0800 From: Chuck Tuffli To: "Long, Scott" Cc: "'Nate Lawson'" , freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? Message-ID: <20021121174327.GC8729@thegrail.rose.agilent.com> References: <6100BCEB85F8E244959C756C04E0EDD161CB94@otcexc01.otc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6100BCEB85F8E244959C756C04E0EDD161CB94@otcexc01.otc.adaptec.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks to everyone that helped. I statically compiled the code into the kernel and the bus does get scaned. "camcontrol rescan" also scans the bus when the driver is a loadable module. On one of those other free OSs, loading the driver automatically kicks off a bus scan. Not that automatically scanning the bus is better, it was just what I was expecting. On Wed, Nov 20, 2002 at 04:45:24PM -0500, Long, Scott wrote: > Ok, I'm getting really confused. Chuck, is the problem that the > bus doesn't get scanned at all, ever, or that it doesn't get scanned > when loaded as a module? Have you tried doing a 'camcontrol rescan' > on the bus after loading the module? [snip] > As for how to handle the target id assignment of the SIM's bus, I think > that you're making it more complicated that it needs to be. CAM's bus > scan algorithm is smart enough to not attempt to probe the target number > that you've specified as belonging to the host. I'm not sure if setting > it to cpi->max_target + 1 will confuse CAM or not, but I highly doubt it. > The bus_id number is another thing that CAM doesn't really care about, so > as long as you provide a number that the user/applications agree is > logical, everything is fine. Ok, this id good to know. -- Chuck Tuffli Agilent Technologies, Storage and Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 21 12:35: 0 2002 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 8C70637B401 for ; Thu, 21 Nov 2002 12:34:59 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E461543E8A for ; Thu, 21 Nov 2002 12:34:54 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 68432 invoked by uid 1000); 21 Nov 2002 20:34:55 -0000 Date: Thu, 21 Nov 2002 12:34:55 -0800 (PST) From: Nate Lawson To: Chuck Tuffli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SIM as loadable module? In-Reply-To: <20021121174327.GC8729@thegrail.rose.agilent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 21 Nov 2002, Chuck Tuffli wrote: > Thanks to everyone that helped. I statically compiled the code into > the kernel and the bus does get scaned. "camcontrol rescan" also scans > the bus when the driver is a loadable module. On one of those other > free OSs, loading the driver automatically kicks off a bus scan. Not > that automatically scanning the bus is better, it was just what I was > expecting. We're working on that. :) -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 22 10:28:50 2002 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 B25FB37B401 for ; Fri, 22 Nov 2002 10:28:49 -0800 (PST) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4F3443E6E for ; Fri, 22 Nov 2002 10:28:48 -0800 (PST) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3/8.12.3) with ESMTP id gAMISl9K064469 for ; Fri, 22 Nov 2002 21:28:47 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3/8.12.3/Submit) id gAMISkRl064468 for freebsd-scsi@freebsd.org; Fri, 22 Nov 2002 21:28:46 +0300 (MSK) Date: Fri, 22 Nov 2002 21:28:46 +0300 From: Yar Tikhiy To: freebsd-scsi@freebsd.org Subject: {da,sa,...}open bug? Message-ID: <20021122212846.C60810@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi folks, While debugging the USB mass storage driver, which uses CAM, I ran into the following doubt. The XXopen() methods of the da, sa etc drivers get a reference to the peripheral ("periph") through cam_periph_acquire() and don't release it on error exit. I suspect this leads to CAM wedge if the device is removed when its driver is in XXopen(). That is because the "periph" stays acquired (refcount > 0), but the XXopen() caller wouldn't invoke XXclose() subsequently since it sees XXopen() having failed. Thus CAM won't ever "forget" the device removed. Moreover, after I had patched daopen() to release the peripheral if returning non-zero error code, the CAM wedge has gone. I'm new to CAM so I'd like to ask if my idea is correct. Thanks. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 22 11:14:48 2002 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 E64D737B404 for ; Fri, 22 Nov 2002 11:14:47 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E143A43E91 for ; Fri, 22 Nov 2002 11:14:46 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 71606 invoked by uid 1000); 22 Nov 2002 19:14:47 -0000 Date: Fri, 22 Nov 2002 11:14:47 -0800 (PST) From: Nate Lawson To: Yar Tikhiy Cc: freebsd-scsi@freebsd.org Subject: Re: {da,sa,...}open bug? In-Reply-To: <20021122212846.C60810@comp.chem.msu.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 22 Nov 2002, Yar Tikhiy wrote: > The XXopen() methods of the da, sa etc drivers get a reference to > the peripheral ("periph") through cam_periph_acquire() and don't > release it on error exit. I suspect this leads to CAM wedge if the > device is removed when its driver is in XXopen(). That is because > the "periph" stays acquired (refcount > 0), but the XXopen() caller > wouldn't invoke XXclose() subsequently since it sees XXopen() having > failed. Thus CAM won't ever "forget" the device removed. > > Moreover, after I had patched daopen() to release the peripheral > if returning non-zero error code, the CAM wedge has gone. Your approach sounds correct to me. open should call cam_periph_release if it errors out after cam_periph_acquire. Care to submit a patch? -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 22 21:52:30 2002 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 A7CF237B401; Fri, 22 Nov 2002 21:52:27 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id C838C43EB2; Fri, 22 Nov 2002 21:52:26 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id gAN5qQKD065886; Fri, 22 Nov 2002 22:52:26 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id gAN5qQ7D065885; Fri, 22 Nov 2002 22:52:26 -0700 (MST) (envelope-from ken) Date: Fri, 22 Nov 2002 22:52:26 -0700 From: "Kenneth D. Merry" To: scsi@FreeBSD.org Cc: stable@FreeBSD.org Subject: call for testers: cd(4) mode sense/mode select patches Message-ID: <20021122225225.A65816@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Here are patches against -current and -stable to add automatic detection of CDROM drives that can't handle 6 byte mode sense and mode select: http://people.FreeBSD.org/~ken/scsi_cd.cmdsize.20021122 http://people.FreeBSD.org/~ken/scsi_cd.cmdsize.stable.20021122 These new patches fix a data corruption bug in the last set that would likely cause a panic. These patches also change the way the da(4) driver handles the no_6_byte sysctl. There is now a per-drive sysctl to set the minimum command size for that particular disk. (Since you could have multiple disks with multiple requirements in one system.) I have also added loader tunable support for all the sysctls in the da(4) and cd(4) drivers. Finally, I've disabled MODE_SENSE and MODE_SELECT translation in ATAPICAM in both -current and -stable, and in the umass(4) driver in -current, since there's no way for that to work properly (see below). (Translation hasn't been MFCed for umass(4) yet, thus the reason I didn't change it in -stable.) I'd appreciate it if folks could test this, especially people with CDROM drives running via usb, firewire, or ATAPICAM, but also people with older SCSI CDROM drives. To test this, apply the patch (for -current or -stable as appropriate) and do the following: cdcontrol status cdcontrol info cdcontrol play (make sure audio comes out) cdcontrol next (make sure it skips to the next track here) If you get an error in response to 'cdcontrol next', definitely let me know what kind of drive you have (dmesg is fine) and how it is hooked up (SCSI, firewire, ATAPICAM, usb, etc.). The SCSI-2 PLAY_TRACK command has apparantly been deprecated in the MMC specs, so some drives don't support it. I'd like to get a handle on which ones do and don't, if possible. (The work around isn't hard, but isn't in this patch.) Reports of success or failure are welcome. ======= Now for more details.... When we get an illegal request in response to a 6 byte mode sense or mode select, we reformat the command to be a 10-byte mode sense or mode select and reissue it. These patches also work with drives that do not return block descriptors (even when dbd is 0 in the mode sense command), and drives that return multiple block descriptors. (They work better with the former than the latter; with the latter, they mostly just bail out.) While commands like READ(6) and WRITE(6) can be translated down in the SIM driver, like the ATAPICAM and usb code do, MODE_SENSE(6) and MODE_SELECT(6) cannot be translated, because the 10-byte version of the parameter list is longer. This means that when, e.g., a MODE_SENSE(6) command is translated to a MODE_SENSE(10) command, the page will likely be truncated (unless more space is allocated than needed), and since the peripheral driver code isn't expecting the returned data to be in MODE_SENSE(10) format, it'll be looking in the wrong place for the mode page. The SIM drivers have no way of knowing how long the buffer is that they've been given for a mode sense or mode select, so they can't just up the dxfer_len, change the CDB and call it good. The only way to do translation effectively for these two commands is where the buffer was originally allocated -- in the peripheral driver. So I have implemented translation and 10-byte mode sense and mode select for the cd(4) driver. Why do translation? Why not just default to 10-byte commands? Because some SCSI CDROM drives, maybe quite a few, don't support 10 byte mode sense and mode select. (The 8x Plextor in my test box doesn't, for example.) The right way to do this, eventually, is with the CAM_NEW_TRAN_CODE. 6byte/10byte can be a function of the protocol, and we can hopefully select the right size command up front. It will take a lot of infrastructure work to make it happen, but that functionality will hopefully solve several problems. Since translation won't work at the SIM level, I have disabled MODE_SENSE(6) and MODE_SELECT translation in ATAPICAM and umass(4). Comments are welcome on the patches; they're more complicated than I would like, but unfortunately that complication seems necessary to get the desired functionality. Many thanks to David Kleiner for testing multiple iterations of these patches, he has been a big help. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 23 14:35:18 2002 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 3B68437B401 for ; Sat, 23 Nov 2002 14:35:15 -0800 (PST) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B72E43E4A for ; Sat, 23 Nov 2002 14:35:14 -0800 (PST) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (212.129.39.30) by mail.libertysurf.net (6.5.026) id 3DCA8A7A004A63EE; Sat, 23 Nov 2002 23:35:07 +0100 Date: Sun, 24 Nov 2002 00:35:26 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: xxxlucasxxx@canoemail.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Initializing SCSI drive ST15150W In-Reply-To: <594B1F70C5F7D8947BB58F869F32E33A@xxxlucasxxx.canoemail.com> Message-ID: <20021124000049.D6113-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Here is the driver code that catches such errors: =09/* =09 * We have been ODD at the end of a DATA IN =09 * transfer and the device didn't send a =09 * IGNORE WIDE RESIDUE message. =09 * It is a data overrun condition. =09 */ =09case SIR_SWIDE_OVERRUN: =09=09if (cp) { =09=09=09OUTONB (HF_PRT, HF_EXT_ERR); =09=09=09cp->xerr_status |=3D XE_SWIDE_OVRUN; =09=09} =09=09goto out; The situation corresponds to the following conditions: - Device in WIDE 16 mode - Driver asked for a SCSI IO with an odd buffer size - The device can only send even sizes of bytes and sends 1 byte more than the buffer size which is odd. - The device doesn't tell that the additionnal byte was not valid data. (It can do so by sending a SCSI IGNORE WIDE RESIDUE message). You can make the sym driver ignore this error by just not compiling the 2 lines of code that sets the error condition, as follows: (/usr/src/sys/dev/sym/) --- sym_hipd.c.orig=09Thu Dec 27 22:25:25 2001 +++ sym_hipd.c=09Sat Nov 23 23:54:18 2002 @@ -6382,10 +6382,12 @@ =09 * It is a data overrun condition. =09 */ =09case SIR_SWIDE_OVERRUN: +#if 0 =09=09if (cp) { =09=09=09OUTONB (HF_PRT, HF_EXT_ERR); =09=09=09cp->xerr_status |=3D XE_SWIDE_OVRUN; =09=09} +#endif =09=09goto out; =09/* =09 * We have been ODD at the end of a DATA OUT ------------------ CUT HERE ------------------------- Btw, with this patch the additional byte will not be reported in the data residual, but if the device attempts to send more data, the driver will report a data overrun condition, but the ignored byte will still not be counted in the negative residual. Yes, this patch is not perfect, but your device firmware doesn't seem better to me. :-) But it can solve your problem. Doing odd sized IO with SCSI devices is probably a good way to trigger problems and CAM should avoid this. In fact, it only may do so when reading the full INQUIRY data. The size used by CAM is based on the additionnal length field returned by the device. Then CAM tries to read (additionnal length + 4) bytes in order to get the full INQUIRY data. As a result, if your device returns a odd value as 'additionnal length' on the short INQUIRY (36 bytes), then the problem can occur when CAM attemps to read the full INQUIRY data. I don't know if such an additionnal byte is to be silently ignored, but I never read that it must be so in SCSI specifications. If I missed something, may-be SCSI experts could point what I missed. (?) G=E9rard. On Mon, 18 Nov 2002 xxxlucasxxx@canoemail.com wrote: > Hi, > > I am having a problem getting two seagate (compaq) ST15150W > drives initialized at boot. > > dmesg gives me the bellow message for the SCSI card and drive (I am > trying one at a time not to confuse matters). In this case I have set > the drive as bootable in the SCSI BIOS. I have also tried it as not > bootable. I have tried another drive that has the device ID 0, in this > case it is device 2. All attemps have lead to nothing more then the > below. With the device set as not bootable the "SCAN AT BOOT" message > includes the target 2. The drive and card do work, I have tested them > on a W2K system without any problems other then being on a W2K system. > Any clues, a good schooling and taunts are welcome. > -------------------- > . > . > . > sym0: <875> port 0xe000-0xe0ff mem > 0xe5001000-0xe5001fff,0xe5000000-0xe50000ff irq 11 at device 13.0 on > pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym0: SCAN AT BOOT disabled for targets 0 1 3 4 5 6 8 9 10 11 12 13 14 > 15. > . > . > . > Waiting 15 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (probe2:sym0:0:2:0): extraneous data discarded. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 1). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. > (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > > -------------------- > Thanks in advance for any help. > > Lucas > > > > > Sign up today for your Free E-mail at: http://www.canoe.ca/CanoeMail > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message