From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 20 03:10:23 2011 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 AD25C106564A; Sun, 20 Feb 2011 03:10:23 +0000 (UTC) (envelope-from joachim@tingvold.com) Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54]) by mx1.freebsd.org (Postfix) with ESMTP id 615208FC0C; Sun, 20 Feb 2011 03:10:23 +0000 (UTC) Received: from aannecy-552-1-267-197.w92-157.abo.wanadoo.fr ([92.157.235.197] helo=new-host.home) by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1Pqzgj-0005y8-NH; Sun, 20 Feb 2011 04:10:21 +0100 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Joachim Tingvold In-Reply-To: <20110218171619.GB78796@nargothrond.kdm.org> Date: Sun, 20 Feb 2011 04:10:19 +0100 Content-Transfer-Encoding: 7bit Message-Id: <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> References: <07392102-4584-4690-9188-5202728CC7CA@tingvold.com> <20110120155746.GA22515@nargothrond.kdm.org> <070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com> <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> To: Kenneth D. Merry X-Mailer: Apple Mail (2.1076) Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 03:10:23 -0000 On Fri, Feb 18, 2011, at 18:16:19PM GMT+01:00, Kenneth D. Merry wrote: > I just committed a fix to -current for the out of chain buffers > issue. If > you've got time, pull that fix in and see whether it works for you. [jocke@filserver /storage/tmp]$ i=0;while [ $i -le 10 ]; do dd if=/ dev/zero of=foo bs=1M count=204800; let "i += 1"; done I let it run for a while, and checked back later. hw.mps.0.debug_level: 0 hw.mps.0.allow_multiple_tm_cmds: 0 hw.mps.0.io_cmds_active: 0 hw.mps.0.io_cmds_highwater: 970 hw.mps.0.chain_free: 1024 hw.mps.0.chain_free_lowwater: 0 hw.mps.0.chain_alloc_fail: 786 As you can see, I didn't do anything about the 'MPS_CHAIN_FRAMES'- value after I pulled the latest version. I could change it, but I guess this only would get rid of the 'out of chain'-messages, and not really solve the underlying problem. -- Joachim From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 11:07:07 2011 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 B4E1E10656E0 for ; Mon, 21 Feb 2011 11:07:07 +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 A20E68FC22 for ; Mon, 21 Feb 2011 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LB77fd075817 for ; Mon, 21 Feb 2011 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LB77SY075813 for freebsd-scsi@FreeBSD.org; Mon, 21 Feb 2011 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Feb 2011 11:07:07 GMT Message-Id: <201102211107.p1LB77SY075813@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, 21 Feb 2011 11:07:07 -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/154434 scsi [iscsi] FreeBSD iscsi initiator sends invalid scsi com o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after 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/141934 scsi [cam] [patch] add support for SEAGATE DAT Scopion 130 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/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi 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/94838 scsi Kernel panic while mounting SD card with lock switch o 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 bin/57088 scsi [cam] [patch] for a possible fd leak in libcam.c 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/40895 scsi wierd kernel / device driver bug 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 48 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 15:09:36 2011 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 164D0106566B; Mon, 21 Feb 2011 15:09:36 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E1A1E8FC0A; Mon, 21 Feb 2011 15:08:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LF8TUw036238; Mon, 21 Feb 2011 15:08:29 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LF7Nth036226; Mon, 21 Feb 2011 15:07:23 GMT (envelope-from jh) Date: Mon, 21 Feb 2011 15:07:23 GMT Message-Id: <201102211507.p1LF7Nth036226@freefall.freebsd.org> To: me@swizard.beercan.ru, jh@FreeBSD.org, freebsd-scsi@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/94838: Kernel panic while mounting SD card with lock switch on 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, 21 Feb 2011 15:09:36 -0000 Synopsis: Kernel panic while mounting SD card with lock switch on State-Changed-From-To: open->feedback State-Changed-By: jh State-Changed-When: Mon Feb 21 15:07:23 UTC 2011 State-Changed-Why: Can you still reproduce this on a supported release? http://www.freebsd.org/cgi/query-pr.cgi?pr=94838 From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 15:22:03 2011 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF0C31065672; Mon, 21 Feb 2011 15:22:03 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B5A578FC17; Mon, 21 Feb 2011 15:22:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LFM3j8056727; Mon, 21 Feb 2011 15:22:03 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LFM3Tj056723; Mon, 21 Feb 2011 15:22:03 GMT (envelope-from jh) Date: Mon, 21 Feb 2011 15:22:03 GMT Message-Id: <201102211522.p1LFM3Tj056723@freefall.freebsd.org> To: j_guojun@lbl.gov, jh@FreeBSD.org, freebsd-scsi@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/40895: wierd kernel / device driver bug 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, 21 Feb 2011 15:22:04 -0000 Synopsis: wierd kernel / device driver bug State-Changed-From-To: open->feedback State-Changed-By: jh State-Changed-When: Mon Feb 21 15:22:03 UTC 2011 State-Changed-Why: Can you still reproduce this on a supported release? http://www.freebsd.org/cgi/query-pr.cgi?pr=40895 From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 15:50:42 2011 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 8C1451065672; Mon, 21 Feb 2011 15:50:42 +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 124998FC08; Mon, 21 Feb 2011 15:50:41 +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 p1LFoftR038062; Mon, 21 Feb 2011 08:50:41 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p1LFof2d038061; Mon, 21 Feb 2011 08:50:41 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2011 08:50:41 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110221155041.GA37922@nargothrond.kdm.org> References: <070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com> <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 21 Feb 2011 15:50:42 -0000 On Sun, Feb 20, 2011 at 04:10:19 +0100, Joachim Tingvold wrote: > On Fri, Feb 18, 2011, at 18:16:19PM GMT+01:00, Kenneth D. Merry wrote: > >I just committed a fix to -current for the out of chain buffers > >issue. If > >you've got time, pull that fix in and see whether it works for you. > > [jocke@filserver /storage/tmp]$ i=0;while [ $i -le 10 ]; do dd if=/ > dev/zero of=foo bs=1M count=204800; let "i += 1"; done > > I let it run for a while, and checked back later. > > > > hw.mps.0.debug_level: 0 > hw.mps.0.allow_multiple_tm_cmds: 0 > hw.mps.0.io_cmds_active: 0 > hw.mps.0.io_cmds_highwater: 970 > hw.mps.0.chain_free: 1024 > hw.mps.0.chain_free_lowwater: 0 > hw.mps.0.chain_alloc_fail: 786 > > As you can see, I didn't do anything about the 'MPS_CHAIN_FRAMES'- > value after I pulled the latest version. I could change it, but I > guess this only would get rid of the 'out of chain'-messages, and not > really solve the underlying problem. Okay, good. It looks like it is running as designed. I'll probably just double the number of chain buffers and disable the messages. >From previous experiments, the problem is much less likely to occur when you have 2048 chain buffers, correct? What filesystem are you using by the way? Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 16:50:09 2011 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B3181065674 for ; Mon, 21 Feb 2011 16:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1B7548FC1B for ; Mon, 21 Feb 2011 16:50:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LGo8Jk043610 for ; Mon, 21 Feb 2011 16:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LGo8hA043609; Mon, 21 Feb 2011 16:50:08 GMT (envelope-from gnats) Date: Mon, 21 Feb 2011 16:50:08 GMT Message-Id: <201102211650.p1LGo8hA043609@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/94838: Kernel panic while mounting SD card with lock switch on X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 16:50:09 -0000 The following reply was made to PR kern/94838; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@freebsd.org Cc: Subject: Re: kern/94838: Kernel panic while mounting SD card with lock switch on Date: Mon, 21 Feb 2011 18:42:09 +0200 I am not the submitter, but I was able to reproduce this issue a while ago. Now I can not reproduce it - mounting just fails, but there is no panic. It would be nice though for filesystem code (msdos in particular) to autodetect RO/locked media and fallback to RO mount. -- Andriy Gapon From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 18:15:41 2011 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 2ADD7106566B; Mon, 21 Feb 2011 18:15:41 +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 EADA18FC1D; Mon, 21 Feb 2011 18:15:40 +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 p1LIFeHK040561; Mon, 21 Feb 2011 11:15:40 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p1LIFd9t040560; Mon, 21 Feb 2011 11:15:39 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2011 11:15:39 -0700 From: "Kenneth D. Merry" To: Ollivier Robert Message-ID: <20110221181539.GA40528@nargothrond.kdm.org> References: <20110218164209.GA77903@nargothrond.kdm.org> <20110219232057.GA20053@bau44-1-88-173-173-77.fbx.proxad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110219232057.GA20053@bau44-1-88-173-173-77.fbx.proxad.net> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: mps(4) driver (LSI 6Gb SAS) commited to stable/8 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, 21 Feb 2011 18:15:41 -0000 On Sun, Feb 20, 2011 at 00:20:57 +0100, Ollivier Robert wrote: > According to Kenneth D. Merry: > > I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb > > SAS hardware. > > Thanks a lot Ken! You'll make people very happy (incl. me!) in France :) You're welcome! > > There are also a couple of othere issues with the driver that I am planning > > to fix in -current today and merge back into stable/8 in a few days. In > > particular I have fixes for these issues: > > I'll wait till you commit these in stable/8 before regenerating my mfsbsd image. The MFC of both changes is done. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 21:26:40 2011 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 0D8E91065672; Mon, 21 Feb 2011 21:26:40 +0000 (UTC) (envelope-from joachim@tingvold.com) Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54]) by mx1.freebsd.org (Postfix) with ESMTP id B76A28FC19; Mon, 21 Feb 2011 21:26:39 +0000 (UTC) Received: from aannecy-552-1-267-197.w92-157.abo.wanadoo.fr ([92.157.235.197] helo=new-host-2.home) by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1PrdHB-0006k3-LJ; Mon, 21 Feb 2011 22:26:38 +0100 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Joachim Tingvold In-Reply-To: <20110221155041.GA37922@nargothrond.kdm.org> Date: Mon, 21 Feb 2011 22:26:31 +0100 Content-Transfer-Encoding: 7bit Message-Id: <3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com> References: <070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com> <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> <20110221155041.GA37922@nargothrond.kdm.org> To: "Kenneth D. Merry" X-Mailer: Apple Mail (2.1076) Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 21 Feb 2011 21:26:40 -0000 On Mon, Feb 21, 2011, at 16:50:41PM GMT+01:00, Kenneth D. Merry wrote: > Okay, good. It looks like it is running as designed. It is? It still terminating the commands, which I guess it shouldn't? mps0: (0:40:0) terminated ioc 804b scsi 0 state c xfer 0 > I'll probably just double the number of chain buffers and disable the > messages. > > From previous experiments, the problem is much less likely to occur > when > you have 2048 chain buffers, correct? It just doesn't display the 'out of chain'-errors, that's all I think. > What filesystem are you using by the way? ZFS. -- Joachim From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 21 21:45:46 2011 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 C33FB1065672; Mon, 21 Feb 2011 21:45:46 +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 1E6FA8FC17; Mon, 21 Feb 2011 21:45:46 +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 p1LLjjsU044096; Mon, 21 Feb 2011 14:45:45 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p1LLjixQ044095; Mon, 21 Feb 2011 14:45:44 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2011 14:45:44 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110221214544.GA43886@nargothrond.kdm.org> References: <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> <20110221155041.GA37922@nargothrond.kdm.org> <3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 21 Feb 2011 21:45:46 -0000 On Mon, Feb 21, 2011 at 22:26:31 +0100, Joachim Tingvold wrote: > On Mon, Feb 21, 2011, at 16:50:41PM GMT+01:00, Kenneth D. Merry wrote: > >Okay, good. It looks like it is running as designed. > > It is? It still terminating the commands, which I guess it shouldn't? > > mps0: (0:40:0) terminated ioc 804b scsi 0 state c xfer 0 Sorry, I missed that, I was just looking at the first part. I'm still waiting for LSI to look at the SAS analyzer trace I sent them for the "IOC terminated" bug. It appears to be (at least on my hardware) a backend issue of some sort, and probably not anything we can fix in the driver. Since you've got an HP branded expander, that makes it a little more difficult to determine whether it's an LSI, Maxim, or some other expander. Can you try the following on your system? You'll need the sg3_utils port: sg_inq -i ses0 (I need to update camcontrol to parse page 0x83 output.) This is example output from a Supermicro chassis with an LSI 3Gb expander: VPD INQUIRY: Device Identification page Designation descriptor number 1, descriptor length: 12 transport: Serial Attached SCSI (SAS) designator_type: NAA, code_set: Binary associated with the target port NAA 5, IEEE Company_id: 0x3048 Vendor Specific Identifier: 0x45157f [0x500304800045157f] Maxim expanders seem to report LUN descriptors in VPD page 0x83 instead of target port descriptors. We might get a slight clue from the output, but it's hard to say for certain since HP could have customized the page 0x83 values in the expander firmware. > >I'll probably just double the number of chain buffers and disable the > >messages. > > > >From previous experiments, the problem is much less likely to occur > >when > >you have 2048 chain buffers, correct? > > It just doesn't display the 'out of chain'-errors, that's all I think. Well, if you don't see the 'out of chain' errors with 2048 chain buffers, that means the condition isn't happening. The cost of going from 1024 to 2048 is only 32K of extra memory, which is not a big deal, so I think I'll go ahead and bump the limit up and remove the printfs. We've now proven the recovery strategy, so it'll just slow things down slightly if anyone runs into that issue again. > >What filesystem are you using by the way? > > ZFS. Interesting. I haven't been able to run out of chain elements with ZFS, but I can use quite a few with UFS. I had to artificially limit the number of chain elements to test the change. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 23 03:58:18 2011 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 C9DAA106566B; Wed, 23 Feb 2011 03:58:18 +0000 (UTC) (envelope-from joachim@tingvold.com) Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54]) by mx1.freebsd.org (Postfix) with ESMTP id 849E08FC0C; Wed, 23 Feb 2011 03:58:18 +0000 (UTC) Received: from aannecy-552-1-267-197.w92-157.abo.wanadoo.fr ([92.157.235.197] helo=new-host.home) by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1Ps5rk-0005mg-Td; Wed, 23 Feb 2011 04:58:17 +0100 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Joachim Tingvold In-Reply-To: <20110221214544.GA43886@nargothrond.kdm.org> Date: Wed, 23 Feb 2011 04:58:14 +0100 Content-Transfer-Encoding: 7bit Message-Id: <2E532F21-B969-4216-9765-BC1CC1EAB522@tingvold.com> References: <20110203221056.GA25389@nargothrond.kdm.org> <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> <20110221155041.GA37922@nargothrond.kdm.org> <3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com> <20110221214544.GA43886@nargothrond.kdm.org> To: Kenneth D. Merry X-Mailer: Apple Mail (2.1076) Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 23 Feb 2011 03:58:19 -0000 On Mon, Feb 21, 2011, at 22:45:44PM GMT+01:00, Kenneth D. Merry wrote: >>> Okay, good. It looks like it is running as designed. >> It is? It still terminating the commands, which I guess it shouldn't? >> >> mps0: (0:40:0) terminated ioc 804b scsi 0 state c xfer 0 > Sorry, I missed that, I was just looking at the first part. No worries. (-: > I'm still waiting for LSI to look at the SAS analyzer trace I sent > them for > the "IOC terminated" bug. > > It appears to be (at least on my hardware) a backend issue of some > sort, > and probably not anything we can fix in the driver. I see. Good to know that you're able to reproduce it, since I with good possibility can rule out that it's a hardware-issue on my controller. > Since you've got an HP branded expander, that makes it a little more > difficult to determine whether it's an LSI, Maxim, or some other > expander. > Can you try the following on your system? You'll need the sg3_utils > port: > > sg_inq -i ses0 > > (I need to update camcontrol to parse page 0x83 output.) > > [...] > > Maxim expanders seem to report LUN descriptors in VPD page 0x83 > instead of > target port descriptors. We might get a slight clue from the > output, but > it's hard to say for certain since HP could have customized the page > 0x83 > values in the expander firmware. VPD INQUIRY: Device Identification page Designation descriptor number 1, descriptor length: 12 transport: Serial Attached SCSI (SAS) designator_type: NAA, code_set: Binary associated with the target port NAA 5, IEEE Company_id: 0x1438 Vendor Specific Identifier: 0x101a2865 [0x50014380101a2865] Designation descriptor number 2, descriptor length: 8 transport: Serial Attached SCSI (SAS) designator_type: Relative target port, code_set: Binary associated with the target port Relative target port: 0x1 >> It just doesn't display the 'out of chain'-errors, that's all I >> think. > > Well, if you don't see the 'out of chain' errors with 2048 chain > buffers, > that means the condition isn't happening. > > The cost of going from 1024 to 2048 is only 32K of extra memory, > which is > not a big deal, so I think I'll go ahead and bump the limit up and > remove > the printfs. We've now proven the recovery strategy, so it'll just > slow > things down slightly if anyone runs into that issue again. Good. It has such a small impact, yes, so it shouldn't trouble anyone. >>> What filesystem are you using by the way? >> ZFS. > Interesting. I haven't been able to run out of chain elements with > ZFS, > but I can use quite a few with UFS. I had to artificially limit the > number > of chain elements to test the change. Maybe it's because the amount of disks in the same pool that I have? Or that I have two un-even raidz2 vdev's in the same pool? The latter has to be forced when adding it to the pool, so I guess it's not an "ideal" solution... (but "everyone" does it, it seems). -- Joachim From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 23 10:10:12 2011 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27E851065674 for ; Wed, 23 Feb 2011 10:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F0F3E8FC0C for ; Wed, 23 Feb 2011 10:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1NAAB2L067320 for ; Wed, 23 Feb 2011 10:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1NAABKM067319; Wed, 23 Feb 2011 10:10:11 GMT (envelope-from gnats) Date: Wed, 23 Feb 2011 10:10:11 GMT Message-Id: <201102231010.p1NAABKM067319@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Daniel Braniss Cc: Subject: Re: kern/154434: [iscsi] FreeBSD iscsi initiator sends invalid scsi command during iscsi discovery X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Braniss List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Feb 2011 10:10:12 -0000 The following reply was made to PR kern/154434; it has been noted by GNATS. From: Daniel Braniss To: bug-followup@FreeBSD.org, vidhya.gopalan@sun.com Cc: Danny Braniss Subject: Re: kern/154434: [iscsi] FreeBSD iscsi initiator sends invalid scsi command during iscsi discovery Date: Wed, 23 Feb 2011 11:51:37 +0200 I have requested the OP to upgrade the driver and am waiting for response danny From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 25 18:33:53 2011 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 4C451106564A; Fri, 25 Feb 2011 18:33:53 +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 C8C698FC15; Fri, 25 Feb 2011 18:33:52 +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 p1PIXq8x031770; Fri, 25 Feb 2011 11:33:52 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p1PIXpWp031769; Fri, 25 Feb 2011 11:33:51 -0700 (MST) (envelope-from ken) Date: Fri, 25 Feb 2011 11:33:51 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110225183351.GA31590@nargothrond.kdm.org> References: <20110204180011.GA38067@nargothrond.kdm.org> <20110208201310.GA97635@nargothrond.kdm.org> <4A14FA28-6C9E-4F22-B7A3-4295ACD77719@tingvold.com> <20110218171619.GB78796@nargothrond.kdm.org> <318745DD-B5F4-4693-B3F2-22DF8D437349@tingvold.com> <20110221155041.GA37922@nargothrond.kdm.org> <3037190B-6CF2-4C8E-8350-5BA4F13456A8@tingvold.com> <20110221214544.GA43886@nargothrond.kdm.org> <2E532F21-B969-4216-9765-BC1CC1EAB522@tingvold.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2E532F21-B969-4216-9765-BC1CC1EAB522@tingvold.com> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 25 Feb 2011 18:33:53 -0000 On Wed, Feb 23, 2011 at 04:58:14 +0100, Joachim Tingvold wrote: > On Mon, Feb 21, 2011, at 22:45:44PM GMT+01:00, Kenneth D. Merry wrote: > >>>Okay, good. It looks like it is running as designed. > >>It is? It still terminating the commands, which I guess it shouldn't? > >> > >> mps0: (0:40:0) terminated ioc 804b scsi 0 state c xfer 0 > >Sorry, I missed that, I was just looking at the first part. > > No worries. (-: > > >I'm still waiting for LSI to look at the SAS analyzer trace I sent > >them for > >the "IOC terminated" bug. > > > >It appears to be (at least on my hardware) a backend issue of some > >sort, > >and probably not anything we can fix in the driver. > > I see. Good to know that you're able to reproduce it, since I with > good possibility can rule out that it's a hardware-issue on my > controller. And if you're only seeing it occasionally, it's probably not a big worry. I have the driver set up to retry IOC terminated errors without decrementing the retry count, so you won't run into any filesystem or other errors because of it. The only issue is that if you get into a situation where you're getting those errors continuously, you'll wind up in an endless retry loop. (I've seen that on my test system, but 60 drives behind 8 expanders in multiple levels is a bit of an exceptional case.) > >Since you've got an HP branded expander, that makes it a little more > >difficult to determine whether it's an LSI, Maxim, or some other > >expander. > >Can you try the following on your system? You'll need the sg3_utils > >port: > > > >sg_inq -i ses0 > > > >(I need to update camcontrol to parse page 0x83 output.) > > > >[...] > > > >Maxim expanders seem to report LUN descriptors in VPD page 0x83 > >instead of > >target port descriptors. We might get a slight clue from the > >output, but > >it's hard to say for certain since HP could have customized the page > >0x83 > >values in the expander firmware. > > VPD INQUIRY: Device Identification page > Designation descriptor number 1, descriptor length: 12 > transport: Serial Attached SCSI (SAS) > designator_type: NAA, code_set: Binary > associated with the target port > NAA 5, IEEE Company_id: 0x1438 > Vendor Specific Identifier: 0x101a2865 > [0x50014380101a2865] > Designation descriptor number 2, descriptor length: 8 > transport: Serial Attached SCSI (SAS) > designator_type: Relative target port, code_set: Binary > associated with the target port > Relative target port: 0x1 Is this a 6Gb or a 3Gb expander? Since it has a target port descriptor, it might be OEM LSI expander, but who knows. > >>It just doesn't display the 'out of chain'-errors, that's all I > >>think. > > > >Well, if you don't see the 'out of chain' errors with 2048 chain > >buffers, > >that means the condition isn't happening. > > > >The cost of going from 1024 to 2048 is only 32K of extra memory, > >which is > >not a big deal, so I think I'll go ahead and bump the limit up and > >remove > >the printfs. We've now proven the recovery strategy, so it'll just > >slow > >things down slightly if anyone runs into that issue again. > > Good. It has such a small impact, yes, so it shouldn't trouble anyone. I just checked the change into -current, I'll merge it to -stable next week. > >>>What filesystem are you using by the way? > >>ZFS. > >Interesting. I haven't been able to run out of chain elements with > >ZFS, > >but I can use quite a few with UFS. I had to artificially limit the > >number > >of chain elements to test the change. > > Maybe it's because the amount of disks in the same pool that I have? > Or that I have two un-even raidz2 vdev's in the same pool? The latter > has to be forced when adding it to the pool, so I guess it's not an > "ideal" solution... (but "everyone" does it, it seems). I don't think that would affect the out of chain problem. It has a lot more to do with memory fragmentation and therefore how long the scatter/gather lists are that get generated by busdma. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 26 18:10:11 2011 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DEA1065696 for ; Sat, 26 Feb 2011 18:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D45768FC0C for ; Sat, 26 Feb 2011 18:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1QIABvO050658 for ; Sat, 26 Feb 2011 18:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1QIABBt050657; Sat, 26 Feb 2011 18:10:11 GMT (envelope-from gnats) Date: Sat, 26 Feb 2011 18:10:11 GMT Message-Id: <201102261810.p1QIABBt050657@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Mark Linimon Cc: Subject: Re: kern/154434: [iscsi] FreeBSD iscsi initiator sends invalid scsi command during iscsi discovery X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2011 18:10:12 -0000 The following reply was made to PR kern/154434; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/154434: [iscsi] FreeBSD iscsi initiator sends invalid scsi command during iscsi discovery Date: Sat, 26 Feb 2011 12:03:48 -0600 ----- Forwarded message from Daniel Braniss ----- Date: Sat, 26 Feb 2011 12:52:15 +0200 From: Daniel Braniss To: linimon@FreeBSD.org Subject: Re: kern/154434: [iscsi] FreeBSD iscsi initiator sends invalid scsi command during iscsi discovery X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 > I upgraded to FreeBSD8.2 initiator and I am not finding any problem. > > Thanks and Regards, > Vidhya G ----- End forwarded message -----