Date: Fri, 10 Oct 2003 12:48:52 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: current@FreeBSD.org Subject: Re: Seeing system-lockups on recent current Message-ID: <20031010124744.V66490@carver.gumbysoft.com> In-Reply-To: <p06002013bbac9e8160de@[128.113.24.47]> References: <p06002013bbac9e8160de@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031010124744.V66490>