From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 25 01:30:46 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 AA7F0106564A for ; Sat, 25 Feb 2012 01:30:46 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from midgard.transactionware.com (mail2.transactionware.com [203.14.245.36]) by mx1.freebsd.org (Postfix) with SMTP id EB8DD8FC0A for ; Sat, 25 Feb 2012 01:30:45 +0000 (UTC) Received: (qmail 27002 invoked by uid 907); 25 Feb 2012 01:04:03 -0000 Received: from eth222.nsw.adsl.internode.on.net (HELO [192.168.1.54]) (150.101.196.221) (smtp-auth username janm, mechanism plain) by midgard.transactionware.com (qpsmtpd/0.84) with (AES128-SHA encrypted) ESMTPSA; Sat, 25 Feb 2012 12:04:03 +1100 Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1250 From: Jan Mikkelsen In-Reply-To: <20120223235932.GB19927@rivendell> Date: Sat, 25 Feb 2012 12:04:05 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120223235932.GB19927@rivendell> To: Csillag Tamas X-Mailer: Apple Mail (2.1257) Cc: freebsd-scsi@freebsd.org Subject: Re: mfi timeout issues and patch that seems to work (PERC H800) 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, 25 Feb 2012 01:30:46 -0000 On 24/02/2012, at 10:59 AM, Csillag Tamas wrote: > Hi, >=20 > I had the same issues with the Perc H800 controller as it is described > here:=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/140416 > (Just for google I include the error here: > mfi0: COMMAND 0xffffff80009c4b90 TIMEOUT AFTER 41 SECONDS) > [ =85 ] > however getting and compiling the newest kernel did NOT fix it for me. > Issuing commands with mfiutils still fixed the hang and everything > returned to normal. >=20 > It seems that intensive read triggers the issue, but if you have write > concurrently you are fine (mostly). Restarting rsync is ideal for > triggering this buggy condition. >=20 > I tried to poke around in the source code and in the end tweaked the > patch (seen here before > = http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html): >=20 > replacing > (void)sc->mfi_read_fw_status(sc); > with > mfi_get_controller_info(sc); > around line 933 >=20 > and after testing it for a day it seems to be solid. > (The original patch did not help me.) >=20 > Can someone expert in the topic can confirm if any of this is correct? The default value for hw.mfi.msi is 0. I had to set it to 1 in = /boot/loader.conf when using a 9261-8i controller. It might be worth = retesting with that setting and the standard kernel. Regards, Jan.