Date: Wed, 06 Feb 2013 12:35:19 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: "Steven Hartland" <killing@multiplay.co.uk> Cc: freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: problems with the mfi Message-ID: <E1U32LX-000DgS-Kv@kabab.cs.huji.ac.il> In-Reply-To: <D2D11675983447BE912A5C498CF526C3@multiplay.co.uk> References: <E1U2eCa-0007TS-HS@kabab.cs.huji.ac.il> <201302051224.33779.jhb@freebsd.org> <D2D11675983447BE912A5C498CF526C3@multiplay.co.uk>
index | next in thread | previous in thread | raw e-mail
> ----- Original Message ----- > From: "John Baldwin" <jhb@freebsd.org> > > > > On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: > >> after rebooting I get very often: > >> ... > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 659 SECONDS > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 689 SECONDS > >> mfi0: COMMAND 0xffffff800132d990 TIMEOUT AFTER 719 SECONDS > >> ... > >> > >> another reboot usualy fixes this. > > > > Does it have the latest firmware? > > Be aware that the current code for mfi timeout's never abort so > if you get a command stuck it will moan forever. > > This is one of the issues fixed in a patch that's in testing. > > Regards > Steve i know :-), I caught this one because the machine was not rebooting. can you shed some light as to what command timed out? cheers, dannyhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1U32LX-000DgS-Kv>