Date: Mon, 26 Apr 2004 10:40:07 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: edwinculp <edwinculp@prodigy.net.mx> Cc: current@freebsd.org Subject: Re: updating a Athlon XP 2200 signal 4's everywhere Message-ID: <20040426103920.C23749@carver.gumbysoft.com> In-Reply-To: <40850888.28a.ad9.8814@prodigy.net.mx> References: <40850888.28a.ad9.8814@prodigy.net.mx>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040426103920.C23749>