From owner-freebsd-stable@FreeBSD.ORG Thu Oct 3 19:47:10 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 871D2EF2 for ; Thu, 3 Oct 2013 19:47:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 093A72B79 for ; Thu, 3 Oct 2013 19:47:09 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r93Jl4Kc019811; Thu, 3 Oct 2013 22:47:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r93Jl4Kc019811 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r93Jl4B8019809; Thu, 3 Oct 2013 22:47:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 3 Oct 2013 22:47:04 +0300 From: Konstantin Belousov To: Ryan Stone Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE Message-ID: <20131003194704.GG41229@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4duS90ZuJLzQ/Kg" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: 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: Thu, 03 Oct 2013 19:47:10 -0000 --T4duS90ZuJLzQ/Kg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 03, 2013 at 11:50:15AM -0400, Ryan Stone wrote: > We're having trouble booting 9.2-RELEASE on a system with an mfi > (Drake Skinny) controller. When it tries to mount root we get: >=20 > mfi0: COMMAND 0xffffff8000cb7220 TIMEOUT AFTER 59 SECONDS > mfi0: COMMAND 0xffffff8000cb72a8 TIMEOUT AFTER 60 SECONDS > mfi0: COMMAND 0xffffff8000cb7220 TIMEOUT AFTER 90 SECONDS >=20 > I also get the following when mfi attaches (with bootverbose): >=20 > mfi0: port 0x5000-0x50ff mem 0xfbd60000-0xfbd63fff,0xfbd00= 000-0xf > bd3ffff irq 16 at device 0.0 on pci2^M > mfi0: attempting to allocate 1 MSI vectors (1 supported)^M > msi: routing MSI IRQ 282 to local APIC 0 vector 77^M > mfi0: using IRQ 282 for MSI^M > mfi0: Using MSI^M > mfi0: Megaraid SAS driver Ver 4.23 ^M > mfi0: Frame 0xffffff85d394b280 timed out command 0x1010000^M > error 60 in callback from mfi_send_frame^M > mfi0: Frame 0xffffff85d394b500 timed out command 0x1040100^M > error 60 in callback from mfi_send_frame^M > mfi0: Frame 0xffffff85d394b780 timed out command 0x1040300^M > error 60 in callback from mfi_send_frame^M > mfi0: Error 255 fetching controller entries^M >=20 > I've put full bootverbose logs from boots with hw.mfi.msi=3D0 and > hw.mfi.msi=3D1 here: > http://people.freebsd.org/~rstone/mfi_timeout_irq.txt > http://people.freebsd.org/~rstone/mfi_timeout_msi.txt >=20 > Neither boot was successful. I don't have the ability to boot from > alternative media so I have a limited ability to test changes (I can > re-image from a full disk image, but that requires building a new disk > image which takes some time). >=20 > I did see the following forum post and tried with cbb and pccard > removed from GENERIC. That didn't fix it. > http://forums.freebsd.org/showpost.php?p=3D231135&postcount=3D4 I have two Drake Skinny cards, one four-ports, one with eight ports, both not working with either version of driver in HEAD from February up to now. I tried to talk about this both with Doug Ambrisko and "Desai, Kashyap" , and provided the debugging data I could think of, but no avail. There is a rumor that it might be related to the slot the card is inserted in. I only have 8x or wider PCIe slot provided by CPU north-bridge. It might be that card does not like it and only work in the south-bridge PCIe lanes. I have no idea why could it be so, neither I saw the confirmation of the speculation. --T4duS90ZuJLzQ/Kg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQIcBAEBAgAGBQJSTcm3AAoJEJDCuSvBvK1BIz8QAIxvQuzKQkg4W/ptDCBxobxp LjQpv2Br2vmLBplnLsY/jANmHknBAI/TASMk3d/v+eUq4hvmW85LUDUHJ2KztsaB hVjLAj2Qab/Ry3PvorrIYTNOQMJzRwIx4i4mGfV/V2wByQJ5K4YcJ7bOTWT+vT8c ex96uI6vfI6tV+PrwEEtGpoHAgJPsHEYi1Ut8aAPQxk5qbBJizWOtolAe5nNfxiF 9rlp+l9F5DP1dVX6jtxcuz+dunYZrsqpzqe5VuCtR+2QMWGuAcxpACpbouApeQWc 0SZKdsfi9GDyj8Oz2TpNwNgfF8T/6GrFJnjEkHQPUYTgrF0nlQGIN6R7ht/4iooY 8NtOhph67gl3tbFUVWnBrutzp9ePAPwuR+Mx/BPYmAUJYr+SlRc7LwPslT4TEVpJ lIyUmVFHyGoQQBR/jZ8gyWSBYVXlK44UV+wWrBLG49W+6apdzvWapMsPn8CkRTni DrNQNHENxtDiUsHJi4OAiGgTUuG5/XAqYTvSSnX7N2x6HlO1eLeNHzzJrmJQVxwH Jb6DWH0oziob7+ZWGiyY1wg+6RkCCJu126b1/8CDBGiWogHlAqDYX1VbhGfYFcdP f97HAPRFUEi9uBcTBV+aMIBlzu7cjvU/6MSSLmAqHXJugL/JCWBU9xX0gaMhGxd7 6YrAit87iBdiU574uelp =XIZO -----END PGP SIGNATURE----- --T4duS90ZuJLzQ/Kg--