From owner-freebsd-stable@FreeBSD.ORG Thu Aug 7 02:26:37 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 9B498EFD for ; Thu, 7 Aug 2014 02:26:37 +0000 (UTC) Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 51CC62F7C for ; Thu, 7 Aug 2014 02:26:36 +0000 (UTC) Received: by mail-qa0-f44.google.com with SMTP id f12so3339983qad.17 for ; Wed, 06 Aug 2014 19:26:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=baXJlnJOdv+fSB9iLTza93S1AzAzgx3zU8cX5i/N5Go=; b=LSfHnNsKlPSHhWjm2ym1nD7dOi4rxp1rPEKkEJ8w80lBIBgHaiwQFqgBkQ0gkWX3lQ /zR78ucoxNNU34RPinIFXioI7VM0jJIE2g8iAQt8wHLe4otwAI+A8NczvDhkFEnZmk+I P+uEDEXbGmhIV6chRR6WqpeLSKUNxTRKbkvf58YPUDI66SM+lUcq8cUqi7YmYKlN2pKU BFd6O1VEbA385Q8WOfqUoQtl48JcYBDioqiBmMncp/HGlp2D9VBlhCrzdpb3LYYC3veO IvHZ0CXbIdDX/dufaIr4UsPCj4p3+DYAo779rnKPjt81KE63JgX93KPqX1osWMEIVwkr ucdg== X-Gm-Message-State: ALoCoQnLrfl0oRys2JxbXEcNVoI2QyjT/XBWRkqQ7oDHrehPrZ+1/kdUYtRTRDBgf6VELPrgG7R4 X-Received: by 10.140.43.245 with SMTP id e108mr8689388qga.76.1407378395357; Wed, 06 Aug 2014 19:26:35 -0700 (PDT) Received: from [97.62.248.155] (155.sub-97-62-248.myvzw.com. [97.62.248.155]) by mx.google.com with ESMTPSA id k6sm874951qgf.5.2014.08.06.19.26.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Aug 2014 19:26:33 -0700 (PDT) References: <21474.34330.572142.206098@hergotha.csail.mit.edu> <4DE72E01E8A64E98A31920FCFCAA5D26@multiplay.co.uk> <201408062110.s76LAhhE079487@hergotha.csail.mit.edu> Mime-Version: 1.0 (1.0) In-Reply-To: Message-Id: <45558B49-C3DD-4FD0-8E04-38BC30A1AC35@longcount.org> X-Mailer: iPhone Mail (11D257) From: Mark Saad Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers Date: Wed, 6 Aug 2014 22:26:23 -0400 To: Steven Hartland Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 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: Thu, 07 Aug 2014 02:26:37 -0000 > On Aug 6, 2014, at 5:33 PM, "Steven Hartland" wr= ote: >=20 > 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. >=20 Why details can you provide about the hardware ? Could you upload a dmesg.bo= ot to=20 www.nycbug.org/index.cgi?action=3Ddmesgd&do=3Dhome > If its random then you could be facing the same thing. >=20 > I our case it turned out to be a faulty Intel CPU. There where on other > signs of issues just random panic in mfi. >=20 > So given the similarity and you said it only effects one out of two machin= es > have the HW replaced and see if the problem goes away. >=20 > Regards > Stev >=20 > ----- 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 >=20 >=20 >> 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 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Mark saad | mark.saad@longcount.org=20=