From owner-freebsd-stable@FreeBSD.ORG Fri Jan 9 15:06:08 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBF68106566C for ; Fri, 9 Jan 2009 15:06:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id B34588FC1B for ; Fri, 9 Jan 2009 15:06:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id n09F66ka008503; Fri, 9 Jan 2009 10:06:06 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id n09F65sF035500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Jan 2009 10:06:06 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200901091506.n09F65sF035500@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 09 Jan 2009 10:05:57 -0500 To: Guy Helmer , Pete French , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <49676406.9050902@palisadesys.com> References: <49676406.9050902@palisadesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 15:06:09 -0000 At 09:49 AM 1/9/2009, Guy Helmer wrote: >>RAID controller with a pair of mirrored drives connected. Each one has >>both ethernets connected, bundled using lagg and LACP. >> >> >I can't tell whether my situation is related, but I am seeing >lockups on SMP Supermicro servers with both older (NetBurst-ish) and >current Xeon CPUs. I have been dropping into the kernel debugger >and getting lock information and process backtraces, but so far >nothing has been conclusively identified. I think the issue I'm >seeing was introduced sometime between October 2 and November 24 in >the RELENG_7 branch, and I suppose the next step is to do a binary >search for the offending change. Are you using the same disk controller as Peter ? Do both of you run with quotas on the file system ? By lockup, do you mean it doesnt respond to the network either or just anything that needs disk IO ? ---Mike