From owner-freebsd-current Tue Aug 28 10:36:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 197F637B403 for ; Tue, 28 Aug 2001 10:36:46 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f7SHahY34060; Tue, 28 Aug 2001 10:36:43 -0700 (PDT) (envelope-from dillon) Date: Tue, 28 Aug 2001 10:36:43 -0700 (PDT) From: Matt Dillon Message-Id: <200108281736.f7SHahY34060@earth.backplane.com> To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Subject: Re: More SIG4s during make world References: <200108281612.f7SGCdf02521@hak.lan.Awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi, : :Just a quick note to say that my -current box has started dropping :cores during make world again. : :I have a kernel from August 11 that works ok, and had one from August :18 that was causing sig 4 at random places. I accidently overwrote :my Aug 18 kernel.old, but Aug 25, 27 and 28 are still dropping cores :all over the place. : :My machine config has changed slightly since this happened in May, :It's now a P4/1.7GHz with 384Mb RAM. : :As before, I can give people access to the box if required - although :unfortunately I haven't got enough room in swap for a kernel core any :more (oops!) -- but that can be fixed if required. : :If anybody has any suggestions, I'd be glad to hear them, otherwise :I'll try rolling the sources forward from the 11th to try to discover :when the breakage occurred. : :Cheers. :-- :Brian : http://www.freebsd-services.com/ I took a look at the diff between those dates and there were a lot of changes. If you have the time it may well be that the best way to home in on the problem is to do a date-based cvs checkout to try to narrow down the date range where the problems started to occur. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message