Date: Fri, 4 Oct 2013 09:03:00 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Jan Mikkelsen <janm@transactionware.com> Cc: freebsd-stable@freebsd.org, Ryan Stone <rysto32@gmail.com> Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE Message-ID: <20131004060300.GP41229@kib.kiev.ua> In-Reply-To: <DAB5A340-813E-4495-A771-14523E64F526@transactionware.com> References: <CAFMmRNzWwxe=YVJcC7Lkjqru5eugciwzEQHjgE-Bh-ctOykVNQ@mail.gmail.com> <20131003194704.GG41229@kib.kiev.ua> <E0480AD0-8097-41D2-BCB6-8650AA662C20@transactionware.com> <20131004052457.GN41229@kib.kiev.ua> <DAB5A340-813E-4495-A771-14523E64F526@transactionware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--V0/E3hsWvtxr/GVk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Oct 04, 2013 at 03:53:10PM +1000, Jan Mikkelsen wrote:
> >> We have Drake Skinny (9240-4i and 9240-8i) cards running, most recentl=
y 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 interac=
tions with some Supermicro BIOS versions. All these problems have been reso=
lved by upgrading to the latest versions of the controller firmware and sys=
tem 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.
>=20
> OK. I haven't seen timeout errors like that for a long time, so you could=
be right. I don't know.
>=20
> This is from a running 9.2-RC4 system:
>=20
> mfi1: <Drake Skinny> port 0xc000-0xc0ff mem 0xfad9c000-0xfad9ffff,0xfadc0=
000-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
Could you provide me the output of the kenv(8) ? I am interested in the
smbios mibs, i.e. your hardware identification.
--V0/E3hsWvtxr/GVk
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)
iQIcBAEBAgAGBQJSTloTAAoJEJDCuSvBvK1BUvsP/jSqWAZk11jQthTz7SPMCgJw
5YR3UGWhq1JESFZS1Er8FtHy6g81LgoyRqWrCIPTvycSnVlcsaAOjDORYkKNYbz9
GorvWFavv9a8AhhFJtZ8dGR9+fmRsqYVLpy8OeoRPaQwqbJ9DMmPaOhxe+DdAre9
7gvWf6r9ly6vZcXlSVwOrOoKCFUDUW+KzB+Mnou7ur2olA5kWB2yyKCd4uVEMapu
A28BdliNz1eOyf8e7x8DzCaCpx8XioZ9KFdHKQK7izo/uKpKxgjlybkdiaGYT+Cu
uXNHlTKayU6BQmHlDH5vUUpeBXlni/vn4EnD/1Kjg768lEwpL+c4Kqdi/4O2FpS3
e7sUxg0t1PP4zf4piPWUfLCmFGt/lM+EO/YStwq4+0f99UejoDslBWoTXpmLmXuD
au0RlAKbJZ7o3wIvtZoVYFELOwLdmn/H4Og04FBTew1yCj45n48P9C+lB1+tcroA
LF0HwvYZ9pffDhoz6f9ib+N+BiIOWNvm8sF6+rvO7Rwk9UhOXLk6drS9dbEItjuR
+k/piJt0V+/Uam8HqWOU20J8inVgZZOTnEQ6u+MQTSZ3/hzzWikYJ1maErj5aFHi
qPUTKmj1iP9FyX4jL1i7w9Pr773Ow5oIHzs1sQDORMUm8CCE9uGGPNcV7j+6z8O8
ANLJ+tGh88MJF9HEtPn8
=NyU7
-----END PGP SIGNATURE-----
--V0/E3hsWvtxr/GVk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131004060300.GP41229>