From owner-freebsd-stable@FreeBSD.ORG  Wed Feb  6 09:20:39 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 3438E752;
 Wed,  6 Feb 2013 09:20:39 +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 DCBE5B66;
 Wed,  6 Feb 2013 09:20:38 +0000 (UTC)
Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny)
 by kabab.cs.huji.ac.il with esmtp
 id 1U31BA-000C50-6a; Wed, 06 Feb 2013 11:20:32 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: John Baldwin <jhb@freebsd.org>
Subject: Re: problems with the mfi
In-reply-to: <201302051224.33779.jhb@freebsd.org>
References: <E1U2eCa-0007TS-HS@kabab.cs.huji.ac.il> 
 <201302051224.33779.jhb@freebsd.org>
Comments: In-reply-to John Baldwin <jhb@freebsd.org>
 message dated "Tue, 05 Feb 2013 12:24:33 -0500."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 06 Feb 2013 11:20:32 +0200
From: Daniel Braniss <danny@cs.huji.ac.il>
Message-ID: <E1U31BA-000C50-6a@kabab.cs.huji.ac.il>
Cc: freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 09:20:39 -0000

> 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?

it happened on several boxes, this one just arrived a week ago, and I will 
check, but
most probably has the latest firmaware.

cheers
	danny

> 
> -- 
> John Baldwin