From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 13:24:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2165635B; Wed, 6 Feb 2013 13:24:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id BF5409B4; Wed, 6 Feb 2013 13:24:41 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by kabab.cs.huji.ac.il with esmtp id 1U34zP-000MUr-Sq; Wed, 06 Feb 2013 15:24:40 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: "Steven Hartland" Subject: Re: problems with the mfi In-reply-to: <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> References: <201302051224.33779.jhb@freebsd.org> <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> Comments: In-reply-to "Steven Hartland" message dated "Wed, 06 Feb 2013 12:30:04 +0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Feb 2013 15:24:39 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org, John Baldwin 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: Wed, 06 Feb 2013 13:24:42 -0000 > ----- Original Message ----- > From: "Daniel Braniss" > >> > 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: 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