From owner-freebsd-current@FreeBSD.ORG Tue Oct 21 08:22:08 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 BB79D16A4B3 for ; Tue, 21 Oct 2003 08:22:08 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BDA943FBF for ; Tue, 21 Oct 2003 08:22:05 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9p2/8.12.9) with ESMTP id h9LFM5YL075396; Tue, 21 Oct 2003 11:22:05 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9p2/8.12.9/Submit) id h9LFM4YC075395; Tue, 21 Oct 2003 11:22:04 -0400 (EDT) (envelope-from barney) Date: Tue, 21 Oct 2003 11:22:04 -0400 From: Barney Wolff To: Terry Lambert Message-ID: <20031021152204.GA75081@pit.databus.com> References: <20031020081944.GA40541@kevad.internal> <20031020102613.P47918@beagle.fokus.fraunhofer.de> <20031020132055.GA4653@laptop.6bone.nl> <20031020145001.GA60994@pit.databus.com> <3F94D8EC.48FA556F@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F94D8EC.48FA556F@mindspring.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.37 cc: freebsd-current@freebsd.org Subject: Re: Random signals in {build,install}world recently? 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: Tue, 21 Oct 2003 15:22:08 -0000 On Mon, Oct 20, 2003 at 11:57:48PM -0700, Terry Lambert wrote: > Barney Wolff wrote: > > I don't think so. I tried that on my A7M266D with no effect. I believe > > something in recent pmap code doesn't like this mobo, or maybe dual > > athlons in general. I can run RELENG_5_1 rock solid, and -current from > > 9/24/03 rock solid, but -current from 10/3 or later gets random sigs > > and eventually panics. I have scsi disks so it's not ata. > > I think you need to define "random"; do you mean "rare in frequency > over time at unpredicatable intervals" or "you never know what > program is going to get shot in the head, every 5 seconds, like > clockwork"? The latter, with the interval being more like a very few minutes rather than seconds. The system would sit fine when idle, but never make it all the way through buildworld, or buildkernel, or building a port. In one notorious instance, the -current kernel didn't even make it through installworld without a sig. grep, sed, awk, sh have all gotten sigs, not just cc. > My impression so far in this therad is that it's the former. If > it's the latter, then I need to think about the problem differently. > > > Note that you can identify the patch that caused the problem, if > there's an 8 day difference, in no more than 4 kernel recompiles > (log2(8)+1), if you have a local CVS mirror. The frequency of patches to pmap was quite high, and that was not the only file patched. But yes, I can do a binary search. I haven't, because the changes to pmap were architectural; we're not talking about a typo here. Of course it's just my assumption that it's pmap because the eventual panic is there. btw, I use sched_bsd so _ule is not a suspect. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.