From owner-freebsd-current@FreeBSD.ORG  Mon Apr 26 10:40:07 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E28AF16A4CE
	for <current@freebsd.org>; Mon, 26 Apr 2004 10:40:07 -0700 (PDT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C43D643D2F
	for <current@freebsd.org>; Mon, 26 Apr 2004 10:40:07 -0700 (PDT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id B03EC72DF0; Mon, 26 Apr 2004 10:40:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id AA03472DBF; Mon, 26 Apr 2004 10:40:07 -0700 (PDT)
Date: Mon, 26 Apr 2004 10:40:07 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: edwinculp <edwinculp@prodigy.net.mx>
In-Reply-To: <40850888.28a.ad9.8814@prodigy.net.mx>
Message-ID: <20040426103920.C23749@carver.gumbysoft.com>
References: <40850888.28a.ad9.8814@prodigy.net.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: updating a Athlon XP 2200 signal 4's everywhere
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2004 17:40:08 -0000

On Tue, 20 Apr 2004, edwinculp wrote:

> On April 17 I tried updating an Athlon XP from a current
> built at the end of february or the begining of march.
> Cvsup, buildworld, installworld, buildkernel, installkernel
> worked fine.  I didn't reboot and test the installation and
> on April 18 resup'ed and repeated the process - bad idea --
> everything built except the kernel and now I am getting
> signal 4 dumps on fsck, sysctl, df, ps, dd, etc.  I can't
> remember ever having signal 4 problems.  I built a new
> release on Sunday night on another machine, burned a CD and
> tried doing a new install but it wouldn't write to the disk.
> (maybe the reported entropy problem) I did an update to
> April 18 but it still has the same signal 4 problem.

Make sure you don't have a bogus CPU type set in /etc/make.conf.

Signal 4 = SIGILL for people not paying attention.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org