From owner-freebsd-stable@FreeBSD.ORG Wed Feb 6 12:34:24 2013 Return-Path: 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 2E70A8EE; Wed, 6 Feb 2013 12:34:24 +0000 (UTC) (envelope-from prvs=174982bc16=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4D972D; Wed, 6 Feb 2013 12:34:23 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50002046088.msg; Wed, 06 Feb 2013 12:34:21 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 06 Feb 2013 12:34:21 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=174982bc16=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <29AB0808C9774432B343681D3135F9AF@multiplay.co.uk> From: "Steven Hartland" To: "Daniel Braniss" References: <201302051224.33779.jhb@freebsd.org> Subject: Re: problems with the mfi Date: Wed, 6 Feb 2013 12:30:04 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 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 12:34:24 -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? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.