From owner-freebsd-stable@FreeBSD.ORG Wed Aug 6 21:33:40 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD69E12B; Wed, 6 Aug 2014 21:33:40 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id 71D3D2B10; Wed, 6 Aug 2014 21:33:40 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 9121920E7088B; Wed, 6 Aug 2014 21:33:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: ** X-Spam-Status: No, score=2.8 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1, HELO_NO_DOMAIN, RDNS_DYNAMIC, STOX_REPLY_TYPE, TVD_FINGER_02 autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 992EB20E70885; Wed, 6 Aug 2014 21:33:34 +0000 (UTC) Message-ID: From: "Steven Hartland" To: References: <21474.34330.572142.206098@hergotha.csail.mit.edu> <4DE72E01E8A64E98A31920FCFCAA5D26@multiplay.co.uk> <201408062110.s76LAhhE079487@hergotha.csail.mit.edu> Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers Date: Wed, 6 Aug 2014 22:33:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; 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-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 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 Aug 2014 21:33:40 -0000 TBH that sounds like dodgy hardware. We had a similar thing a few years back with a machine which would panic mfi badly all the time where as other machines where solid as a rock. If its random then you could be facing the same thing. I our case it turned out to be a faulty Intel CPU. There where on other signs of issues just random panic in mfi. So given the similarity and you said it only effects one out of two machines have the HW replaced and see if the problem goes away. Regards Stev ----- Original Message ----- From: To: Cc: ; Sent: Wednesday, August 06, 2014 10:10 PM Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers > In article <4DE72E01E8A64E98A31920FCFCAA5D26@multiplay.co.uk>, > killing@multiplay.co.uk writes: >>The stack from the panic would be a good start. > > As I said, it's in the middle of the USB code, which does not appear, > from my previous bisection, to be connected with the bug at all. (The > panic is the result of an unhandled trap that happens during > interrupt-driven probing, and it's nearly always in the USB code. By > loading different modules I can make it happen at slightly different > times and places.) Six months ago, I found that enabling any form of > memory debugging suppresses the symptoms, although it also kills > performance, of course. I haven't tried that yet this time around. > > Once I get a serial console hooked up I'll be in a better position to > capture the full data (although obviously not a core dump). > > -GAWollman > >