From owner-freebsd-current@FreeBSD.ORG Fri Jul 2 20:43:19 2004 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 A247016A4CE for ; Fri, 2 Jul 2004 20:43:19 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9787143D45 for ; Fri, 2 Jul 2004 20:43:19 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id AD50372DF2; Fri, 2 Jul 2004 13:42:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id A814172DB5; Fri, 2 Jul 2004 13:42:15 -0700 (PDT) Date: Fri, 2 Jul 2004 13:42:15 -0700 (PDT) From: Doug White To: bugghy In-Reply-To: <1088716575.47518.9.camel@illusion.com> Message-ID: <20040702134131.U84991@carver.gumbysoft.com> References: <1088691081.59098.3.camel@illusion.com> <20040701103803.U73568@carver.gumbysoft.com> <1088716575.47518.9.camel@illusion.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Bus error (core dumped) problem 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: Fri, 02 Jul 2004 20:43:19 -0000 On Thu, 1 Jul 2004, bugghy wrote: > Now everything seems to break ... > > > pkg_deinstall pth-2.0.0 > [Updating the pkgdb in /var/db/pkg ... - 276 > packages found > (-2 +0) (...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:467: [BUG] > Segmentation > fault > ruby 1.8.1 (2003-12-25) [i386-freebsd5] > > Abort trap (core dumped) > > I've exceeded quota for the coredump but I can send it on private. > The computer is in good state ... and worked fine for a long time now. > Another family member boots windows on another hdd with no problems. > > It has the same problems without vmmon. This is classic hardware failure. It might be a failure that Windows can't exercise, but there's something critically wrong with the system. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org