From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 17 07:40:11 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93B9016A473 for ; Sun, 17 Jun 2007 07:40:11 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from m2a2.dyndns.org (p50910993.dip0.t-ipconnect.de [80.145.9.147]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADE813C48C for ; Sun, 17 Jun 2007 07:40:11 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: by merlin.emma.line.org (Postfix, from userid 500) id 7C3E7C0D7; Sun, 17 Jun 2007 09:28:00 +0200 (CEST) Date: Sun, 17 Jun 2007 09:28:00 +0200 From: Matthias Andree To: freebsd-scsi@freebsd.org Message-ID: <20070617072800.GA84802@merlin.emma.line.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.15 (2007-04-06) Subject: hald on sym(4) causes phase change log spam X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2007 07:40:11 -0000 Greetings, on a FreeBSD 6.2-STABLE machine that contains, among others, a Tekram DC-390U2W SCSI HBA (SYM53C895) and a Plextor PX-32TS SCSI CD-ROM, I get these pairs of log entries when running hald (hal-0.5.8.20070403_2): (pass0:sym0:0:2:0): phase change 2-3 16@3e86a768 resid=10. (pass0:sym0:0:2:0): phase change 2-3 16@3e86a768 resid=6. Are these caused by: - a firmware bug in the CD-ROM drive? - a bug in the sym(4) driver? - a bug or missing feature in hald? Thanks, -- Matthias Andree From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 18 02:14:11 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82A1316A46B for ; Mon, 18 Jun 2007 02:14:11 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 6BC2713C44B for ; Mon, 18 Jun 2007 02:14:11 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1I06ks-0004OG-N3 for freebsd-scsi@freebsd.org; Sun, 17 Jun 2007 19:14:10 -0700 Message-ID: <11169093.post@talk.nabble.com> Date: Sun, 17 Jun 2007 19:14:10 -0700 (PDT) From: emaney To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: smsrks2007@gmail.com Subject: simple SCSI question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 02:14:11 -0000 iam a student and new to SCSI, i have a question please someone help me to get the answer for this following question how an =E2=80=98initiator=E2=80=99 on a SCSI bus identifies the logical ent= ity with which it wants to communicate? can anyone help me with this question, iam not getting whats is logical entity --=20 View this message in context: http://www.nabble.com/simple-SCSI-question-tf= 3938007.html#a11169093 Sent from the freebsd-scsi mailing list archive at Nabble.com. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 18 11:08:46 2007 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.org Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA0BB16A52D for ; Mon, 18 Jun 2007 11:08:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D34FD13C45E for ; Mon, 18 Jun 2007 11:08:46 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l5IB8koC017768 for ; Mon, 18 Jun 2007 11:08:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l5IB8i9F017764 for freebsd-scsi@FreeBSD.org; Mon, 18 Jun 2007 11:08:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Jun 2007 11:08:44 GMT Message-Id: <200706181108.l5IB8i9F017764@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 11:08:47 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceProbeInfo comm o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems with Symbios/LSI o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x (regression) o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks 15 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/23314 scsi [aic] aic driver fails to detect Adaptec 1520B unless o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [feature request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/96133 scsi [scsi] [patch] add scsi quirk for joyfly 128mb flash u o kern/103702 scsi [cam] [patch] ChipsBnk: Unsupported USB memory stick 7 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 18 14:33:37 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F39D16A41F for ; Mon, 18 Jun 2007 14:33:37 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 8DBAE13C447 for ; Mon, 18 Jun 2007 14:33:36 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scott-longs-computer.local ([12.44.170.33]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l5IEXMt7029771; Mon, 18 Jun 2007 08:33:28 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <467697A8.3080503@samsco.org> Date: Mon, 18 Jun 2007 07:33:12 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: emaney References: <11169093.post@talk.nabble.com> In-Reply-To: <11169093.post@talk.nabble.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Mon, 18 Jun 2007 08:33:29 -0600 (MDT) X-Spam-Status: No, score=0.0 required=5.5 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: simple SCSI question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 14:33:37 -0000 emaney wrote: > iam a student and new to SCSI, i have a question please someone help me to > get the answer for this > following question > how an ‘initiator’ on a SCSI bus identifies the logical entity with which it > wants to communicate? > > can anyone help me with this question, iam not getting whats is logical > entity A parallel SCSI initiator will do two steps to identify the "logical entity" that it wants to talk to. First, it'll select the target by raising a signal on one of the 16 data lines. Once the target has responded, the initiator will send a series of 1 or more message bytes that identify the LUN inside the target that the upcoming command is for. This is a gross simplification of how the SCSI wire protocol works, and I suggest reading some of the docs on www.t11.org for more information. Scott From owner-freebsd-scsi@FreeBSD.ORG Mon Jun 18 15:25:39 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9BB4616A421 for ; Mon, 18 Jun 2007 15:25:39 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by mx1.freebsd.org (Postfix) with ESMTP id 5B8E213C4B0 for ; Mon, 18 Jun 2007 15:25:39 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so1222563nzn for ; Mon, 18 Jun 2007 08:25:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D2170ggDKYb+QlV1jCUw5eT5hsh/AMWbUNWAu3S1A1UGtovreHV8hgBhGmN93ctoN642g8JtsKieBDvKYFyF8A01sP1pgKnwkclkD19AzYY5xjhcNGj8taGALjEt8pnc7BfhDOyxeRxGt/oEtrndx3ryVVztu+QeEnKj+DZ23xU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GnkDTdiemksORNj17SQ0OhHQc4YP7XT2h5VQA+JRFrPwVAVafif2sMj+Pk3pBs3DqvlvGnj0O6BMjA+3wo5L7pJTmUBnmufMJbxQTOXLjSdEyB/MG7/lDd+VpPfSJnYUHBAga5TbSc2BC0l+UfUqtEULeY3LVLsUfB0+sN3ZUaQ= Received: by 10.114.159.1 with SMTP id h1mr6249037wae.1182180335429; Mon, 18 Jun 2007 08:25:35 -0700 (PDT) Received: by 10.114.125.14 with HTTP; Mon, 18 Jun 2007 08:25:35 -0700 (PDT) Message-ID: <7579f7fb0706180825wc4a58c1g88d858bbec50d8fb@mail.gmail.com> Date: Mon, 18 Jun 2007 08:25:35 -0700 From: "Matthew Jacob" To: "Scott Long" In-Reply-To: <467697A8.3080503@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <11169093.post@talk.nabble.com> <467697A8.3080503@samsco.org> Cc: freebsd-scsi@freebsd.org, emaney Subject: Re: simple SCSI question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 15:25:39 -0000 *cough* www.t10.org - t11 is for fibre channel (t13 for ata) :-) On 6/18/07, Scott Long wrote: > emaney wrote: > > iam a student and new to SCSI, i have a question please someone help me to > > get the answer for this > > following question > > how an 'initiator' on a SCSI bus identifies the logical entity with which it > > wants to communicate? > > > > can anyone help me with this question, iam not getting whats is logical > > entity > > A parallel SCSI initiator will do two steps to identify the "logical > entity" that it wants to talk to. First, it'll select the target by > raising a signal on one of the 16 data lines. Once the target has > responded, the initiator will send a series of 1 or more message bytes > that identify the LUN inside the target that the upcoming command is > for. This is a gross simplification of how the SCSI wire protocol > works, and I suggest reading some of the docs on www.t11.org for more > information. > > Scott > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 20 02:21:31 2007 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.org Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E5AD516A469 for ; Wed, 20 Jun 2007 02:21:31 +0000 (UTC) (envelope-from ade@lovett.com) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.freebsd.org (Postfix) with ESMTP id CDB8E13C44B for ; Wed, 20 Jun 2007 02:21:31 +0000 (UTC) (envelope-from ade@lovett.com) Received: from inferno.canal.lovett.com ([172.16.32.23]:51216) by mail.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1I0pYM-000AYE-NH; Tue, 19 Jun 2007 19:04:14 -0700 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <47887E3A-8E97-4AA0-8799-DF0FA5AB2E5B@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Ade Lovett Date: Tue, 19 Jun 2007 19:04:14 -0700 To: freebsd-scsi@FreeBSD.org X-Mailer: Apple Mail (2.752.3) Sender: ade@lovett.com Cc: Ade Lovett Subject: LSI SAS HBAs supported? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 02:21:32 -0000 Hi folks, Anyone happen to know what LSI SAS HBAs are supported (and by what driver). I need either 4- or 8-port, and absolutely none of that pointless hardware onboard RAID. http://www.lsi.com/storage_home/products_home/host_bus_adapters/ sas_hbas/lsisas3801e/index.html looks like a decent fit, going to a set of external SAS/SATA JBODs, with geom(4) doing all the real work. Cheers, -aDe From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 20 04:59:14 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27C7F16A469 for ; Wed, 20 Jun 2007 04:59:14 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by mx1.freebsd.org (Postfix) with ESMTP id DD54A13C484 for ; Wed, 20 Jun 2007 04:59:13 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so68556nzn for ; Tue, 19 Jun 2007 21:59:13 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XHYRq7aQCLmxfZbhYST+2eHiAPtTrwmUEn0Fdu/ka48MfOoVptboJh4cY+M4jLjtK6Uu+r6Yb4+YfhsxJLbkAP5R0gTOnPsLXJCI+9IyQ7dFBnFiS3km7ratFtY8hu6PtlibV6T3d6PjBy7WFKYfDIObT9MCyenfnyHxS/GdvKs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BnvXA+NEdlivih6ivDujSbhMnFD9yIvMRdeHsYoYMoizxX+JQVFwFcuBfTiNESAKtYagu7xNx/d6JSIRrYh+4JcXAFm9aUtn+To2mRHBBAyxbE36DmJPG6ktFC9D12MaJnZnugj525s/v4yrP0uAP4LGtKd8hJCtyHYAhvdd78M= Received: by 10.65.138.4 with SMTP id q4mr541452qbn.1182315552775; Tue, 19 Jun 2007 21:59:12 -0700 (PDT) Received: by 10.114.125.14 with HTTP; Tue, 19 Jun 2007 21:59:12 -0700 (PDT) Message-ID: <7579f7fb0706192159v7fd733acpeb322fcceeceb73@mail.gmail.com> Date: Tue, 19 Jun 2007 21:59:12 -0700 From: "Matthew Jacob" To: "Ade Lovett" In-Reply-To: <47887E3A-8E97-4AA0-8799-DF0FA5AB2E5B@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47887E3A-8E97-4AA0-8799-DF0FA5AB2E5B@FreeBSD.org> Cc: freebsd-scsi@freebsd.org Subject: Re: LSI SAS HBAs supported? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 04:59:14 -0000 mpt, but some of the PCI ids for the newer cards may not have been seen before. On 6/19/07, Ade Lovett wrote: > Hi folks, > > Anyone happen to know what LSI SAS HBAs are supported (and by what > driver). I need either 4- or 8-port, and absolutely none of that > pointless hardware onboard RAID. > > http://www.lsi.com/storage_home/products_home/host_bus_adapters/ > sas_hbas/lsisas3801e/index.html > > looks like a decent fit, going to a set of external SAS/SATA JBODs, > with geom(4) doing all the real work. > > Cheers, > -aDe > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 20 11:42:29 2007 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E05BF16A400 for ; Wed, 20 Jun 2007 11:42:29 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id C697713C48C for ; Wed, 20 Jun 2007 11:42:29 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1I0yZu-0003TW-Jq for freebsd-scsi@freebsd.org; Wed, 20 Jun 2007 04:42:26 -0700 Message-ID: <11211594.post@talk.nabble.com> Date: Wed, 20 Jun 2007 04:42:26 -0700 (PDT) From: emaney To: freebsd-scsi@freebsd.org In-Reply-To: <467697A8.3080503@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: smsrks2007@gmail.com References: <11169093.post@talk.nabble.com> <467697A8.3080503@samsco.org> Subject: Re: simple SCSI question X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 11:42:30 -0000 Scott Long-2 wrote: >=20 > emaney wrote: >> iam a student and new to SCSI, i have a question please someone help me >> to >> get the answer for this >> following question >> how an =E2=80=98initiator=E2=80=99 on a SCSI bus identifies the logical = entity with which >> it >> wants to communicate? >>=20 >> can anyone help me with this question, iam not getting whats is logical >> entity >=20 > A parallel SCSI initiator will do two steps to identify the "logical > entity" that it wants to talk to. First, it'll select the target by > raising a signal on one of the 16 data lines. Once the target has > responded, the initiator will send a series of 1 or more message bytes > that identify the LUN inside the target that the upcoming command is > for. This is a gross simplification of how the SCSI wire protocol > works, and I suggest reading some of the docs on www.t11.org for more > information. >=20 > Scott >=20 > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" >=20 >=20 somewhere else i read following about initiator identifying logical unit.............is it similar to what you have said? The SCSI ID of the target is selected in the selection phase (BSY & SEL=20 asserted, Data lines that corresponds to initator ID and target ID=20 asserted). The initiator should also assert ATN in the selection phase.=20 The MESSAGE OUT phase (BSY & C/D & MSG asserted) forced by ATN can now=20 be use by the initiator to send an IDENTIFY message to select the LUN.=20 --=20 View this message in context: http://www.nabble.com/simple-SCSI-question-tf= 3938007.html#a11211594 Sent from the freebsd-scsi mailing list archive at Nabble.com. From owner-freebsd-scsi@FreeBSD.ORG Wed Jun 20 19:29:19 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F33C516A421 for ; Wed, 20 Jun 2007 19:29:18 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 56BA313C45E for ; Wed, 20 Jun 2007 19:29:18 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: by py-out-1112.google.com with SMTP id a29so583210pyi for ; Wed, 20 Jun 2007 12:29:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oFRODSz27jJlFhg+hz3c3F0CAuzk34+W3nCo3CW3K46ZEQyrUfBDmG/kf54Waz+08IWd0arFyhR+JXVOR4V4ChZY9IaFlucL1h7wjk8TFCBOXtHxfPPB3+/sfG5vkzrCxGuyQaLc3ipXOIpMgsMFk1PvE+Ts611UZ7E6r06g0BI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LOR/Q3s02DnPHAFdA/6IsDqTwWXtyeYxMiq8DPMFii7MpY3glj1OfrBys9hLnHauqF+XnhtMork/d6ZCA/Wkm4S25/l3d/279pghFt2KGraBJ2iWBpu1V5puuL1ZniB7yzjWr8scYEm0i2Qjxh0Sk7V08NRuAoqiNj/lbVr0eus= Received: by 10.114.168.1 with SMTP id q1mr630778wae.1182366274048; Wed, 20 Jun 2007 12:04:34 -0700 (PDT) Received: by 10.114.125.14 with HTTP; Wed, 20 Jun 2007 12:04:34 -0700 (PDT) Message-ID: <7579f7fb0706201204k67ccff77o4cc9bbdaf38cacc7@mail.gmail.com> Date: Wed, 20 Jun 2007 12:04:34 -0700 From: "Matthew Jacob" To: "Rong-en Fan" In-Reply-To: <6eb82e0706032030k3a0ac855r1f41b2c2f62b55d3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0706032030k3a0ac855r1f41b2c2f62b55d3@mail.gmail.com> Cc: scsi@freebsd.org Subject: Re: inquiry data fails comparison at DV1 step X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 19:29:19 -0000 Sorry for not seeing this earlier and responding. Can you chase down why the DV1 comparison is failing? The 6.6MB/s is really async/wide. On 6/3/07, Rong-en Fan wrote: > I reported this to scottl@ some time ago. I think > it may be better to post it here. > > I have a system running i386 7-CURRENT as of today. > An external raid connected to a Adaptec 29160, but it > is only running at 6.6MB/s. relevant dmesg are: > > ahc0: port 0x2500-0x25ff mem > 0xfbfdf000-0xfbfdffff irq 18 at device 2.0 on pci1 > ahc0: [ITHREAD] > (probe2:ahc0:0:0:0): inquiry data fails comparison at DV1 step > (probe2:ahc0:0:0:0): inquiry data fails comparison at DV1 step > (probe2:ahc0:0:0:0): inquiry data fails comparison at DV1 step > (probe2:ahc0:0:0:0): inquiry data fails comparison at DV1 step > (probe2:ahc0:0:0:0): inquiry data fails comparison at DV1 step > da2 at ahc0 bus 0 target 0 lun 0 > da2: Fixed Direct Access SCSI-4 device > da2: 6.600MB/s transfers (16bit) > da2: Command Queueing Enabled > da2: 915737MB (1875429888 512 byte sectors: 255H 63S/T 116740C) > > This card and the raid box work perfectly with 6-STABLE. > I heard from Scott that making DV work is really tricky and > not that easy. I would like to help to test any patches. > Or is there any workaround to this problem? > > Regards, > Rong-En Fan > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 22 17:09:59 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A61516A46B for ; Fri, 22 Jun 2007 17:09:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id C572113C44B for ; Fri, 22 Jun 2007 17:09:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l5MH8jk9069093 for ; Fri, 22 Jun 2007 11:08:45 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 22 Jun 2007 11:09:18 -0600 (MDT) Message-Id: <20070622.110918.-345494230.imp@bsdimp.com> To: scsi@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 22 Jun 2007 11:08:45 -0600 (MDT) Cc: Subject: DA_Q_NO_SYN_CACHE X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 17:09:59 -0000 Is the DA_Q_NO_SYN_CACHE quirk still needed? there's suggestions in some PRs I'm looking at to never send this command for UFI devices. Was that ever implemented, and is that a good idea? Warner From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 22 17:36:59 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A87D16A400 for ; Fri, 22 Jun 2007 17:36:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id D0E9B13C44B for ; Fri, 22 Jun 2007 17:36:58 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l5MHZ4CJ069303; Fri, 22 Jun 2007 11:35:05 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 22 Jun 2007 11:35:38 -0600 (MDT) Message-Id: <20070622.113538.-749248556.imp@bsdimp.com> To: scottl@samsco.org From: "M. Warner Losh" In-Reply-To: <467C055A.5090008@samsco.org> References: <20070622.110918.-345494230.imp@bsdimp.com> <467C055A.5090008@samsco.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 22 Jun 2007 11:35:05 -0600 (MDT) Cc: scsi@freebsd.org Subject: Re: DA_Q_NO_SYN_CACHE X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 17:36:59 -0000 In message: <467C055A.5090008@samsco.org> Scott Long writes: : M. Warner Losh wrote: : > Is the DA_Q_NO_SYN_CACHE quirk still needed? there's suggestions in : > some PRs I'm looking at to never send this command for UFI devices. : > Was that ever implemented, and is that a good idea? : > : : Are you suggesting modifying umass to universally disable the sync cache : for UFI devices? That's something that should be looked at, but I don't : think that the 7.0 code freeze is the best time to experiment with that. My question was more "has this already been done," since if it has, I can close about 15PRs with no action required in the tree. If it has not been done, then we're past what I feel comfortable doing during a freeze as well, unless one can get a lot of verified testing done with ~100 devices or more. So it sounds like the answer is 'We need to keep adding the quirks for those devices that hang the system' that can be found in the PR database. That I do feel comfortable doing during a code freeze. : There has also been talk about re-doing the way that sync cache is done : so that it's only done if the device reports that its write cache is : present and enabled. That would also be useful. Warner From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 22 17:54:28 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8473616A400 for ; Fri, 22 Jun 2007 17:54:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 4103413C45A for ; Fri, 22 Jun 2007 17:54:27 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scott-longs-computer.local (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l5MHMck9057983; Fri, 22 Jun 2007 11:22:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <467C055A.5090008@samsco.org> Date: Fri, 22 Jun 2007 10:22:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: "M. Warner Losh" References: <20070622.110918.-345494230.imp@bsdimp.com> In-Reply-To: <20070622.110918.-345494230.imp@bsdimp.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Fri, 22 Jun 2007 11:22:39 -0600 (MDT) X-Spam-Status: No, score=0.0 required=5.5 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: scsi@freebsd.org Subject: Re: DA_Q_NO_SYN_CACHE X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 17:54:28 -0000 M. Warner Losh wrote: > Is the DA_Q_NO_SYN_CACHE quirk still needed? there's suggestions in > some PRs I'm looking at to never send this command for UFI devices. > Was that ever implemented, and is that a good idea? > Are you suggesting modifying umass to universally disable the sync cache for UFI devices? That's something that should be looked at, but I don't think that the 7.0 code freeze is the best time to experiment with that. There has also been talk about re-doing the way that sync cache is done so that it's only done if the device reports that its write cache is present and enabled. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 22 19:05:47 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D6D616A421 for ; Fri, 22 Jun 2007 19:05:47 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id DE18113C487 for ; Fri, 22 Jun 2007 19:05:46 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scott-longs-computer.local (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l5MJ5bJF058375; Fri, 22 Jun 2007 13:05:38 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <467C1D7D.7010501@samsco.org> Date: Fri, 22 Jun 2007 12:05:33 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: "M. Warner Losh" References: <20070622.110918.-345494230.imp@bsdimp.com> <467C055A.5090008@samsco.org> <20070622.113538.-749248556.imp@bsdimp.com> In-Reply-To: <20070622.113538.-749248556.imp@bsdimp.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Fri, 22 Jun 2007 13:05:39 -0600 (MDT) X-Spam-Status: No, score=0.0 required=5.5 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: scsi@freebsd.org Subject: Re: DA_Q_NO_SYN_CACHE X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 19:05:47 -0000 M. Warner Losh wrote: > In message: <467C055A.5090008@samsco.org> > Scott Long writes: > : M. Warner Losh wrote: > : > Is the DA_Q_NO_SYN_CACHE quirk still needed? there's suggestions in > : > some PRs I'm looking at to never send this command for UFI devices. > : > Was that ever implemented, and is that a good idea? > : > > : > : Are you suggesting modifying umass to universally disable the sync cache > : for UFI devices? That's something that should be looked at, but I don't > : think that the 7.0 code freeze is the best time to experiment with that. > > My question was more "has this already been done," since if it has, I > can close about 15PRs with no action required in the tree. If it has > not been done, then we're past what I feel comfortable doing during a > freeze as well, unless one can get a lot of verified testing done with > ~100 devices or more. > > So it sounds like the answer is 'We need to keep adding the quirks for > those devices that hang the system' that can be found in the PR > database. That I do feel comfortable doing during a code freeze. I don't see anything in the umass driver that suggests it gets automatically handled. So yeah, the right thing to do at this point is to just add more quirks (make sure you read Nate's posting on adding quirks first), and hopefully we'll improve the state of the art in the future. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 22 21:04:41 2007 Return-Path: X-Original-To: scsi@freebsd.org Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 057A516A421 for ; Fri, 22 Jun 2007 21:04:41 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id C097113C447 for ; Fri, 22 Jun 2007 21:04:40 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.1/8.14.1) with ESMTP id l5MKS5b9074848 for ; Fri, 22 Jun 2007 13:28:13 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.1/8.14.1/Submit) with ESMTP id l5MKS5bU074845 for ; Fri, 22 Jun 2007 13:28:05 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 22 Jun 2007 13:28:05 -0700 (PDT) From: mjacob@freebsd.org To: scsi@freebsd.org Message-ID: <20070622132621.Q74839@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: FYI: a note about some automatic attach/detach stuff X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2007 21:04:41 -0000 Barf. This happened after an event caused a rescan.. Sigh... Hopefully I'll get this tracked down for RELENG_7.0 proberegister: Unable to probe new device. Unable to allocate softc (xpt0:isp0:0:395:0): xpt_scan_lun: cam_alloc_periph returned an error, can't continue probe Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex isp r = 0 (0xc2d71090) locked @ cam/cam_xpt.c:7140 KDB: stack backtrace: db_trace_self_wrapper(c0a3b900,d3c83ae4,c077bebd,c0a3bcbf,d3c83af8,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a3bcbf,d3c83af8,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0a63882,c073a77c,c2e66000,...) at witness_warn+0x1cd trap(d3c83b80) at trap+0x115 calltrap() at calltrap+0x6 --- trap 0xc, eip = 0xc0468ef4, esp = 0xd3c83bc0, ebp = 0xd3c83c04 --- xpt_scan_bus(c2dc4680,c4e4d800,d3c83c20,246,c2ead594,...) at xpt_scan_bus+0x334 camisr_runqueue(c2d71090,0,c09efaf9,1be4,0,...) at camisr_runqueue+0x39f camisr(0,0,c0a35bf3,471,c2dc4664,...) at camisr+0x11a ithread_loop(c2e5a0e0,d3c83d38,7c72604,3e800001,c2e66000,...) at ithread_loop+0x1b5 fork_exit(c072afc0,c2e5a0e0,d3c83d38) at fork_exit+0x57 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xd3c83d70, ebp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xdeadc141 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0468ef4 stack pointer = 0x28:0xd3c83bc0 frame pointer = 0x28:0xd3c83c04 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 19 (swi2: cambio) [thread pid 19 tid 100015 ] Stopped at xpt_scan_bus+0x334: testb $0x4,0x63(%edx) db> bt Tracing pid 19 tid 100015 td 0xc2d84800 xpt_scan_bus(c2dc4680,c4e4d800,d3c83c20,246,c2ead594,...) at xpt_scan_bus+0x334 camisr_runqueue(c2d71090,0,c09efaf9,1be4,0,...) at camisr_runqueue+0x39f camisr(0,0,c0a35bf3,471,c2dc4664,...) at camisr+0x11a ithread_loop(c2e5a0e0,d3c83d38,7c72604,3e800001,c2e66000,...) at ithread_loop+0x1b5 fork_exit(c072afc0,c2e5a0e0,d3c83d38) at fork_exit+0x57 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xd3c83d70, ebp = 0 --- db>