From owner-freebsd-stable@FreeBSD.ORG Fri Oct 4 05:53:13 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 2655C41F for ; Fri, 4 Oct 2013 05:53:13 +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 551E42663 for ; Fri, 4 Oct 2013 05:53:11 +0000 (UTC) Received: (qmail 39936 invoked by uid 907); 4 Oct 2013 05:53:10 -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 15:53:10 +1000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE From: Jan Mikkelsen In-Reply-To: <20131004052457.GN41229@kib.kiev.ua> Date: Fri, 4 Oct 2013 15:53:10 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20131003194704.GG41229@kib.kiev.ua> <20131004052457.GN41229@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1510) Cc: freebsd-stable@freebsd.org, Ryan Stone 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 05:53:13 -0000 >> We have Drake Skinny (9240-4i and 9240-8i) cards running, most = recently with 9.2-RC4. We'll be testing 9.2-RELEASE in the next week or = two. >>=20 >> We have seen problems with older versions of the firmware, and = interactions with some Supermicro BIOS versions. All these problems have = been resolved by upgrading to the latest versions of the controller = firmware and system BIOSes. >>=20 >> We're running with with hw.mfi.msi=3D1. I haven't tested without that = since early 2011; I should probably try it out. >>=20 >> So: What firmware do you have in the controller? Did you update it? >=20 > Yes, I reflashed one board to the latest blob I was able to find at = that > time. For the second board, I did not bothered. The info I am able = to > find right now in my outcoming mbox, is >=20 > (this is for four-ports, was flashed, I believe) > mfi0: 916 (boot + 3s/0x0020/info) - Firmware version 2.130.374-2023 = =20 > mfi0: 917 (boot + 6s/0x0020/info) - Package version 20.10.1-0126 = =20 > mfi0: 918 (boot + 6s/0x0020/info) - Board Revision 03A >=20 > (and this is for eight-ports) > mfi0: 326 (boot + 4s/0x0020/info) - Firmware version 2.130.314-1585 = =20 > mfi0: 327 (boot + 5s/0x0020/info) - Package version 20.10.1-0101 = =20 > mfi0: 328 (boot + 5s/0x0020/info) - Board Revision 03B >=20 > I am pretty much sure that the issue is either in the m/b = compatibility > or mfi(4) driver. OK. I haven't seen timeout errors like that for a long time, so you = could be right. I don't know. This is from a running 9.2-RC4 system: 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=20 ... 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 Regards, Jan.