From owner-freebsd-stable@FreeBSD.ORG Fri Oct 4 09:18:25 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EEF131D6 for ; Fri, 4 Oct 2013 09:18:25 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail3.transactionware.com [202.68.173.211]) by mx1.freebsd.org (Postfix) with SMTP id 2555B207D for ; Fri, 4 Oct 2013 09:18:24 +0000 (UTC) Received: (qmail 11974 invoked by uid 907); 4 Oct 2013 09:18:22 -0000 Received: from Unknown (HELO [192.168.2.132]) (202.68.173.218) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (AES128-SHA encrypted) ESMTPSA; Fri, 04 Oct 2013 19:18:22 +1000 Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset=iso-8859-1 From: Jan Mikkelsen X-Priority: 3 In-Reply-To: <50CFBCA5FBFB4525AD3F49AB779D31FB@multiplay.co.uk> Date: Fri, 4 Oct 2013 19:18:21 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20131003194704.GG41229@kib.kiev.ua> <20131004052457.GN41229@kib.kiev.ua> <24C7E2F8EDAF40439C076C03B8A0E203@multiplay.co.uk> <50CFBCA5FBFB4525AD3F49AB779D31FB@multiplay.co.uk> To: "Steven Hartland" X-Mailer: Apple Mail (2.1510) Cc: Konstantin Belousov , Ryan Stone , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2013 09:18:26 -0000 On 04/10/2013, at 6:59 PM, "Steven Hartland" = wrote: > ----- Original Message ----- From: "Jan Mikkelsen" = >=20 >>>> mfi1: port 0xc000-0xc0ff mem = 0xfad9c000-0xfad9ffff,0xfadc0000-0xfadfffff irq 30 at device 0.0 on pci2 >>>> mfi1: Using MSI >>>> mfi1: Megaraid SAS driver Ver 4.23 >>>> ... >>>> mfi1: 15228 (boot + 3s/0x0020/info) - Firmware version = 2.130.384-2291 >>>> mfi1: 15229 (boot + 5s/0x0020/info) - Package version 20.11.1-0137 >>>> mfi1: 15230 (boot + 5s/0x0020/info) - Board Revision 03A >>> In every case I've invesitgated for this is been either:- >>> 1. Old Firmware >>> 2. Bad Cabling, Disk or Ram >>> I'm 99.9999% certain timeout issues are not a driver issue. #1 is = the cause of >>> almost all occurances I've looked at. >>> FW we're running here is: >>> mfi0: Megaraid SAS driver Ver 4.23 >>> ... >>> mfi0: 14299 (boot + 4s/0x0020/info) - Firmware version 3.190.05-1669 >>> mfi0: 14300 (boot + 5s/0x0020/info) - Package version 23.7.0-0029 >>> mfi0: 14301 (boot + 5s/0x0020/info) - Board Revision >>> So looks like your FW is quite old and needs updating. >>=20 >> Either we're not talking about the same card or there is somewhere to = find >> firmware that I don't know about. >>=20 >> I just checked the LSI website for 9240-4i firmware and there is a >> 20.12.1-0150 version (labeled "4.11") released on 23 September 2013. = The >> previous version is the version running in this machine. >>=20 >> Are we talking about the same card? Is there a better place to look = for >> firmware updates on the LSI website? >=20 > There are many different MFI controllers unforutnately making tracking > versions very hard especially when OEM's have different versions = again. > Id suggest contacting LSI support and request the FW with the command > timeout fix in. I'm not the one with the problem, that's Konstantin & Ryan. It works for me on many machines with 9240-4i and -8i controllers and = 9261-8i controllers. I have also seen problems that have been resolved = through firmware updates which is how we got to talking about firmware = revisions. So the point "... looks like your FW is quite old and needs updating" is = really "check your firmware." Thanks, Jan.