From owner-freebsd-current@FreeBSD.ORG Fri Oct 10 12:48:52 2003 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 B573216A4B3 for ; Fri, 10 Oct 2003 12:48:52 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D63543FDF for ; Fri, 10 Oct 2003 12:48:52 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2E7D872DA3; Fri, 10 Oct 2003 12:48:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2C4D672DA2; Fri, 10 Oct 2003 12:48:52 -0700 (PDT) Date: Fri, 10 Oct 2003 12:48:52 -0700 (PDT) From: Doug White To: Garance A Drosihn In-Reply-To: Message-ID: <20031010124744.V66490@carver.gumbysoft.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: Seeing system-lockups on recent current 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: Fri, 10 Oct 2003 19:48:52 -0000 On Fri, 10 Oct 2003, Garance A Drosihn wrote: > For the past week or so, I have been having a frustrating time > with my freebsd-current/i386 system. It is a dual Athlon > system. It has been running -current just fine since December, > with me updating the OS every week or two. I did not update it > for most of September, and then went to update it to pick up > the recent round of security-related fixes. It would be useful to isolate exactly what day the problem started occuring. That would simplify isolating the offending commit. Use the date specifier in cvsup to checkout specific dates, then build & test. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org