From owner-freebsd-current@FreeBSD.ORG Sat Aug 28 02:11:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4685C16A4CE for ; Sat, 28 Aug 2004 02:11:58 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38FEB43D41 for ; Sat, 28 Aug 2004 02:11:58 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2DB7472DD4; Fri, 27 Aug 2004 19:11:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2870A72DCB; Fri, 27 Aug 2004 19:11:58 -0700 (PDT) Date: Fri, 27 Aug 2004 19:11:58 -0700 (PDT) From: Doug White To: Craig Boston In-Reply-To: <20040826214816.GB40029@nowhere> Message-ID: <20040827190953.W51306@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826145324.GA40029@nowhere><20040826214816.GB40029@nowhere> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Aug 2004 02:11:58 -0000 On Thu, 26 Aug 2004, Craig Boston wrote: > On Thu, Aug 26, 2004 at 11:18:34AM -0700, Doug White wrote: > > Okay, for those of you experiencing the data corruption issue, I need to > > know the following: > > Sure, I'll do what I can to help track this down. > > > . cvsup date & time for the affect kernel(s) > > "Sometime yesterday" is the closest I can come up with by memory. > /usr/sup/src-all/checkouts.cvs:RELENG_5 seems to indicate 8/25/2004 > 05:39 UTC, which sounds right. > > > . branch you're tracking > > RELENG_5 + IPI patch > (manually reapplied after each cvsup) > > > . revision of src/sys/kern/kern_lock.c - I'm checking for a specific set > > of commits here > > /usr/src/sys/kern/kern_lock.c: > $FreeBSD: src/sys/kern/kern_lock.c,v 1.74 2004/08/16 15:01:22 kan Exp $ DING DING DING -- we have a winner. This rev is bogus and was backed out. Back up to a working kernel, cvsup, and re-build. The IPI patch has been merged so you won't need to reapply it. > Possibly. The only other thing recently changed on there is using > gvinum instead of regular vinum. But there's no hard evidence either > way -- my stripe size is much bigger than the size of the corrupt > sections, and the frequency of the corrupt files appearing seems to be > about the same as the frequency of deadlocks I had prior to the IPI > patch. Both facts are completely circumstantial and could easily be > coincidence. Or it could be something else entirely. Good to know that there was some bogosity in gvinum too that you might be hitting :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org