From owner-freebsd-current@FreeBSD.ORG Tue Oct 21 00:00:23 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 1873C16A4BF for ; Tue, 21 Oct 2003 00:00:23 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5AB543FAF for ; Tue, 21 Oct 2003 00:00:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0fk.dialup.mindspring.com ([209.86.1.244] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1ABqV9-0007Ut-00; Tue, 21 Oct 2003 00:00:19 -0700 Message-ID: <3F94D8EC.48FA556F@mindspring.com> Date: Mon, 20 Oct 2003 23:57:48 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Barney Wolff References: <20031020081944.GA40541@kevad.internal> <20031020102613.P47918@beagle.fokus.fraunhofer.de> <20031020145001.GA60994@pit.databus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a45333e7aa43bb305dd75094431ace958f666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c 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 07:00:23 -0000 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"? 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. -- Terry