Date: Wed, 06 Feb 2013 15:24:39 +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: <E1U34zP-000MUr-Sq@kabab.cs.huji.ac.il> In-Reply-To: <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> References: <E1U2eCa-0007TS-HS@kabab.cs.huji.ac.il> <201302051224.33779.jhb@freebsd.org> <D2D11675983447BE912A5C498CF526C3@multiplay.co.uk> <E1U32LX-000DgS-Kv@kabab.cs.huji.ac.il> <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> ----- Original Message ----- > From: "Daniel Braniss" <danny@cs.huji.ac.il> > >> > 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. > > > > i know :-), I caught this one because the machine was not rebooting. > > can you shed some light as to what command timed out? > > Unfortunately not it was a generic issue any command which timeout > would get stuck for ever. > > What FreeBSD version are using and what controller are you using? > freebsd-9.1-stable as of last Friday the last one that did this is: mfi1: <Dell PERC H810 Adapter> port 0xdc00-0xdcff mem 0xd4ffc000-0xd4ffffff,0xd4f80000-0xd4fbffff irq 66 at device 0.0 on pci65 but I saw this on older PERCs too. cheers, danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1U34zP-000MUr-Sq>