From owner-freebsd-current@FreeBSD.ORG Thu Jul 31 13:52:10 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 9C85437B401 for ; Thu, 31 Jul 2003 13:52:10 -0700 (PDT) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82E1A43F93 for ; Thu, 31 Jul 2003 13:52:09 -0700 (PDT) (envelope-from bruce@cran.org.uk) Received: from buffy.brucec.backnet ([82.41.200.71]) by smtp-out4.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600); Thu, 31 Jul 2003 21:52:04 +0100 Received: from buffy.brucec.backnet (localhost [127.0.0.1]) by buffy.brucec.backnet (8.12.9/8.12.9) with ESMTP id h6VKq883014484; Thu, 31 Jul 2003 21:52:08 +0100 (BST) (envelope-from bruce@buffy.brucec.backnet) Received: (from bruce@localhost) by buffy.brucec.backnet (8.12.9/8.12.9/Submit) id h6VKq8Z8014483; Thu, 31 Jul 2003 21:52:08 +0100 (BST) Date: Thu, 31 Jul 2003 21:52:08 +0100 From: Bruce Cran To: Chris Shenton Message-ID: <20030731205208.GA14443@buffy.brucec.backnet> References: <86he52r1b6.fsf@PECTOPAH.shenton.org> <86zniupli2.fsf@PECTOPAH.shenton.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86zniupli2.fsf@PECTOPAH.shenton.org> User-Agent: Mutt/1.4.1i X-OriginalArrivalTime: 31 Jul 2003 20:52:05.0068 (UTC) FILETIME=[995C28C0:01C357A5] cc: current@freebsd.org Subject: Re: make buildworld: Signal 11; Illegal instruction 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: Thu, 31 Jul 2003 20:52:10 -0000 On Thu, Jul 31, 2003 at 03:03:01PM -0400, Chris Shenton wrote: > Chris Shenton writes: > > > *** Signal 11 > >... > > Illegal instruction (core dumped) > > *** Error code 132 > > Also seeing > > *** Signal 4 > > if it matters. This sounds way too flakey to be SW. I'm seeing the same symptoms. I got a signal 4 when running 'clean' in the pam authentication directory, and I've just had a signal 11 running 'rm -f libradius.so'. This is an install from a snapshot I built today - during the install I had panics in _mtx_init_ and a backtrace traced through vfs and ffs functions, and I only managed to install successfully when I had the CPU throttled to 30%. This is the same computer which ran memtest86 for 8 hours without a single fault last night, so I doubt the hardware's faulty, at least not the memory or the CPU. -- Bruce Cran