From owner-freebsd-current@FreeBSD.ORG Tue Mar 27 17:46:36 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D2241065676; Tue, 27 Mar 2012 17:46:36 +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 9D8B08FC1A; Tue, 27 Mar 2012 17:46:35 +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 q2RHLUKC068423; Tue, 27 Mar 2012 11:21:30 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q2RHLUcu068422; Tue, 27 Mar 2012 11:21:30 -0600 (MDT) (envelope-from ken) Date: Tue, 27 Mar 2012 11:21:29 -0600 From: "Kenneth D. Merry" To: Matt Thyer Message-ID: <20120327172129.GA67307@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> <20120326132558.GB76647@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: "Desai, Kashyap" , Gary Palmer , Garrett Cooper , freebsd-current@freebsd.org, Steven Hartland , freebsd-scsi@freebsd.org Subject: Re: LSI supported mps(4) driver available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2012 17:46:36 -0000 On Tue, Mar 27, 2012 at 23:50:31 +1030, Matt Thyer wrote: > On 26 March 2012 23:55, Gary Palmer wrote: > > > On Mon, Mar 26, 2012 at 08:05:59PM +1030, Matt Thyer wrote: > > > On Mar 26, 2012 3:43 AM, "Garrett Cooper" wrote: > > > > > > > > On Sun, Mar 25, 2012 at 5:16 AM, Matt Thyer > > wrote: > > > > > Has this driver been MFC to 8-STABLE yet ? > > > > > > > > > > I'm asking because I updated my NAS on the 4th of March from 8-STABLE > > > > > r225723 to r232477 and am now seeing 157,000 interrupts per second on > > > irq > > > > > 16 where my SuperMicro AOC-USAS2-L8i resides (this card uses the LSI > > > > > SAS2008 chip). > > > > [snip] > > > > > After encountering this problem I updated my firmware from phase 7 to > > phase > > > 11 but this did not fix things. > > > > > > My question is: "Is the LSI driver even in 8-STABLE yet?". > > > > > > If not I'll upgrade to 9-STABLE to get the new driver. > > > > > > If it is, then I want to downgrade to just before it came in to see if > > this > > > high interrupt rate problem is fixed. > > > > I'm no export in svn, however: > > > > http://svnweb.freebsd.org/base?view=revision&revision=230922 > > > > would appear to suggest that the new driver is in 8-Stable > > > > Gary > > > > It's painful to take this system back to r230921 due to intolerance for > downtime from it's users so I'd like to investigate the cause of the > problem and try patches/sysctls/whatever first. > > The drives I'm using are 7 x WDC WD20EARS-00M (3 are AB50, 4 are AB51) and > 1 x WD20EARX-00P AB51. > The WD20EARX-00P AB51 is a SATA 3 (6 Gbps) drive but the others are all > SATA 2 (3 Gbps). > > I know the driver doesn't like mixed speeds in IR mode but I'm flashed with > IT firmware as ZFS is doing my RAID (raidz2). > > I was having problems with the WD20EARX-00P AB51 drive being faulted by ZFS > until I updated the firmware to 11 and now ZFS is happy (I've also done a > full extended drive SMART test and the drive is fine). > > So what do people suggest (before reversion to r230921) ? If you're going to prove that it's the new LSI driver, you will probably have to go back to the old driver. You don't have to back out your entire tree, you can just back out the driver itself if you have an SVN tree. You can go into sys/dev/mps and do: svn update -r 230714 And then edit sys/conf/files and comment out these three lines: dev/mps/mps_config.c optional mps dev/mps/mps_mapping.c optional mps dev/mps/mps_sas_lsi.c optional mps Then you should be able to rebuild your kernel with the old driver and see if the problem occurs again. Ken -- Kenneth Merry ken@FreeBSD.ORG