Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Feb 2012 12:04:05 +1100
From:      Jan Mikkelsen <janm@transactionware.com>
To:        Csillag Tamas <cstamas@digitus.itk.ppke.hu>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: mfi timeout issues and patch that seems to work (PERC H800)
Message-ID:  <D0CB85E6-0C4B-4BC7-8647-51334B4BF51C@transactionware.com>
In-Reply-To: <20120223235932.GB19927@rivendell>
References:  <20120223235932.GB19927@rivendell>

next in thread | previous in thread | raw e-mail | index | archive | help

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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0CB85E6-0C4B-4BC7-8647-51334B4BF51C>