From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 10 11:10:09 2012 Return-Path: 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 53AB710656F4 for ; Mon, 10 Sep 2012 11:10:09 +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 39FF98FC08 for ; Mon, 10 Sep 2012 11:10:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8ABA9cH071633 for ; Mon, 10 Sep 2012 11:10:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8ABA7l9071240 for freebsd-scsi@FreeBSD.org; Mon, 10 Sep 2012 11:10:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Sep 2012 11:10:07 GMT Message-Id: <201209101110.q8ABA7l9071240@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, 10 Sep 2012 11:10:09 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/169976 scsi [cam] [patch] make scsi_da use sysctl values where app o kern/169974 scsi [cam] [patch] add Quirks for SSD that are 4k optimised o kern/169835 scsi [patch] remove some unused variables from scsi_da prob o kern/169801 scsi [cam] [patc] make changes to delete_method in scsi_da o kern/169403 scsi [cam] [patch] CAM layer, I/O starvation, no fairness o kern/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153514 scsi [cam] [panic] CAM related panic o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c s kern/149927 scsi [cam] hard drive not stopped before removing power dur o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 55 problems total. From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 13 00:58:20 2012 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 90984106566C for ; Thu, 13 Sep 2012 00:58:20 +0000 (UTC) (envelope-from 3qy9RUAoJDNYLAE.JA4C6J8E2AD.4GE7J663K5-K4KA7J663K5.GJ8@calendar-server.bounces.google.com) Received: from mail-iy0-f202.google.com (mail-iy0-f202.google.com [209.85.210.202]) by mx1.freebsd.org (Postfix) with ESMTP id 5156F8FC0A for ; Thu, 13 Sep 2012 00:58:19 +0000 (UTC) Received: by iahk25 with SMTP id k25so547321iah.1 for ; Wed, 12 Sep 2012 17:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:reply-to:sender:auto-submitted:message-id:date:subject :from:to:content-type; bh=liINtXvnFwnYbP0Yqsbir5Xqkd4hcmgHMRab9AogoHQ=; b=iLeuqK5+V8pV3rnMDCSEf0gCoXA5JvXVsZZLJvrZUKeU2maszqssAc4y7ejXAUSZEz 0RyrFEVPwU38PqCWDyqnqQHfkEhZK/uQEmq9rtrJYF5wwBAy13OfRIaIiGly61aPMESe eVi2al4dp/PWa6Vds0HfHLJsmpYF8K88jew0/08AJpCjFiIo1U86M9gmJh602K/ilzho B6dTgE6x9MPcWcwJSuePSofOajtH5s1HfRrgegMoQR/yz8Lvyh+Q75QHTjvDW55ZUiyK Aasx1oEu/NLCH0MbJtzirPnvvQjn7ExrwyBWtFj0b8x/IxBdHNYyEPmV7TgayJWmpzkK s7Kw== MIME-Version: 1.0 Received: by 10.182.44.74 with SMTP id c10mr18355obm.13.1347497899202; Wed, 12 Sep 2012 17:58:19 -0700 (PDT) Sender: Google Calendar Auto-Submitted: auto-generated Message-ID: Date: Thu, 13 Sep 2012 00:58:19 +0000 From: Tim Ricker To: "freebsd-scsi@freebsd.org" Content-Type: multipart/mixed; boundary=f46d044785e39e18d804c98acdcf X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Invitation: (No title) @ Wed Sep 12 7pm - 8pm (freebsd-scsi@freebsd.org) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tim Ricker List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 00:58:20 -0000 --f46d044785e39e18d804c98acdcf Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes Content-Transfer-Encoding: base64 WW91IGhhdmUgYmVlbiBpbnZpdGVkIHRvIHRoZSBmb2xsb3dpbmcgZXZlbnQuDQoNClRpdGxlOiAo Tm8gdGl0bGUpDQpXaGVuOiBXZWQgU2VwIDEyIDdwbSCWIDhwbSBNb3VudGFpbiBUaW1lDQpDYWxl bmRhcjogZnJlZWJzZC1zY3NpQGZyZWVic2Qub3JnDQpXaG86DQogICAgICogdGltLnJpY2tlckBn bWFpbC5jb20gLSBvcmdhbml6ZXINCiAgICAgKiBmcmVlYnNkLXNjc2lAZnJlZWJzZC5vcmcNCg0K RXZlbnQgZGV0YWlsczogIA0KaHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS9jYWxlbmRhci9ldmVudD9h Y3Rpb249VklFVyZlaWQ9YlhWdk0yRnVaM1p6T0dacWN6Tm1kVGd6WVdveGRIUTFjR3NnWm5KbFpX SnpaQzF6WTNOcFFHWnlaV1ZpYzJRdWIzSm4mdG9rPU1qQWpkR2x0TG5KcFkydGxja0JuYldGcGJD NWpiMjAwTW1Fek0yRXdNVFZrWVdObVlUQmlNRFk0T0RZMU0yTmhZMk16WWpSaE9EaG1ZbVpoT1RS bSZjdHo9QW1lcmljYS9EZW52ZXImaGw9ZW4NCg0KSW52aXRhdGlvbiBmcm9tIEdvb2dsZSBDYWxl bmRhcjogaHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS9jYWxlbmRhci8NCg0KWW91IGFyZSByZWNlaXZp bmcgdGhpcyBjb3VydGVzeSBlbWFpbCBhdCB0aGUgYWNjb3VudCAgDQpmcmVlYnNkLXNjc2lAZnJl ZWJzZC5vcmcgYmVjYXVzZSB5b3UgYXJlIGFuIGF0dGVuZGVlIG9mIHRoaXMgZXZlbnQuDQoNClRv IHN0b3AgcmVjZWl2aW5nIGZ1dHVyZSBub3RpZmljYXRpb25zIGZvciB0aGlzIGV2ZW50LCBkZWNs aW5lIHRoaXMgZXZlbnQuICANCkFsdGVybmF0aXZlbHkgeW91IGNhbiBzaWduIHVwIGZvciBhIEdv b2dsZSBhY2NvdW50IGF0ICANCmh0dHBzOi8vd3d3Lmdvb2dsZS5jb20vY2FsZW5kYXIvIGFuZCBj b250cm9sIHlvdXIgbm90aWZpY2F0aW9uIHNldHRpbmdzIGZvciAgDQp5b3VyIGVudGlyZSBjYWxl bmRhci4NCg== --f46d044785e39e18d804c98acdcf-- From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 13 00:58:25 2012 Return-Path: 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 B761F106566B for ; Thu, 13 Sep 2012 00:58:25 +0000 (UTC) (envelope-from tim.ricker@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C46F8FC12 for ; Thu, 13 Sep 2012 00:58:25 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3430736pbb.13 for ; Wed, 12 Sep 2012 17:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vxP6oTmO/fe+0d9ngfXwNoPLzwrlHxOrMEekBhXcNMg=; b=YFTlbvVOrikRVyAMcgXA/NGlOBpLb5nEdwmJm65vJEaxjdKKkdRfX+kStMjYBuZ1dr 7zjeEz9ZJIB7tShj40Rljzvi/uFlZlzbanb2WIBeA+bHLIEHK4mGhy14CeHpssB41cGw pc9UMsJ0AvVV/pUfGXeH8o057Sc93MgThaSyyEzR7HPkqnzXyG2WdmaH/WUYNU5qWsyC 1mW+hVz7d+5e90O37LekPisd5eprILFcVJGnYkkIA1Ah7AIAPeDSega5BGHtWDGIBLkc T2erMdRKAebfds9acQ27qSTI/xnmOoGZa6WMsA4djYt37ZcH4dpT16n9s+9aHHZleD4I QFsw== MIME-Version: 1.0 Received: by 10.68.190.8 with SMTP id gm8mr1775481pbc.74.1347497899375; Wed, 12 Sep 2012 17:58:19 -0700 (PDT) Received: by 10.68.36.4 with HTTP; Wed, 12 Sep 2012 17:58:19 -0700 (PDT) Date: Wed, 12 Sep 2012 18:58:19 -0600 Message-ID: From: Tim Ricker To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: (no subject) 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, 13 Sep 2012 00:58:25 -0000 (No title) *When* Wed, September 12, 7pm =96 8pm GMT-06:00 *Who* =95 Tim Ricker =95 freebsd-scsi@freebsd.org From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 13 01:30:04 2012 Return-Path: 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 CF5EA106566B for ; Thu, 13 Sep 2012 01:30:04 +0000 (UTC) (envelope-from tim.ricker@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A0C908FC08 for ; Thu, 13 Sep 2012 01:30:04 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so3461643pbb.13 for ; Wed, 12 Sep 2012 18:30:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=BE4yZh9f0T78eCoaJ7oPmoJURchI8fOh1cA7LjRh8IE=; b=nf+itI1gLi8gRMJDz1T5gjh+xrahHkrS2yQ2EbPZnw0axFwv9A/6BHMvVM34eHeZCw 6fgk6+Jb0fnhWeyfX/H/4Rqw6K3J+tMeiYX9mk4SnPTNS7eQvmbXreDqLTe6QK94AJ4P uOCikYahHJv93TISr6H2rxW4S6vGyoCaYPCVLZMeKuMgPCj6uMEWpnG4RtnmV+uCegE1 BfIhvkto6o7j7iuqa73b2Yw8m7V0NsDDqsZ+EJgF0QJySxwCS+OfUJSuoDfoSzYf2mor bwE9KKavtkjAzPEIh9R2RP3cekgOrPANnROn/g1DrWCbrKybNmaUwRcUAS+KmKiI23Rs iugQ== MIME-Version: 1.0 Received: by 10.68.190.8 with SMTP id gm8mr1937606pbc.74.1347499804188; Wed, 12 Sep 2012 18:30:04 -0700 (PDT) Received: by 10.68.36.4 with HTTP; Wed, 12 Sep 2012 18:30:04 -0700 (PDT) Date: Wed, 12 Sep 2012 19:30:04 -0600 Message-ID: From: Tim Ricker To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: smp_utils: command line utilities for SAS expanders 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, 13 Sep 2012 01:30:04 -0000 Ken, Will you show output of =93./smp_read_sgpio /dev/da5=94 ? At least, an output that I can see the gpio read. First I wanted to see if I could get similar to what you gave on the mailing list. I did. $ sudo smp_discover ses5 -b phy 0:S:attached:[500605b003fb1210:07 i(SSP+STP+SMP)] phy 1:S:attached:[500605b003fb1210:06 i(SSP+STP+SMP)] phy 2:S:attached:[500605b003fb1210:05 i(SSP+STP+SMP)] phy 3:S:attached:[500605b003fb1210:04 i(SSP+STP+SMP)] phy 12:T:attached:[50030480015c85ec:00 t(SATA)] phy 13:T:attached:[50030480015c85ed:00 t(SATA)] phy 14:T:attached:[50030480015c85ee:00 t(SATA)] phy 15:T:attached:[50030480015c85ef:00 t(SATA)] phy 16:T:attached:[50030480015c85f0:00 t(SATA)] phy 17:T:attached:[50030480015c85f1:00 t(SATA)] phy 18:T:attached:[50030480015c85f2:00 t(SATA)] phy 19:T:attached:[50030480015c85f3:00 t(SATA)] phy 20:T:attached:[50030480015c85f4:00 t(SATA)] phy 21:T:attached:[50030480015c85f5:00 t(SATA)] phy 22:T:attached:[50030480015c85f6:00 t(SATA)] phy 23:T:attached:[50030480015c85f7:00 t(SATA)] phy 28:D:attached:[50030480015c85fd:00 V i(SSP+SMP) t(SSP)] Second, pick a device number. $ sudo camcontrol smpphylist ses5 -q 12 0x50030480015c85ec (da114,pass120) 13 0x50030480015c85ed (da115,pass121) 14 0x50030480015c85ee (da116,pass122) 15 0x50030480015c85ef (da117,pass123) 16 0x50030480015c85f0 (da118,pass124) 17 0x50030480015c85f1 (da119,pass125) 18 0x50030480015c85f2 (da120,pass126) 19 0x50030480015c85f3 (da121,pass127) 20 0x50030480015c85f4 (da122,pass128) 21 0x50030480015c85f5 (da123,pass129) 22 0x50030480015c85f6 (da124,pass130) 23 0x50030480015c85f7 (da125,pass131) 28 0x50030480015c85fd (ses5,pass132) Next, I tried reading gpio. $ sudo smp_read_gpio da114 -vH Read GPIO register request: 40 02 00 00 01 00 00 00 00 00 00 00 00 41 02 01 00 00 00 00 00 Exit status 1 indicates error detected And, for the fun of it. $ sudo smp_read_gpio ses5 -vH Read GPIO register request: 40 02 00 00 01 00 00 00 00 00 00 00 00 41 02 01 00 00 00 00 00 Exit status 1 indicates error detected ~ Tim R. From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 13 13:04:29 2012 Return-Path: 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 A759E1065670 for ; Thu, 13 Sep 2012 13:04:29 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 32C128FC0C for ; Thu, 13 Sep 2012 13:04:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id E5CD12041B0; Thu, 13 Sep 2012 14:55:27 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEip1YxTPTWY; Thu, 13 Sep 2012 14:55:27 +0200 (CEST) Received: from [82.134.31.171] (unknown [82.134.31.171]) by smtp.infotech.no (Postfix) with ESMTPA id 9E57020416A; Thu, 13 Sep 2012 14:55:27 +0200 (CEST) Message-ID: <5051D7BF.3090809@interlog.com> Date: Thu, 13 Sep 2012 14:55:27 +0200 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Tim Ricker References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-scsi@freebsd.org Subject: Re: smp_utils: command line utilities for SAS expanders X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 13:04:29 -0000 On 12-09-13 03:30 AM, Tim Ricker wrote: > Ken, > > Will you show output of “./smp_read_sgpio /dev/da5” ? > At least, an output that I can see the gpio read. > > First I wanted to see if I could get similar to what you gave on the > mailing list. I did. > > $ sudo smp_discover ses5 -b > phy 0:S:attached:[500605b003fb1210:07 i(SSP+STP+SMP)] > phy 1:S:attached:[500605b003fb1210:06 i(SSP+STP+SMP)] > phy 2:S:attached:[500605b003fb1210:05 i(SSP+STP+SMP)] > phy 3:S:attached:[500605b003fb1210:04 i(SSP+STP+SMP)] > phy 12:T:attached:[50030480015c85ec:00 t(SATA)] > phy 13:T:attached:[50030480015c85ed:00 t(SATA)] > phy 14:T:attached:[50030480015c85ee:00 t(SATA)] > phy 15:T:attached:[50030480015c85ef:00 t(SATA)] > phy 16:T:attached:[50030480015c85f0:00 t(SATA)] > phy 17:T:attached:[50030480015c85f1:00 t(SATA)] > phy 18:T:attached:[50030480015c85f2:00 t(SATA)] > phy 19:T:attached:[50030480015c85f3:00 t(SATA)] > phy 20:T:attached:[50030480015c85f4:00 t(SATA)] > phy 21:T:attached:[50030480015c85f5:00 t(SATA)] > phy 22:T:attached:[50030480015c85f6:00 t(SATA)] > phy 23:T:attached:[50030480015c85f7:00 t(SATA)] > phy 28:D:attached:[50030480015c85fd:00 V i(SSP+SMP) t(SSP)] > > Second, pick a device number. > > $ sudo camcontrol smpphylist ses5 -q > 12 0x50030480015c85ec (da114,pass120) > 13 0x50030480015c85ed (da115,pass121) > 14 0x50030480015c85ee (da116,pass122) > 15 0x50030480015c85ef (da117,pass123) > 16 0x50030480015c85f0 (da118,pass124) > 17 0x50030480015c85f1 (da119,pass125) > 18 0x50030480015c85f2 (da120,pass126) > 19 0x50030480015c85f3 (da121,pass127) > 20 0x50030480015c85f4 (da122,pass128) > 21 0x50030480015c85f5 (da123,pass129) > 22 0x50030480015c85f6 (da124,pass130) > 23 0x50030480015c85f7 (da125,pass131) > 28 0x50030480015c85fd (ses5,pass132) > > Next, I tried reading gpio. > > $ sudo smp_read_gpio da114 -vH > Read GPIO register request: 40 02 00 00 01 00 00 00 00 00 00 00 > 00 41 02 01 00 00 00 00 00 > Exit status 1 indicates error detected Tim, I'm the author of smp_utils. Could you add a few more '-v' options (e.g. '-vvvH' instead of '-vH' in the above invocation) so we can see what error was detected. Doug Gilbert > And, for the fun of it. > > $ sudo smp_read_gpio ses5 -vH > Read GPIO register request: 40 02 00 00 01 00 00 00 00 00 00 00 > 00 41 02 01 00 00 00 00 00 > Exit status 1 indicates error detected > > ~ Tim R. From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 14 17:09:27 2012 Return-Path: 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 233D6106564A for ; Fri, 14 Sep 2012 17:09:27 +0000 (UTC) (envelope-from mikea@mikea.ath.cx) Received: from mikea.ath.cx (mikea.ath.cx [70.164.65.62]) by mx1.freebsd.org (Postfix) with ESMTP id DBA6D8FC08 for ; Fri, 14 Sep 2012 17:09:26 +0000 (UTC) Received: from mikea.ath.cx (localhost [127.0.0.1]) by mikea.ath.cx (8.14.5/8.14.5) with ESMTP id q8EGk3KJ039160 for ; Fri, 14 Sep 2012 11:46:04 -0500 (CDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.14.5/8.14.5/Submit) id q8EGk32Y039159 for freebsd-scsi@freebsd.org; Fri, 14 Sep 2012 11:46:03 -0500 (CDT) (envelope-from mikea) Date: Fri, 14 Sep 2012 11:46:03 -0500 From: Mike A To: freebsd-scsi@freebsd.org Message-ID: <20120914164603.GA34637@mikea.ath.cx> References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> <201208290818.20990.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201208290818.20990.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 14 Sep 2012 17:09:27 -0000 On Wed, Aug 29, 2012 at 08:18:20AM -0400, John Baldwin wrote: > Humm, that is bizarre. All the early bootstrap code just relies on the BIOS > to perform disk I/O, etc. Can you PXE boot these machines? That might be a > way to get the CD out of the picture. I haven't seen any machines with your > symptoms. At the least, if a machine does have a problem with the boot process > due to a bug or some such, it is consistent in having the problem every time, > not suddenly failing after working. > > Also, to be honest, the original NMI in itself is a bit odd. If you are having > these problems now I do wonder if there isn't an underlying hardware issue. > Regardless, I think netbooting would be a good thing to look to get the CD/DVD > bit out of the way. All the stars finally moved to the right places, and I was able to try booting from a 9.1 amd64 memstick made from FreeBSD-9.1-RC1-amd64-memstick.img. That failed, both without and with boot loader hints. I had a movie camera running to catch the console message traffic. The last normal messages on the screen have to do with device mfi0. Here is the last screenfull: class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer==0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=7 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 16 messages in map 0x14 map[10]: type I/O Port, range 32, base 0x3000, size 8, enabled pcib3: allocated I/O port range (0x3000-0x30ff) for rid 10 of pci0:22:0:0 map[14]: type Memory, range 64, base 0xc5d40000, size 14, enabled pcib3: allocated memory range (0xc5d40000-0xcd43fff) for rid 14 of pci0:22:0:0 map[1c]: type Memory, range 64, base 0xc5d00000, size 18, enabled pcib3: allocated memory range (0xc5d00000-0xc5d3ffff) for rid 1c of pci0:22:0:0 pcib3: matched entry for 22.0.INTA pcib3: slot 0 INTA hardwired to IRQ 34 mfi0: port 0x3000-0x30ff mem 0xc5d40000-0xcfd43fff,0xc5d00000-0xc5 d3ffff irq 34 at device 0.0 on pci22 mfi0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 264 to local APIC 0 vector 59 mfi0: using IRQ 264 for MSI mfi0: Using MSI mfi0: Megaraid SAS driver Ver 4.23 mfi0: MaxCmd = 3f0 MaxSgl = 46 state=b75003f0 mfi0: Max fw cmds= 1000, sizing driver pool to 128 After this, the screen goes blank, then to "system initializing" on the very bottom line, which indicates that the system has been reset. The previous screen updates so quickly that lines are overlaid on the video from my camera. I think I can get a high-speed camera; the training video people are next door. I can download and boot a Linux system to get the PCI information for you, if that will get us any farther forward, but that will require more time. Please advise. Thanks again for the help so far. I *will* get this critter going. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 02:24:37 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id A6DA0106566C; Sat, 15 Sep 2012 02:24:37 +0000 (UTC) Date: Sat, 15 Sep 2012 02:24:37 +0000 From: John To: FreeBSD iSCSI Message-ID: <20120915022437.GA90210@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 02:24:37 -0000 Hi Folks, I've been poking around and can't seem to find a way to reset and hopefully acquire access to a disk device in an enclosure. For instance: FreeBSD 9.1-PRERELEASE # camcontrol smpphylist ses4 37 PHYs: PHY Attached SAS Address 0 0x5000039368233602 (pass105,da98) 1 0x5000039368238e3e (pass106,da99) 2 0x500003936823bca2 (pass107,da100) 3 0x500003936819507e (pass108,da101) 4 0x5000039368197d5a (pass109,da102) 5 0x5000039368197c6e (pass110,da103) 6 0x500003936818770e (pass111,da104) 7 0x5000039368238eba (pass112,da105) 8 0x5000039368232f42 (pass113,da106) 9 0x0000000000000000 10 0x500003936813c31e 11 0x5000039368233892 (pass114,da107) 12 0x500003936813c2ca (pass115,da108) ... Note, bay/slot 10 has a listed device address. If I were to pull the drive and re-insert it, it would show up (as da390 in this case). The above is after a fresh reboot. Note da106 to da107 skipping slot 10 (slot 9 is empty). The smp utils provide a similar view: # smp_discover /dev/ses4 phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps ... The address of slot 10 matches. There is a disk in the slot - just isn't recognized and attached. Back to the basic question. How can I issue a command to the enclosure to force a re-initialization of the device to recover it without having to physically pull & insert it. Even if the device numbers are not sequential, I need access to the drive... Thoughts? Thanks, John From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 02:45:21 2012 Return-Path: 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 5659C106564A; Sat, 15 Sep 2012 02:45:21 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 039A48FC14; Sat, 15 Sep 2012 02:45:20 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q8F2XTj4056661; Fri, 14 Sep 2012 20:33:29 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q8F2XT70056660; Fri, 14 Sep 2012 20:33:29 -0600 (MDT) (envelope-from ken) Date: Fri, 14 Sep 2012 20:33:29 -0600 From: "Kenneth D. Merry" To: John Message-ID: <20120915023329.GA55292@nargothrond.kdm.org> References: <20120915022437.GA90210@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120915022437.GA90210@FreeBSD.org> User-Agent: Mutt/1.4.2i Cc: FreeBSD iSCSI Subject: Re: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 02:45:21 -0000 On Sat, Sep 15, 2012 at 02:24:37 +0000, John wrote: > Hi Folks, > > I've been poking around and can't seem to find a way to reset and > hopefully acquire access to a disk device in an enclosure. For instance: > > FreeBSD 9.1-PRERELEASE > > # camcontrol smpphylist ses4 > 37 PHYs: > PHY Attached SAS Address > 0 0x5000039368233602 (pass105,da98) > 1 0x5000039368238e3e (pass106,da99) > 2 0x500003936823bca2 (pass107,da100) > 3 0x500003936819507e (pass108,da101) > 4 0x5000039368197d5a (pass109,da102) > 5 0x5000039368197c6e (pass110,da103) > 6 0x500003936818770e (pass111,da104) > 7 0x5000039368238eba (pass112,da105) > 8 0x5000039368232f42 (pass113,da106) > 9 0x0000000000000000 > 10 0x500003936813c31e > 11 0x5000039368233892 (pass114,da107) > 12 0x500003936813c2ca (pass115,da108) > ... > > Note, bay/slot 10 has a listed device address. If I were to pull the > drive and re-insert it, it would show up (as da390 in this case). > The above is after a fresh reboot. Note da106 to da107 skipping > slot 10 (slot 9 is empty). > > The smp utils provide a similar view: > > # smp_discover /dev/ses4 > phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps > phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps > phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps > phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps > phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps > phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps > phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps > phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps > phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps > phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps > phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps > phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps > ... > > The address of slot 10 matches. There is a disk in the slot - just > isn't recognized and attached. > > Back to the basic question. How can I issue a command to the enclosure > to force a re-initialization of the device to recover it without > having to physically pull & insert it. Even if the device numbers > are not sequential, I need access to the drive... You can try sending a link reset: camcontrol smppc ses4 -p 10 -o linkreset It may or may not work. You can also try disabling the PHY (-o disable) and then sending a link reset to re-enable the link. You can also try a hard reset (-o hardreset) Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 03:13:05 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 318A0106566B; Sat, 15 Sep 2012 03:13:05 +0000 (UTC) Date: Sat, 15 Sep 2012 03:13:05 +0000 From: John To: FreeBSD iSCSI Message-ID: <20120915031305.GA97685@FreeBSD.org> References: <20120915022437.GA90210@FreeBSD.org> <20120915023329.GA55292@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120915023329.GA55292@nargothrond.kdm.org> User-Agent: Mutt/1.4.2.1i Cc: "Kenneth D. Merry" Subject: Re: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 03:13:05 -0000 ----- Kenneth D. Merry's Original Message ----- > On Sat, Sep 15, 2012 at 02:24:37 +0000, John wrote: > > Hi Folks, > > > > I've been poking around and can't seem to find a way to reset and > > hopefully acquire access to a disk device in an enclosure. For instance: > > > > FreeBSD 9.1-PRERELEASE > > > > # camcontrol smpphylist ses4 > > 37 PHYs: > > PHY Attached SAS Address > > 0 0x5000039368233602 (pass105,da98) > > 1 0x5000039368238e3e (pass106,da99) > > 2 0x500003936823bca2 (pass107,da100) > > 3 0x500003936819507e (pass108,da101) > > 4 0x5000039368197d5a (pass109,da102) > > 5 0x5000039368197c6e (pass110,da103) > > 6 0x500003936818770e (pass111,da104) > > 7 0x5000039368238eba (pass112,da105) > > 8 0x5000039368232f42 (pass113,da106) > > 9 0x0000000000000000 > > 10 0x500003936813c31e > > 11 0x5000039368233892 (pass114,da107) > > 12 0x500003936813c2ca (pass115,da108) > > ... > > > > Note, bay/slot 10 has a listed device address. If I were to pull the > > drive and re-insert it, it would show up (as da390 in this case). > > The above is after a fresh reboot. Note da106 to da107 skipping > > slot 10 (slot 9 is empty). > > > > The smp utils provide a similar view: > > > > # smp_discover /dev/ses4 > > phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps > > phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps > > phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps > > phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps > > phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps > > phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps > > phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps > > phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps > > phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps > > phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps > > phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps > > phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps > > ... > > > > The address of slot 10 matches. There is a disk in the slot - just > > isn't recognized and attached. > > > > Back to the basic question. How can I issue a command to the enclosure > > to force a re-initialization of the device to recover it without > > having to physically pull & insert it. Even if the device numbers > > are not sequential, I need access to the drive... > > You can try sending a link reset: > > camcontrol smppc ses4 -p 10 -o linkreset > > It may or may not work. You can also try disabling the PHY (-o disable) > and then sending a link reset to re-enable the link. You can also try a > hard reset (-o hardreset) Hi Ken, Well, I hadn't tried to actually disable the device. That did bring some reaction: # camcontrol smppc ses4 -p 10 -o disable # camcontrol smpphylist ses4 37 PHYs: PHY Attached SAS Address 0 0x5000039368233602 (pass105,da98) .... 8 0x5000039368232f42 (pass113,da106) 9 0x0000000000000000 10 0x0000000000000000 11 0x5000039368233892 (pass114,da107) ... The device is gone. # camcontrol smppc ses4 -p 10 -o hardreset root@vprzfs01p:/root # camcontrol smpphylist ses4 37 PHYs: PHY Attached SAS Address 0 0x5000039368233602 (pass105,da98) .... 8 0x5000039368232f42 (pass113,da106) 9 0x0000000000000000 10 0x500003936813c31e 11 0x5000039368233892 (pass114,da107) ... The device is back, but not attached - This msg: kernel: mps1: mpssas_alloc_tm freezing simq kernel: mps1: mpssas_remove_complete on handle 0x0069, IOCStatus= 0x0 kernel: mps1: mpssas_free_tm releasing simq kernel: _mapping_add_new_device: failed to add the device with handle 0x0069 to persistent table because there is no free space available - entry 0 >From a debug statement in the driver: MaxPersistentEntries == 128, but I have more than 128 devices per LSI card and they normally all show up - though I do get a bunch of the above messages in dmesg.. Thoughts? -John > > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 03:28:33 2012 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 DFDAD1065673; Sat, 15 Sep 2012 03:28:33 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 790948FC12; Sat, 15 Sep 2012 03:28:26 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q8F3SQLw063537; Fri, 14 Sep 2012 21:28:26 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q8F3SQQT063536; Fri, 14 Sep 2012 21:28:26 -0600 (MDT) (envelope-from ken) Date: Fri, 14 Sep 2012 21:28:26 -0600 From: "Kenneth D. Merry" To: John Message-ID: <20120915032826.GA63349@nargothrond.kdm.org> References: <20120915022437.GA90210@FreeBSD.org> <20120915023329.GA55292@nargothrond.kdm.org> <20120915031305.GA97685@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120915031305.GA97685@FreeBSD.org> User-Agent: Mutt/1.4.2i Cc: FreeBSD iSCSI Subject: Re: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 03:28:34 -0000 On Sat, Sep 15, 2012 at 03:13:05 +0000, John wrote: > ----- Kenneth D. Merry's Original Message ----- > > On Sat, Sep 15, 2012 at 02:24:37 +0000, John wrote: > > > Hi Folks, > > > > > > I've been poking around and can't seem to find a way to reset and > > > hopefully acquire access to a disk device in an enclosure. For instance: > > > > > > FreeBSD 9.1-PRERELEASE > > > > > > # camcontrol smpphylist ses4 > > > 37 PHYs: > > > PHY Attached SAS Address > > > 0 0x5000039368233602 (pass105,da98) > > > 1 0x5000039368238e3e (pass106,da99) > > > 2 0x500003936823bca2 (pass107,da100) > > > 3 0x500003936819507e (pass108,da101) > > > 4 0x5000039368197d5a (pass109,da102) > > > 5 0x5000039368197c6e (pass110,da103) > > > 6 0x500003936818770e (pass111,da104) > > > 7 0x5000039368238eba (pass112,da105) > > > 8 0x5000039368232f42 (pass113,da106) > > > 9 0x0000000000000000 > > > 10 0x500003936813c31e > > > 11 0x5000039368233892 (pass114,da107) > > > 12 0x500003936813c2ca (pass115,da108) > > > ... > > > > > > Note, bay/slot 10 has a listed device address. If I were to pull the > > > drive and re-insert it, it would show up (as da390 in this case). > > > The above is after a fresh reboot. Note da106 to da107 skipping > > > slot 10 (slot 9 is empty). > > > > > > The smp utils provide a similar view: > > > > > > # smp_discover /dev/ses4 > > > phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps > > > phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps > > > phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps > > > phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps > > > phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps > > > phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps > > > phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps > > > phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps > > > phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps > > > phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps > > > phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps > > > phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps > > > ... > > > > > > The address of slot 10 matches. There is a disk in the slot - just > > > isn't recognized and attached. > > > > > > Back to the basic question. How can I issue a command to the enclosure > > > to force a re-initialization of the device to recover it without > > > having to physically pull & insert it. Even if the device numbers > > > are not sequential, I need access to the drive... > > > > You can try sending a link reset: > > > > camcontrol smppc ses4 -p 10 -o linkreset > > > > It may or may not work. You can also try disabling the PHY (-o disable) > > and then sending a link reset to re-enable the link. You can also try a > > hard reset (-o hardreset) > > Hi Ken, > > Well, I hadn't tried to actually disable the device. That did bring some > reaction: > > # camcontrol smppc ses4 -p 10 -o disable > # camcontrol smpphylist ses4 > 37 PHYs: > PHY Attached SAS Address > 0 0x5000039368233602 (pass105,da98) > .... > 8 0x5000039368232f42 (pass113,da106) > 9 0x0000000000000000 > 10 0x0000000000000000 > 11 0x5000039368233892 (pass114,da107) > ... > > The device is gone. > > # camcontrol smppc ses4 -p 10 -o hardreset > root@vprzfs01p:/root # camcontrol smpphylist ses4 > 37 PHYs: > PHY Attached SAS Address > 0 0x5000039368233602 (pass105,da98) > .... > 8 0x5000039368232f42 (pass113,da106) > 9 0x0000000000000000 > 10 0x500003936813c31e > 11 0x5000039368233892 (pass114,da107) > ... > > The device is back, but not attached - This msg: > > kernel: mps1: mpssas_alloc_tm freezing simq > kernel: mps1: mpssas_remove_complete on handle 0x0069, IOCStatus= 0x0 > kernel: mps1: mpssas_free_tm releasing simq > kernel: _mapping_add_new_device: failed to add the device with handle 0x0069 to persistent table because there is no free space available - entry 0 That message is harmless, it won't prevent the drive from attaching. > >From a debug statement in the driver: MaxPersistentEntries == 128, but I > have more than 128 devices per LSI card and they normally all show up - > though I do get a bunch of the above messages in dmesg.. You might try turning on some of the debugging in the mps(4) driver and disabling and resetting the link again. Try: sysctl -w dev.mps.0.debug_level=0xf You might get a lot of output, so be prepared to reset it back to 4: sysctl -w dev.mps.0.debug_level=4 Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 04:09:07 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.ORG Received: by hub.freebsd.org (Postfix, from userid 821) id 615B21065670; Sat, 15 Sep 2012 04:09:07 +0000 (UTC) Date: Sat, 15 Sep 2012 04:09:07 +0000 From: John To: FreeBSD iSCSI Message-ID: <20120915040907.GA5458@FreeBSD.org> References: <20120915022437.GA90210@FreeBSD.org> <20120915023329.GA55292@nargothrond.kdm.org> <20120915031305.GA97685@FreeBSD.org> <20120915032826.GA63349@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120915032826.GA63349@nargothrond.kdm.org> User-Agent: Mutt/1.4.2.1i Cc: "Kenneth D. Merry" Subject: Re: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 04:09:07 -0000 ----- Kenneth D. Merry's Original Message ----- > On Sat, Sep 15, 2012 at 03:13:05 +0000, John wrote: > > ----- Kenneth D. Merry's Original Message ----- > > > On Sat, Sep 15, 2012 at 02:24:37 +0000, John wrote: > > > > Hi Folks, > > > > > > > > I've been poking around and can't seem to find a way to reset and > > > > hopefully acquire access to a disk device in an enclosure. For instance: > > > > > > > > FreeBSD 9.1-PRERELEASE > > > > > > > > # camcontrol smpphylist ses4 > > > > 37 PHYs: > > > > PHY Attached SAS Address > > > > 0 0x5000039368233602 (pass105,da98) > > > > 1 0x5000039368238e3e (pass106,da99) > > > > 2 0x500003936823bca2 (pass107,da100) > > > > 3 0x500003936819507e (pass108,da101) > > > > 4 0x5000039368197d5a (pass109,da102) > > > > 5 0x5000039368197c6e (pass110,da103) > > > > 6 0x500003936818770e (pass111,da104) > > > > 7 0x5000039368238eba (pass112,da105) > > > > 8 0x5000039368232f42 (pass113,da106) > > > > 9 0x0000000000000000 > > > > 10 0x500003936813c31e > > > > 11 0x5000039368233892 (pass114,da107) > > > > 12 0x500003936813c2ca (pass115,da108) > > > > ... > > > > > > > > Note, bay/slot 10 has a listed device address. If I were to pull the > > > > drive and re-insert it, it would show up (as da390 in this case). > > > > The above is after a fresh reboot. Note da106 to da107 skipping > > > > slot 10 (slot 9 is empty). > > > > > > > > The smp utils provide a similar view: > > > > > > > > # smp_discover /dev/ses4 > > > > phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps > > > > phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps > > > > phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps > > > > phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps > > > > phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps > > > > phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps > > > > phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps > > > > phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps > > > > phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps > > > > phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps > > > > phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps > > > > phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps > > > > ... > > > > > > > > The address of slot 10 matches. There is a disk in the slot - just > > > > isn't recognized and attached. > > > > > > > > Back to the basic question. How can I issue a command to the enclosure > > > > to force a re-initialization of the device to recover it without > > > > having to physically pull & insert it. Even if the device numbers > > > > are not sequential, I need access to the drive... > > > > > > You can try sending a link reset: > > > > > > camcontrol smppc ses4 -p 10 -o linkreset > > > > > > It may or may not work. You can also try disabling the PHY (-o disable) > > > and then sending a link reset to re-enable the link. You can also try a > > > hard reset (-o hardreset) > > > > Hi Ken, > > > > Well, I hadn't tried to actually disable the device. That did bring some > > reaction: > > > > # camcontrol smppc ses4 -p 10 -o disable > > # camcontrol smpphylist ses4 > > 37 PHYs: > > PHY Attached SAS Address > > 0 0x5000039368233602 (pass105,da98) > > .... > > 8 0x5000039368232f42 (pass113,da106) > > 9 0x0000000000000000 > > 10 0x0000000000000000 > > 11 0x5000039368233892 (pass114,da107) > > ... > > > > The device is gone. > > > > # camcontrol smppc ses4 -p 10 -o hardreset > > root@vprzfs01p:/root # camcontrol smpphylist ses4 > > 37 PHYs: > > PHY Attached SAS Address > > 0 0x5000039368233602 (pass105,da98) > > .... > > 8 0x5000039368232f42 (pass113,da106) > > 9 0x0000000000000000 > > 10 0x500003936813c31e > > 11 0x5000039368233892 (pass114,da107) > > ... > > > > The device is back, but not attached - This msg: > > > > kernel: mps1: mpssas_alloc_tm freezing simq > > kernel: mps1: mpssas_remove_complete on handle 0x0069, IOCStatus= 0x0 > > kernel: mps1: mpssas_free_tm releasing simq > > kernel: _mapping_add_new_device: failed to add the device with handle 0x0069 to persistent table because there is no free space available - entry 0 > > That message is harmless, it won't prevent the drive from attaching. > > > >From a debug statement in the driver: MaxPersistentEntries == 128, but I > > have more than 128 devices per LSI card and they normally all show up - > > though I do get a bunch of the above messages in dmesg.. > > You might try turning on some of the debugging in the mps(4) driver and > disabling and resetting the link again. > > Try: > > sysctl -w dev.mps.0.debug_level=0xf > > You might get a lot of output, so be prepared to reset it back to 4: > > sysctl -w dev.mps.0.debug_level=4 Hi Ken, I don't see anything obvious. Hopefully you're more familair with the code and have better eyes than I do... Here's everything from messages after the -o disable. There are some "unknown/unhandled"s showing up. kernel: mpssas_action func 0x4 kernel: mpssas_action func 0x15 kernel: mpssas_action func 0x91b kernel: sending SMP request to SAS address 0x5001438014a0a0bf kernel: mps_enqueue_request SMID 689 cm 0xffffff80013cd2c8 ccb 0 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 214 kernel: mps_complete_command cm 0xffffff80013cd2c8 calling cm_complete 0xffffffff805da470 data 0xfffffe002c7ca000 reply 0xffffff96f9f31800 kernel: SMP request to SAS address 0x5001438014a0a0bf completed successfully kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 215 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 215 kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 1 kernel: Discovery Started kernel: 5 kernel: 0 kernel: mpssas_evt_handler kernel: kernel: 7 kernel: 0 kernel: SasDeviceStatusChange (0xf) kernel: 0x78 kernel: 0xffff kernel: Internal Device Reset kernel: 0x0 kernel: 0x0 kernel: 0x78 kernel: 0x500003936811feae kernel: mpssas_evt_handler kernel: kernel: 25 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 22 kernel: 10 kernel: Responding (0x3) kernel: 5 kernel: 0x0078 kernel: LinkRate Unknown (0xa) kernel: TargetMissing kernel: 0x0079 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0089 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008e kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008f kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0090 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0093 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: mpssas_evt_handler kernel: kernel: 7 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 4 kernel: 32 kernel: Responding (0x3) kernel: 5 kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 7 kernel: 0 kernel: SasDeviceStatusChange (0xf) kernel: 0x78 kernel: 0xffff kernel: Cmp Internal Device Reset kernel: 0x0 kernel: 0x0 kernel: 0x78 kernel: 0x500003936811feae kernel: mpssas_evt_handler kernel: kernel: 6 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x9 kernel: 0x94 kernel: 37 kernel: 3 kernel: 33 kernel: Responding (0x3) kernel: 5 kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 0 kernel: Discovery Complete kernel: 5 kernel: 0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 222 kernel: mps_intr_msi kernel: [16] kernel: SAS discovery start event kernel: [16] kernel: [f] kernel: Unhandled event 0xF kernel: [f] kernel: [1c] kernel: [1c] kernel: [1c] kernel: [1c] kernel: [f] kernel: Unhandled event 0xF kernel: [f] kernel: [1c] kernel: [1c] kernel: [16] kernel: SAS discovery stop event kernel: mpssas_discovery_end kernel: [16] kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 222 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 222 kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 1 kernel: Discovery Started kernel: 5 kernel: 0 kernel: mpssas_evt_handler kernel: kernel: 25 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 22 kernel: 10 kernel: Responding (0x3) kernel: 5 kernel: 0x0078 kernel: LinkRate Unknown (0x0) kernel: TargetGone kernel: 0x0079 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0089 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008e kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008f kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0090 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0093 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: mpssas_evt_handler kernel: kernel: 7 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 4 kernel: 32 kernel: Responding (0x3) kernel: 5 kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 2 kernel: Discovery Complete kernel: 5 kernel: 0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 226 kernel: mps_intr_msi kernel: [16] kernel: SAS discovery start event kernel: [16] kernel: [1c] kernel: mpssas_prepare_remove kernel: mpssas_alloc_tm freezing simq kernel: mpssas_alloc_tm tm_count 1 kernel: mpssas_rescan_target targetid 255 kernel: mpssas_rescan kernel: kernel: mps_enqueue_request SMID 2 cm 0xffffff8001396290 ccb 0 kernel: [1c] kernel: [1c] kernel: [1c] kernel: [16] kernel: SAS discovery stop event kernel: mpssas_discovery_end kernel: [16] kernel: mpssas_action func 0x4 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 226 kernel: mps_complete_command cm 0xffffff8001396290 calling cm_complete 0xffffffff805d9550 data 0x78 reply 0xffffff96f9f31e00 kernel: mpssas_remove_device kernel: Reset aborted 0 commands kernel: mps_enqueue_request SMID 2 cm 0xffffff8001396290 ccb 0 kernel: clearing target 255 handle 0x0078 kernel: mps_complete_command cm 0xffffff8001396290 calling cm_complete 0xffffffff805d5500 data 0x78 reply 0xffffff96f9f31e80 kernel: mpssas_remove_complete kernel: mpssas_remove_complete on handle 0x0078, IOCStatus= 0x0 kernel: mpssas_free_tm releasing simq kernel: mpssas_free_tm tm_count 0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 228 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 228 kernel: after disable kernel: mpssas_action func 0x4 kernel: mpssas_action func 0x15 kernel: mpssas_action func 0x91b kernel: sending SMP request to SAS address 0x5001438014a0a0bf kernel: mps_enqueue_request SMID 707 cm 0xffffff80013ce9d8 ccb 0 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 228 kernel: mps_complete_command cm 0xffffff80013ce9d8 calling cm_complete 0xffffffff805da470 data 0xfffffe002c7ca000 reply 0xffffff96f9f31f00 kernel: SMP request to SAS address 0x5001438014a0a0bf completed successfully kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 229 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 229 kernel: mpssas_evt_handler kernel: kernel: 1 kernel: 0 kernel: SasBroadcastPrimitive (0x17) kernel: 0x0 kernel: mpssas_evt_handler kernel: kernel: 1 kernel: 0 kernel: SasBroadcastPrimitive (0x17) kernel: 0x0 kernel: mpssas_evt_handler kernel: kernel: 1 kernel: 0 kernel: SasBroadcastPrimitive (0x17) kernel: 0x0 kernel: mpssas_evt_handler kernel: kernel: 1 kernel: 0 kernel: SasBroadcastPrimitive (0x17) kernel: 0x0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 233 kernel: mps_intr_msi kernel: [17] kernel: Unhandled event 0x17 kernel: [17] kernel: [17] kernel: Unhandled event 0x17 kernel: [17] kernel: [17] kernel: Unhandled event 0x17 kernel: [17] kernel: [17] kernel: Unhandled event 0x17 kernel: [17] kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 233 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 233 kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 1 kernel: Discovery Started kernel: 5 kernel: 0 kernel: mpssas_evt_handler kernel: kernel: 25 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 22 kernel: 10 kernel: Responding (0x3) kernel: 5 kernel: 0x0078 kernel: 6.0Gbps (0xa0) kernel: NewTargetAdded kernel: 0x0079 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x007d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0089 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008a kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008b kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008c kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008d kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008e kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x008f kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0090 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0093 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0006 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: mpssas_evt_handler kernel: kernel: 7 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 4 kernel: 32 kernel: Responding (0x3) kernel: 5 kernel: 0x0094 kernel: 6.0Gbps (0xa0) kernel: PHYLinkStatusUnchanged kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 6 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x9 kernel: 0x94 kernel: 37 kernel: 3 kernel: 33 kernel: Responding (0x3) kernel: 5 kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 2 kernel: Discovery Complete kernel: 5 kernel: 0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 238 kernel: mps_intr_msi kernel: [16] kernel: SAS discovery start event kernel: [16] kernel: [1c] kernel: mps_config_get_sas_device_pg0 kernel: mps_enqueue_request SMID 701 cm 0xffffff80013ce228 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 238 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 239 kernel: mps_enqueue_request SMID 693 cm 0xffffff80013cd7e8 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 239 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 240 kernel: failed to add the device with handle 0x0078 to persistent table because there is no free space available - entry 0 kernel: mps_config_get_sas_device_pg0 kernel: mps_enqueue_request SMID 699 cm 0xffffff80013cdf98 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 240 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 241 kernel: mps_enqueue_request SMID 703 cm 0xffffff80013ce4b8 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 241 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 242 kernel: mps_config_get_sas_device_pg0 kernel: mps_enqueue_request SMID 571 cm 0xffffff80013c3b98 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 242 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 243 kernel: mps_enqueue_request SMID 653 cm 0xffffff80013ca4a8 ccb 0 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 243 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 244 kernel: SAS Address from SAS device page0 = 500003936811feae kernel: Found device <401,End Device> <6.0Gbps> <0x0078> <4/36> kernel: mpssas_rescan_target targetid 255 kernel: mpssas_rescan kernel: kernel: Target id 0xff added kernel: [1c] kernel: [1c] kernel: [1c] kernel: [1c] kernel: [1c] kernel: [16] kernel: SAS discovery stop event kernel: mpssas_discovery_end kernel: [16] kernel: mpssas_action func 0x4 kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 244 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 244 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 244 kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 1 kernel: Discovery Started kernel: 5 kernel: 0 kernel: mpssas_evt_handler kernel: kernel: 6 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x4 kernel: 0x47 kernel: 37 kernel: 3 kernel: 33 kernel: Responding (0x3) kernel: 5 kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mpssas_evt_handler kernel: kernel: 6 kernel: 0 kernel: SasTopologyChangeList (0x1c) kernel: 0x0 kernel: 0x9 kernel: 0x94 kernel: 37 kernel: 3 kernel: 33 kernel: Responding (0x3) kernel: 5 kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: 0x0000 kernel: LinkRate Unknown (0x0) kernel: Unknown Status kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 247 kernel: mps_intr_msi kernel: [16] kernel: SAS discovery start event kernel: [16] kernel: [1c] kernel: [1c] kernel: [1c] kernel: [1c] kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 247 kernel: mps_intr_msi kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 247 kernel: mpssas_evt_handler kernel: kernel: 2 kernel: 0 kernel: SasDiscovery (0x16) kernel: 0x0 kernel: 0 kernel: Discovery Complete kernel: 5 kernel: 0 kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 248 kernel: [16] kernel: SAS discovery stop event kernel: mpssas_discovery_end kernel: [16] Thanks, -John From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 15 04:39:39 2012 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 90986106566B; Sat, 15 Sep 2012 04:39:39 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5602D8FC0A; Sat, 15 Sep 2012 04:39:39 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q8F4dcFC073123; Fri, 14 Sep 2012 22:39:38 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q8F4dcVx073122; Fri, 14 Sep 2012 22:39:38 -0600 (MDT) (envelope-from ken) Date: Fri, 14 Sep 2012 22:39:38 -0600 From: "Kenneth D. Merry" To: John Message-ID: <20120915043938.GA71754@nargothrond.kdm.org> References: <20120915022437.GA90210@FreeBSD.org> <20120915023329.GA55292@nargothrond.kdm.org> <20120915031305.GA97685@FreeBSD.org> <20120915032826.GA63349@nargothrond.kdm.org> <20120915040907.GA5458@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120915040907.GA5458@FreeBSD.org> User-Agent: Mutt/1.4.2i Cc: FreeBSD iSCSI Subject: Re: How to force a reset of a device (disk) in an enclosre slot 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: Sat, 15 Sep 2012 04:39:39 -0000 On Sat, Sep 15, 2012 at 04:09:07 +0000, John wrote: > ----- Kenneth D. Merry's Original Message ----- > > On Sat, Sep 15, 2012 at 03:13:05 +0000, John wrote: > > > ----- Kenneth D. Merry's Original Message ----- > > > > On Sat, Sep 15, 2012 at 02:24:37 +0000, John wrote: > > > > > Hi Folks, > > > > > > > > > > I've been poking around and can't seem to find a way to reset and > > > > > hopefully acquire access to a disk device in an enclosure. For instance: > > > > > > > > > > FreeBSD 9.1-PRERELEASE > > > > > > > > > > # camcontrol smpphylist ses4 > > > > > 37 PHYs: > > > > > PHY Attached SAS Address > > > > > 0 0x5000039368233602 (pass105,da98) > > > > > 1 0x5000039368238e3e (pass106,da99) > > > > > 2 0x500003936823bca2 (pass107,da100) > > > > > 3 0x500003936819507e (pass108,da101) > > > > > 4 0x5000039368197d5a (pass109,da102) > > > > > 5 0x5000039368197c6e (pass110,da103) > > > > > 6 0x500003936818770e (pass111,da104) > > > > > 7 0x5000039368238eba (pass112,da105) > > > > > 8 0x5000039368232f42 (pass113,da106) > > > > > 9 0x0000000000000000 > > > > > 10 0x500003936813c31e > > > > > 11 0x5000039368233892 (pass114,da107) > > > > > 12 0x500003936813c2ca (pass115,da108) > > > > > ... > > > > > > > > > > Note, bay/slot 10 has a listed device address. If I were to pull the > > > > > drive and re-insert it, it would show up (as da390 in this case). > > > > > The above is after a fresh reboot. Note da106 to da107 skipping > > > > > slot 10 (slot 9 is empty). > > > > > > > > > > The smp utils provide a similar view: > > > > > > > > > > # smp_discover /dev/ses4 > > > > > phy 0:D:attached:[5000039368233602:00 t(SSP)] 6 Gbps > > > > > phy 1:D:attached:[5000039368238e3e:00 t(SSP)] 6 Gbps > > > > > phy 2:D:attached:[500003936823bca2:00 t(SSP)] 6 Gbps > > > > > phy 3:D:attached:[500003936819507e:00 t(SSP)] 6 Gbps > > > > > phy 4:D:attached:[5000039368197d5a:00 t(SSP)] 6 Gbps > > > > > phy 5:D:attached:[5000039368197c6e:00 t(SSP)] 6 Gbps > > > > > phy 6:D:attached:[500003936818770e:00 t(SSP)] 6 Gbps > > > > > phy 7:D:attached:[5000039368238eba:00 t(SSP)] 6 Gbps > > > > > phy 8:D:attached:[5000039368232f42:00 t(SSP)] 6 Gbps > > > > > phy 10:D:attached:[500003936813c31e:00 t(SSP)] 6 Gbps > > > > > phy 11:D:attached:[5000039368233892:00 t(SSP)] 6 Gbps > > > > > phy 12:D:attached:[500003936813c2ca:00 t(SSP)] 6 Gbps > > > > > ... > > > > > > > > > > The address of slot 10 matches. There is a disk in the slot - just > > > > > isn't recognized and attached. > > > > > > > > > > Back to the basic question. How can I issue a command to the enclosure > > > > > to force a re-initialization of the device to recover it without > > > > > having to physically pull & insert it. Even if the device numbers > > > > > are not sequential, I need access to the drive... > > > > > > > > You can try sending a link reset: > > > > > > > > camcontrol smppc ses4 -p 10 -o linkreset > > > > > > > > It may or may not work. You can also try disabling the PHY (-o disable) > > > > and then sending a link reset to re-enable the link. You can also try a > > > > hard reset (-o hardreset) > > > > > > Hi Ken, > > > > > > Well, I hadn't tried to actually disable the device. That did bring some > > > reaction: > > > > > > # camcontrol smppc ses4 -p 10 -o disable > > > # camcontrol smpphylist ses4 > > > 37 PHYs: > > > PHY Attached SAS Address > > > 0 0x5000039368233602 (pass105,da98) > > > .... > > > 8 0x5000039368232f42 (pass113,da106) > > > 9 0x0000000000000000 > > > 10 0x0000000000000000 > > > 11 0x5000039368233892 (pass114,da107) > > > ... > > > > > > The device is gone. > > > > > > # camcontrol smppc ses4 -p 10 -o hardreset > > > root@vprzfs01p:/root # camcontrol smpphylist ses4 > > > 37 PHYs: > > > PHY Attached SAS Address > > > 0 0x5000039368233602 (pass105,da98) > > > .... > > > 8 0x5000039368232f42 (pass113,da106) > > > 9 0x0000000000000000 > > > 10 0x500003936813c31e > > > 11 0x5000039368233892 (pass114,da107) > > > ... > > > > > > The device is back, but not attached - This msg: > > > > > > kernel: mps1: mpssas_alloc_tm freezing simq > > > kernel: mps1: mpssas_remove_complete on handle 0x0069, IOCStatus= 0x0 > > > kernel: mps1: mpssas_free_tm releasing simq > > > kernel: _mapping_add_new_device: failed to add the device with handle 0x0069 to persistent table because there is no free space available - entry 0 > > > > That message is harmless, it won't prevent the drive from attaching. > > > > > >From a debug statement in the driver: MaxPersistentEntries == 128, but I > > > have more than 128 devices per LSI card and they normally all show up - > > > though I do get a bunch of the above messages in dmesg.. > > > > You might try turning on some of the debugging in the mps(4) driver and > > disabling and resetting the link again. > > > > Try: > > > > sysctl -w dev.mps.0.debug_level=0xf > > > > You might get a lot of output, so be prepared to reset it back to 4: > > > > sysctl -w dev.mps.0.debug_level=4 > > Hi Ken, > > I don't see anything obvious. Hopefully you're more familair with the > code and have better eyes than I do... Here's everything from messages > after the -o disable. There are some "unknown/unhandled"s showing up. Here is where the drive shows up: > kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 243 > kernel: mps_enqueue_request SMID 653 cm 0xffffff80013ca4a8 ccb 0 > kernel: mps_intr_locked sc 0xffffff8001353000 starting with replypostindex 243 > kernel: mps_intr_locked sc 0xffffff8001353000 writing postindex 244 > kernel: SAS Address from SAS device page0 = 500003936811feae > kernel: Found device <401,End Device> <6.0Gbps> <0x0078> <4/36> > kernel: mpssas_rescan_target targetid 255 > kernel: mpssas_rescan > kernel: > kernel: Target id 0xff added It finds the device, with target ID 255 (which is a little suspicious) and queues a rescan, but nothing happens after that. You might try doing a manual rescan of that device to see what happens: camcontrol rescan X:255:0 Where X is the scbus number from camcontrol devlist. If that doesn't work, then we need to figure out what the maximum number of targets supported by the adapter is. To do that, set this in /boot/loader.conf and reboot: hw.mps.debug_level=1 That should result in the IOCFacts page getting printed on boot. How many drives and other devices are currently attached to that controller? What controller model is it, and do you have IT or IR firmware on it? Ken -- Kenneth Merry ken@FreeBSD.ORG