Date: Thu, 3 Oct 2002 23:00:53 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: Reason: releng4 comp. hack, machdep.c 1.539 (was: cvsupd death (signal 6)) Message-ID: <20021003190051.GA11148@nagual.pp.ru> In-Reply-To: <200210031549.g93FnAnw001370@vashon.polstra.com> References: <20021001152542.GA15704@nagual.pp.ru> <20021003024857.GA2461@nagual.pp.ru> <200210031549.g93FnAnw001370@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 03, 2002 at 08:49:10 -0700, John Polstra wrote: > > Good sleuthing! Just divide desert by a half to catch a lion. I mean backward/forward date-based cvsup rollback narrowed to one commit in question. > > *** Value out of range > > *** file > > "/tmp/a/ports/lang/ezm3/work/ezm3-1.0/libs/libm3/src/uid/Common/Time > > Stamp.m3", line 63 > > This particular message is usually caused by a very bogus system date > setting. I test it with exact the same cvsupd data set and system files, but with different kernels. Kernel without the commit in question not show any signs of signal 6 in 12 hours. Kernel with this commit show signal 6 death in approximate first 20 minutes. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021003190051.GA11148>