Date: Thu, 17 Nov 2011 14:21:16 +1100 From: Jan Mikkelsen <janm@transactionware.com> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>, Vincent Hoffman <vince@unsane.co.uk> Subject: Re: mfi timeouts Message-ID: <75BA89D7-8D63-41BB-A20C-F3A03D40FF74@transactionware.com> In-Reply-To: <4EC393E8.9070500@unsane.co.uk> References: <4EA9E0C3.5080306@unsane.co.uk> <201111090939.14177.jhb@freebsd.org> <4EBBAE90.8010101@unsane.co.uk> <201111141442.16722.jhb@freebsd.org> <4EC393E8.9070500@unsane.co.uk>
index | next in thread | previous in thread | raw e-mail
On 16/11/2011, at 9:43 PM, Vincent Hoffman wrote: > On 14/11/2011 19:42, John Baldwin wrote: >> On Thursday, November 10, 2011 5:59:28 am Vincent Hoffman wrote: >>> Well the dell has been up for about 19 hours now using MSI, I ran >>> bonnie++ a few times on it and have now stuck it in a permanent loop >>> (will look in from time to time.) Are there any tests you'd like >>> run/info you'd like? >> Actually, can you please test www.freebsd.org/~jhb/patches/mfi_msi.patch? >> You will have to set the hw.mfi.msi=1 tunable to enable MSI support. This >> is a commit candidate if it works. Thanks. >> > Applied and running with bonnie++ overnight. All good for me at least. Boots for me with hw.mfi.msi=1, fails to boot with mw.mfi.msi=0, giving repeated timeout messages pretty much as expected. Won't be able to put load on it until later tomorrow or next week. Regards, Jan.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75BA89D7-8D63-41BB-A20C-F3A03D40FF74>