From owner-freebsd-scsi@FreeBSD.ORG Mon May 5 11:07:13 2008 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C3671065691 for ; Mon, 5 May 2008 11:07:13 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EEDAA8FC13 for ; Mon, 5 May 2008 11:07:12 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m45B7CcK070840 for ; Mon, 5 May 2008 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m45B7CcC070836 for freebsd-scsi@FreeBSD.org; Mon, 5 May 2008 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 May 2008 11:07:12 GMT Message-Id: <200805051107.m45B7CcC070836@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 freebsd-scsi@FreeBSD.org 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, 05 May 2008 11:07:13 -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/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts 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 o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 14 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [dpt] [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/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/120487 scsi [sg] scsi_sg incompatible with scanners o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc 8 problems total. From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 22:32:25 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA0061065673 for ; Wed, 7 May 2008 22:32:25 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id B6AAA8FC1B for ; Wed, 7 May 2008 22:32:25 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id F08BA1C8042 for ; Wed, 7 May 2008 15:12:01 -0700 (PDT) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30914-06 for ; Wed, 7 May 2008 15:12:01 -0700 (PDT) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id F3E3B1C803D for ; Wed, 7 May 2008 15:12:00 -0700 (PDT) Message-ID: <48222930.2010808@miralink.com> Date: Wed, 07 May 2008 15:12:00 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed May 7 15:12:01 2008 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4822293125393377160525 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Subject: USB drive serial numbers 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, 07 May 2008 22:32:25 -0000 Can someone send me the output of "camcontrol inquiry daX" where daX is a usb attached hard drive? I'm interested to know if the USB external hard drives report a serial number as the USB flash drives I currently have in my possession do not report one. eg: SCSI hard drive: sudo camcontrol inquiry da0 pass0: Fixed Direct Access SCSI-3 device pass0: Serial Number 3KT17YJL pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled eg: USB flash drive: sudo camcontrol inquiry da3 pass4: Removable Direct Access SCSI-0 device pass4: Serial Number pass4: 40.000MB/s transfers Sean From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 23:20:36 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1CBB1065677 for ; Wed, 7 May 2008 23:20:36 +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 590BA8FC0A for ; Wed, 7 May 2008 23:20:36 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m47NKWfL056343; Wed, 7 May 2008 17:20:32 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48223940.5090109@samsco.org> Date: Wed, 07 May 2008 17:20:32 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Sean Bruno References: <48222930.2010808@miralink.com> In-Reply-To: <48222930.2010808@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham 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: USB drive serial numbers 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, 07 May 2008 23:20:36 -0000 Sean Bruno wrote: > Can someone send me the output of "camcontrol inquiry daX" where daX is > a usb attached hard drive? I'm interested to know if the USB external > hard drives report a serial number as the USB flash drives I currently > have in my possession do not report one. > > eg: SCSI hard drive: > sudo camcontrol inquiry da0 > pass0: Fixed Direct Access SCSI-3 device > pass0: Serial Number 3KT17YJL > pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged > Queueing Enabled > > > eg: USB flash drive: > sudo camcontrol inquiry da3 > pass4: Removable Direct Access SCSI-0 device > pass4: Serial Number > pass4: 40.000MB/s transfers > CAM used to assume that all DA devices supported the serial number EVPD page. I recently changed it to query the device for the list of pages it does support, and only ask for the serial number page if it does (which in turns cuts down on a whole lot of kernel printf noise). My experience is that some devices do, but most devices don't. If you want to check your devices manually, do: camcontrol cmd pass0 -v -c "12 01 00 00 255 00" -i 255 "-" | hd If 0x80 appears after the 4th byte, the device claims support for querying the serial number. The serial number can then be fetched with camcontrol cmd pass0 -v -c "12 01 80 00 255 00" -i 255 "-" | hd Or via camcontrol inq pass0 -S Scott From owner-freebsd-scsi@FreeBSD.ORG Wed May 7 23:53:38 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10B2D1065678 for ; Wed, 7 May 2008 23:53:38 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id D71CB8FC13 for ; Wed, 7 May 2008 23:53:37 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 8BE471C8042; Wed, 7 May 2008 16:53:37 -0700 (PDT) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21676-08; Wed, 7 May 2008 16:53:36 -0700 (PDT) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 2E3091C803D; Wed, 7 May 2008 16:53:36 -0700 (PDT) Message-ID: <482240FF.4030704@miralink.com> Date: Wed, 07 May 2008 16:53:35 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Scott Long References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> In-Reply-To: <48223940.5090109@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed May 7 16:53:37 2008 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 48224101296651186327471 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Cc: freebsd-scsi@freebsd.org Subject: Re: USB drive serial numbers 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, 07 May 2008 23:53:38 -0000 Scott Long wrote: > Sean Bruno wrote: >> Can someone send me the output of "camcontrol inquiry daX" where daX >> is a usb attached hard drive? I'm interested to know if the USB >> external hard drives report a serial number as the USB flash drives I >> currently have in my possession do not report one. >> >> eg: SCSI hard drive: >> sudo camcontrol inquiry da0 >> pass0: Fixed Direct Access SCSI-3 device >> pass0: Serial Number 3KT17YJL >> pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged >> Queueing Enabled >> >> >> eg: USB flash drive: >> sudo camcontrol inquiry da3 >> pass4: Removable Direct Access SCSI-0 device >> pass4: Serial Number >> pass4: 40.000MB/s transfers >> > > CAM used to assume that all DA devices supported the serial number EVPD > page. I recently changed it to query the device for the list of pages > it does support, and only ask for the serial number page if it does > (which in turns cuts down on a whole lot of kernel printf noise). My > experience is that some devices do, but most devices don't. If you want > to check your devices manually, do: > > camcontrol cmd pass0 -v -c "12 01 00 00 255 00" -i 255 "-" | hd > > If 0x80 appears after the 4th byte, the device claims support for > querying the serial number. The serial number can then be fetched with > > camcontrol cmd pass0 -v -c "12 01 80 00 255 00" -i 255 "-" | hd > > Or via > > camcontrol inq pass0 -S > > > Scott Hrm....it looks like asking for page 0x80 directly is returning the same as requesting page 0x80 or asking for all pages: sudo camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 1 lun 0 (da1,pass1) at scbus0 target 6 lun 0 (ses0,pass2) at scbus1 target 1 lun 0 (da2,pass3) at scbus2 target 0 lun 0 (pass4,da3) sudo camcontrol cmd pass4 -v -c "12 01 00 00 255 00" -i 255 "-" | hd 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 |........TOSHIBA | 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 |TransMemory | 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 |5.00PMAP1234....| 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000f0 sudo camcontrol cmd pass4 -v -c "12 01 80 00 255 00" -i 255 "-" | hd 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 |........TOSHIBA | 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 |TransMemory | 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 |5.00PMAP1234....| 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000f0 sean From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 00:03:50 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CC2D106567B for ; Thu, 8 May 2008 00:03:50 +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 DB29B8FC13 for ; Thu, 8 May 2008 00:03:49 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m4803jXi056507; Wed, 7 May 2008 18:03:45 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48224361.10809@samsco.org> Date: Wed, 07 May 2008 18:03:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Sean Bruno References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> In-Reply-To: <482240FF.4030704@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham 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: USB drive serial numbers 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: Thu, 08 May 2008 00:03:50 -0000 Sean Bruno wrote: > Scott Long wrote: >> Sean Bruno wrote: >>> Can someone send me the output of "camcontrol inquiry daX" where daX >>> is a usb attached hard drive? I'm interested to know if the USB >>> external hard drives report a serial number as the USB flash drives I >>> currently have in my possession do not report one. >>> >>> eg: SCSI hard drive: >>> sudo camcontrol inquiry da0 >>> pass0: Fixed Direct Access SCSI-3 device >>> pass0: Serial Number 3KT17YJL >>> pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged >>> Queueing Enabled >>> >>> >>> eg: USB flash drive: >>> sudo camcontrol inquiry da3 >>> pass4: Removable Direct Access SCSI-0 device >>> pass4: Serial Number >>> pass4: 40.000MB/s transfers >>> >> >> CAM used to assume that all DA devices supported the serial number EVPD >> page. I recently changed it to query the device for the list of pages >> it does support, and only ask for the serial number page if it does >> (which in turns cuts down on a whole lot of kernel printf noise). My >> experience is that some devices do, but most devices don't. If you want >> to check your devices manually, do: >> >> camcontrol cmd pass0 -v -c "12 01 00 00 255 00" -i 255 "-" | hd >> >> If 0x80 appears after the 4th byte, the device claims support for >> querying the serial number. The serial number can then be fetched with >> >> camcontrol cmd pass0 -v -c "12 01 80 00 255 00" -i 255 "-" | hd >> >> Or via >> >> camcontrol inq pass0 -S >> >> >> Scott > > Hrm....it looks like asking for page 0x80 directly is returning the same > as requesting page 0x80 or asking for all pages: > > sudo camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 1 lun 0 (da1,pass1) > at scbus0 target 6 lun 0 (ses0,pass2) > at scbus1 target 1 lun 0 (da2,pass3) > at scbus2 target 0 lun 0 (pass4,da3) > > sudo camcontrol cmd pass4 -v -c "12 01 00 00 255 00" -i 255 "-" | hd > 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 > |........TOSHIBA | > 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 > |TransMemory | > 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 > |5.00PMAP1234....| > 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > * > 000000f0 > > sudo camcontrol cmd pass4 -v -c "12 01 80 00 255 00" -i 255 "-" | hd > 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 > |........TOSHIBA | > 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 > |TransMemory | > 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 > |5.00PMAP1234....| > 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > * Wow, that's just fantastically broken. It's completely ignoring the EVPD bit in the request and simply reporting standard inq data. I guess the only thing that keeps CAM from exploding on this is that it sees the length field in byte 4 as 0x01, so it doesn't search too far into what it thinks is the response. I'll have to read the spec some more to see if there's a standard way to report that the device supports the EVPD bit that FreeBSD should be checking. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 00:49:07 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7579106567A for ; Thu, 8 May 2008 00:49:07 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 790E78FC0C for ; Thu, 8 May 2008 00:49:07 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 41C961C8042; Wed, 7 May 2008 17:49:07 -0700 (PDT) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19960-08; Wed, 7 May 2008 17:49:05 -0700 (PDT) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 8D89F1C803D; Wed, 7 May 2008 17:49:05 -0700 (PDT) Message-ID: <48224E01.4030907@miralink.com> Date: Wed, 07 May 2008 17:49:05 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Scott Long References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> <48224361.10809@samsco.org> In-Reply-To: <48224361.10809@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed May 7 17:49:06 2008 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 48224e02153291186327471 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Cc: freebsd-scsi@freebsd.org Subject: Re: USB drive serial numbers 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: Thu, 08 May 2008 00:49:07 -0000 Scott Long wrote: > Sean Bruno wrote: >> Scott Long wrote: >>> Sean Bruno wrote: >>>> Can someone send me the output of "camcontrol inquiry daX" where >>>> daX is a usb attached hard drive? I'm interested to know if the >>>> USB external hard drives report a serial number as the USB flash >>>> drives I currently have in my possession do not report one. >>>> >>>> eg: SCSI hard drive: >>>> sudo camcontrol inquiry da0 >>>> pass0: Fixed Direct Access SCSI-3 device >>>> pass0: Serial Number 3KT17YJL >>>> pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged >>>> Queueing Enabled >>>> >>>> >>>> eg: USB flash drive: >>>> sudo camcontrol inquiry da3 >>>> pass4: Removable Direct Access SCSI-0 >>>> device >>>> pass4: Serial Number >>>> pass4: 40.000MB/s transfers >>>> >>> >>> CAM used to assume that all DA devices supported the serial number EVPD >>> page. I recently changed it to query the device for the list of pages >>> it does support, and only ask for the serial number page if it does >>> (which in turns cuts down on a whole lot of kernel printf noise). My >>> experience is that some devices do, but most devices don't. If you >>> want >>> to check your devices manually, do: >>> >>> camcontrol cmd pass0 -v -c "12 01 00 00 255 00" -i 255 "-" | hd >>> >>> If 0x80 appears after the 4th byte, the device claims support for >>> querying the serial number. The serial number can then be fetched with >>> >>> camcontrol cmd pass0 -v -c "12 01 80 00 255 00" -i 255 "-" | hd >>> >>> Or via >>> >>> camcontrol inq pass0 -S >>> >>> >>> Scott >> >> Hrm....it looks like asking for page 0x80 directly is returning the same >> as requesting page 0x80 or asking for all pages: >> >> sudo camcontrol devlist >> at scbus0 target 0 lun 0 (da0,pass0) >> at scbus0 target 1 lun 0 (da1,pass1) >> at scbus0 target 6 lun 0 (ses0,pass2) >> at scbus1 target 1 lun 0 (da2,pass3) >> at scbus2 target 0 lun 0 (pass4,da3) >> >> sudo camcontrol cmd pass4 -v -c "12 01 00 00 255 00" -i 255 "-" | hd >> 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 >> |........TOSHIBA | >> 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 >> |TransMemory | >> 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 >> |5.00PMAP1234....| >> 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> |................| >> * >> 000000f0 >> >> sudo camcontrol cmd pass4 -v -c "12 01 80 00 255 00" -i 255 "-" | hd >> 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 >> |........TOSHIBA | >> 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 >> |TransMemory | >> 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 >> |5.00PMAP1234....| >> 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >> |................| >> * > > Wow, that's just fantastically broken. It's completely ignoring the > EVPD bit in the request and simply reporting standard inq data. I > guess the only thing that keeps CAM from exploding on this is that it > sees the length field in byte 4 as 0x01, so it doesn't search too far > into what it thinks is the response. I'll have to read the spec some > more to see if there's a standard way to report that the device supports > the EVPD bit that FreeBSD should be checking. > > Scott Any chance you have a USB hard drive lying around that you could run a "camcontrol inq"? Sean From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 06:36:51 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDE301065670 for ; Thu, 8 May 2008 06:36:51 +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 650E98FC12 for ; Thu, 8 May 2008 06:36:51 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m486alls058473; Thu, 8 May 2008 00:36:47 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48229F7F.6040602@samsco.org> Date: Thu, 08 May 2008 00:36:47 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Sean Bruno References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> <48224361.10809@samsco.org> <48224E01.4030907@miralink.com> In-Reply-To: <48224E01.4030907@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham 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: USB drive serial numbers 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: Thu, 08 May 2008 06:36:51 -0000 Sean Bruno wrote: > Scott Long wrote: >> Sean Bruno wrote: >>> Scott Long wrote: >>>> Sean Bruno wrote: >>>>> Can someone send me the output of "camcontrol inquiry daX" where >>>>> daX is a usb attached hard drive? I'm interested to know if the >>>>> USB external hard drives report a serial number as the USB flash >>>>> drives I currently have in my possession do not report one. >>>>> >>>>> eg: SCSI hard drive: >>>>> sudo camcontrol inquiry da0 >>>>> pass0: Fixed Direct Access SCSI-3 device >>>>> pass0: Serial Number 3KT17YJL >>>>> pass0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged >>>>> Queueing Enabled >>>>> >>>>> >>>>> eg: USB flash drive: >>>>> sudo camcontrol inquiry da3 >>>>> pass4: Removable Direct Access SCSI-0 >>>>> device >>>>> pass4: Serial Number >>>>> pass4: 40.000MB/s transfers >>>>> >>>> >>>> CAM used to assume that all DA devices supported the serial number EVPD >>>> page. I recently changed it to query the device for the list of pages >>>> it does support, and only ask for the serial number page if it does >>>> (which in turns cuts down on a whole lot of kernel printf noise). My >>>> experience is that some devices do, but most devices don't. If you >>>> want >>>> to check your devices manually, do: >>>> >>>> camcontrol cmd pass0 -v -c "12 01 00 00 255 00" -i 255 "-" | hd >>>> >>>> If 0x80 appears after the 4th byte, the device claims support for >>>> querying the serial number. The serial number can then be fetched with >>>> >>>> camcontrol cmd pass0 -v -c "12 01 80 00 255 00" -i 255 "-" | hd >>>> >>>> Or via >>>> >>>> camcontrol inq pass0 -S >>>> >>>> >>>> Scott >>> >>> Hrm....it looks like asking for page 0x80 directly is returning the same >>> as requesting page 0x80 or asking for all pages: >>> >>> sudo camcontrol devlist >>> at scbus0 target 0 lun 0 (da0,pass0) >>> at scbus0 target 1 lun 0 (da1,pass1) >>> at scbus0 target 6 lun 0 (ses0,pass2) >>> at scbus1 target 1 lun 0 (da2,pass3) >>> at scbus2 target 0 lun 0 (pass4,da3) >>> >>> sudo camcontrol cmd pass4 -v -c "12 01 00 00 255 00" -i 255 "-" | hd >>> 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 >>> |........TOSHIBA | >>> 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 >>> |TransMemory | >>> 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 >>> |5.00PMAP1234....| >>> 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >>> |................| >>> * >>> 000000f0 >>> >>> sudo camcontrol cmd pass4 -v -c "12 01 80 00 255 00" -i 255 "-" | hd >>> 00000000 00 80 00 01 1f 00 00 00 54 4f 53 48 49 42 41 20 >>> |........TOSHIBA | >>> 00000010 54 72 61 6e 73 4d 65 6d 6f 72 79 20 20 20 20 20 >>> |TransMemory | >>> 00000020 35 2e 30 30 50 4d 41 50 31 32 33 34 00 00 00 00 >>> |5.00PMAP1234....| >>> 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >>> |................| >>> * >> >> Wow, that's just fantastically broken. It's completely ignoring the >> EVPD bit in the request and simply reporting standard inq data. I >> guess the only thing that keeps CAM from exploding on this is that it >> sees the length field in byte 4 as 0x01, so it doesn't search too far >> into what it thinks is the response. I'll have to read the spec some >> more to see if there's a standard way to report that the device supports >> the EVPD bit that FreeBSD should be checking. >> >> Scott > Any chance you have a USB hard drive lying around that you could run a > "camcontrol inq"? > > Sean A thumb drive that I have lying around has the same problem, it ignores the EVPD bit and happily returns std inq data for all requests. An ATA->USB+Firewire enclosure works correctly; it doesn't support any VPD pages, but returns a sense error in response, as it should. Given that Firewire is more explicit in its implementation of SBP/SPC, I'm not too surprised that it worked correctly (I tested this over the USB port, though). I have another ATA->USB enclosure lying around, but I can't find the power cord for it right now. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 14:58:25 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F9DE106564A for ; Thu, 8 May 2008 14:58:25 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 587358FC12 for ; Thu, 8 May 2008 14:58:25 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id E19B41C803D; Thu, 8 May 2008 07:58:24 -0700 (PDT) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19322-03; Thu, 8 May 2008 07:58:24 -0700 (PDT) Received: from [10.47.1.94] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id DBB711C8030; Thu, 8 May 2008 07:58:23 -0700 (PDT) Message-ID: <4823150F.30909@miralink.com> Date: Thu, 08 May 2008 07:58:23 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Scott Long References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> <48224361.10809@samsco.org> <48224E01.4030907@miralink.com> <48229F7F.6040602@samsco.org> In-Reply-To: <48229F7F.6040602@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu May 8 07:58:24 2008 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 48231510259971091686056 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.237 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, AWL=0.262, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.237 X-Spam-Level: Cc: freebsd-scsi@freebsd.org Subject: Re: USB drive serial numbers 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: Thu, 08 May 2008 14:58:25 -0000 > > A thumb drive that I have lying around has the same problem, it ignores > the EVPD bit and happily returns std inq data for all requests. An > ATA->USB+Firewire enclosure works correctly; it doesn't support any > VPD pages, but returns a sense error in response, as it should. Given > that Firewire is more explicit in its implementation of SBP/SPC, I'm not > too surprised that it worked correctly (I tested this over the USB port, > though). I have another ATA->USB enclosure lying around, but I can't > find the power cord for it right now. > > Scott > Interesting. Is there some other method that could be used to "identify" drives in the system? Sean From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 15:01:40 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D16B81065679 for ; Thu, 8 May 2008 15:01:40 +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 859E98FC0C for ; Thu, 8 May 2008 15:01:40 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m48F1bCS061978; Thu, 8 May 2008 09:01:37 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <482315D1.4040401@samsco.org> Date: Thu, 08 May 2008 09:01:37 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Sean Bruno References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> <48224361.10809@samsco.org> <48224E01.4030907@miralink.com> <48229F7F.6040602@samsco.org> <4823150F.30909@miralink.com> In-Reply-To: <4823150F.30909@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham 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: USB drive serial numbers 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: Thu, 08 May 2008 15:01:40 -0000 Sean Bruno wrote: > >> >> A thumb drive that I have lying around has the same problem, it ignores >> the EVPD bit and happily returns std inq data for all requests. An >> ATA->USB+Firewire enclosure works correctly; it doesn't support any >> VPD pages, but returns a sense error in response, as it should. Given >> that Firewire is more explicit in its implementation of SBP/SPC, I'm not >> too surprised that it worked correctly (I tested this over the USB port, >> though). I have another ATA->USB enclosure lying around, but I can't >> find the power cord for it right now. >> >> Scott >> > > Interesting. Is there some other method that could be used to > "identify" drives > in the system? > Sean I think the only option is to do a std inq followed by an EVPD inquiry and bcmp the results. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 01:32:05 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D399106564A for ; Fri, 9 May 2008 01:32:05 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from florence.spa.umn.edu (florence.spa.umn.edu [128.101.220.10]) by mx1.freebsd.org (Postfix) with ESMTP id 44D628FC17 for ; Fri, 9 May 2008 01:32:05 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from peevish.spa.umn.edu ([128.101.220.230]) by florence.spa.umn.edu with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1JuH80-000Bwg-Kg for freebsd-scsi@freebsd.org; Thu, 08 May 2008 20:10:28 -0500 Received: from peevish.spa.umn.edu (localhost.localdomain [127.0.0.1]) by peevish.spa.umn.edu (8.13.1/8.12.11) with ESMTP id m491AS1h027961 for ; Thu, 8 May 2008 20:10:28 -0500 Received: (from allan@localhost) by peevish.spa.umn.edu (8.13.1/8.13.1/Submit) id m491ASRc027960 for freebsd-scsi@freebsd.org; Thu, 8 May 2008 20:10:28 -0500 Date: Thu, 8 May 2008 20:10:28 -0500 From: Graham Allan To: freebsd-scsi@freebsd.org Message-ID: <20080509011028.GV25577@physics.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: Hang on boot in isp with QLA2342 after upgrading to 6.3 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, 09 May 2008 01:32:05 -0000 Hi, I've been trying to figure out a problem on a system which I just upgraded from FreeBSD 6.1 to 6.3. It's a Dell 1750 with a QLA2342 (isp2312) HBA, connected to an EMC DS-16B2 (aka Brocade 3800) switch, and from there to a couple of AC&NC Jetstor arrays. It's all been working fine like this for some time under 6.1. When I boot the system under 6.3, though I get a hang like this: isp0: Interrupting Mailbox Command (0x6f) Timeout (500000us) isp0: PLOGI 0x031a00 failed isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) isp0: isp_pdb_sync: isp_scan_fabric failed isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) isp0: isp_pdb_sync: isp_scan_fabric failed isp0: Mailbox Command 'SEND SNS' failed (COMMAND ERROR) isp0: isp_pdb_sync: isp_scan_fabric failed after which the system stays hung. I do have ispfw_load="YES" set (it reports loading F/W revision 3.3.19): isp0: port 0xdc00-0xdcff mem 0xfcf01000-0xfcf01fff irq 20 atdevice 4.0 on pci1 isp0: [GIANT-LOCKED] isp0: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.19 isp1: port 0xd800-0xd8ff mem 0xfcf00000-0xfcf00fff irq 21 atdevice 4.1 on pci1 isp1: [GIANT-LOCKED] isp1: Board Type 2312, Chip Revision 0x2, loaded F/W Revision 3.3.19 I initially suspected a hardware problem, but I've retested with a couple of different QLA2342 cards in a couple of different 1750 systems. I did find one or two interesting things though. 1) Reinstalling 6.1 has everything working again (as long as ispfw_load="YES" is set). 2) if, under 6.3, I connect the HBA directly to a storage device (eg a tape drive/loader) instead of the SAN switch, it works fine. So possibly something related to point-to-point mode rather than fabric? 3) If I connect one port of the HBA to the tape loader, and the other to the SAN switch, it also boots up successfully, although we get the same errors reported as above, without the hang... isp0: Interrupting Mailbox Command (0x6f) Timeout (500000us) isp0: PLOGI 0x031a00 failed isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) isp0: isp_pdb_sync: isp_scan_fabric failed isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) isp0: isp_pdb_sync: isp_scan_fabric failed isp0: Mailbox Command 'SEND SNS' failed (COMMAND ERROR) isp0: isp_pdb_sync: isp_scan_fabric failed sa0 at isp1 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-4 device sa0: 200.000MB/s transfers da0 at isp0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 200.000MB/s transfers, Tagged Queueing Enabled da0: 953MB (1952256 512 byte sectors: 64H 32S/T 953C) ... Finally I booted with "hint.isp.0.debug=0x1F" in /boot/device.hints, while connected only to the switch, and... unfortunately I wasn't able to capture the extensive output, but the final text was: isp0: target 496 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 497 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 498 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 499 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 500 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 501 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 502 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 503 lun 0 CAM status 0xa SCSI status 0x0 isp0: target 504 lun 0 CAM status 0xa SCSI status 0x0 I will work on hooking up a serial console so I can capture the entire output, though I'm also wondering if anyone might have some advice on what to try next at this point? Graham -- ------------------------------------------------------------------------- Graham Allan - I.T. Manager - allan@physics.umn.edu - (612) 624-5040 School of Physics and Astronomy - University of Minnesota ------------------------------------------------------------------------- From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 21:56:22 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BD6B106566B for ; Fri, 9 May 2008 21:56:22 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from florence.spa.umn.edu (florence.spa.umn.edu [128.101.220.10]) by mx1.freebsd.org (Postfix) with ESMTP id 726508FC0A for ; Fri, 9 May 2008 21:56:22 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from peevish.spa.umn.edu ([128.101.220.230]) by florence.spa.umn.edu with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1JuaZh-000Nfa-Tl for freebsd-scsi@freebsd.org; Fri, 09 May 2008 16:56:21 -0500 Received: from peevish.spa.umn.edu (localhost.localdomain [127.0.0.1]) by peevish.spa.umn.edu (8.13.1/8.12.11) with ESMTP id m49LuLck010903 for ; Fri, 9 May 2008 16:56:21 -0500 Received: (from allan@localhost) by peevish.spa.umn.edu (8.13.1/8.13.1/Submit) id m49LuLpF010902 for freebsd-scsi@freebsd.org; Fri, 9 May 2008 16:56:21 -0500 Date: Fri, 9 May 2008 16:56:21 -0500 From: Graham Allan To: freebsd-scsi@freebsd.org Message-ID: <20080509215621.GX25577@physics.umn.edu> References: <20080509011028.GV25577@physics.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080509011028.GV25577@physics.umn.edu> User-Agent: Mutt/1.5.9i Subject: Re: Hang on boot in isp with QLA2342 after upgrading to 6.3 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, 09 May 2008 21:56:22 -0000 On Thu, May 08, 2008 at 08:10:28PM -0500, Graham Allan wrote: > Hi, > > I've been trying to figure out a problem on a system which I just > upgraded from FreeBSD 6.1 to 6.3. It's a Dell 1750 with a QLA2342 > (isp2312) HBA, connected to an EMC DS-16B2 (aka Brocade 3800) switch, > and from there to a couple of AC&NC Jetstor arrays. It's all been > working fine like this for some time under 6.1. > > When I boot the system under 6.3, though I get a hang like this: > > isp0: Interrupting Mailbox Command (0x6f) Timeout (500000us) > isp0: PLOGI 0x031a00 failed > isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) > isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) > isp0: isp_pdb_sync: isp_scan_fabric failed > isp0: Interrupting Mailbox Command (0x6e) Timeout (10000000us) > isp0: Mailbox Command 'SEND SNS' failed (TIMEOUT) > isp0: isp_pdb_sync: isp_scan_fabric failed > isp0: Mailbox Command 'SEND SNS' failed (COMMAND ERROR) > isp0: isp_pdb_sync: isp_scan_fabric failed > > after which the system stays hung. I've done some more testing on this and am left with a headache because nothing makes sense! Would certainly be grateful if any fiber channel gurus might comment. I tested again with FreeBSD 7.0 and got the same result as above. Next I tried swapping components in and out of the SAN to see if different combinations have different results. These tests were with 7.0 since that was what I still had installed. The SAN switch has the following devices connected: 1) AC&NC Jetstor 416F 2) AC&NC Jetstor 516F 3) Alphaserver ES40, Tru64 5.1B-6, KGPSA-CA (Emulex) HBA 4) Dell 1750, (the system I'm writing about), Qlogic 2342 HBA 5) Dell 1750, Windows 2003, LSI 7202P HBA There's no zoning on the switch since all three servers connect to the two Jetstors. Access to the RAID volumes is controlled by host filters on the Jetstors. So I tested with different combinations of devices connected to the switch, with perplexing results: FreeBSD + 416F only - boots fine FreeBSD + 516F only - boots fine FreeBSD + 416F + 516F - boots fine FreeBSD + 416F + 516F + windows - boots fine FreeBSD + 416F + 516F + ES40 - hangs with the above error but, continuing... FreeBSD + 516F + ES40 - boots fine FreeBSD + 416F + ES40 - boots fine FreeBSD + 416F + 516F + ES40 - hangs again I can't make any sense of this... there are so many different systems involved that there's no way to know where the problem really lies. Although as it did work with FreeBSD 6.1, it feels to me like something is wrong in the newer isp driver, but I have no solid knowledge to base that on. Thanks for any ideas, Graham -- ------------------------------------------------------------------------- Graham Allan - I.T. Manager - allan@physics.umn.edu - (612) 624-5040 School of Physics and Astronomy - University of Minnesota ------------------------------------------------------------------------- From owner-freebsd-scsi@FreeBSD.ORG Sat May 10 04:41:33 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53F9C1065672 for ; Sat, 10 May 2008 04:41:33 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 14F068FC18 for ; Sat, 10 May 2008 04:41:32 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from ns1.feral.com (mjacob@ns1.feral.com [192.67.166.1]) by ns1.feral.com (8.14.2/8.14.2) with ESMTP id m4A4HvAk014325 for ; Fri, 9 May 2008 21:17:58 -0700 (PDT) (envelope-from lydianconcepts@gmail.com) Date: Fri, 9 May 2008 21:17:57 -0700 (PDT) From: lydianconcepts@gmail.com To: freebsd-scsi@freebsd.org Message-ID: <20080509211554.J14314@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (ns1.feral.com [192.67.166.1]); Fri, 09 May 2008 21:17:58 -0700 (PDT) Subject: updated freebsd-isp patches X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lydianconcepts@gmail.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2008 04:41:33 -0000 No particularily testing, but newer 2400 f/w and bunches of other stuff, including some n-port virtualization stuff. For whomever feels like integrating it into -current. ftp://ftp.feral.com/pub/isp/freebsd.isp.diffs MD5 (freebsd.isp.diffs) = f9aaa921ddb8982587088d703200686f