From owner-freebsd-stable@FreeBSD.ORG Thu Nov 12 11:53:52 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E914106568F for ; Thu, 12 Nov 2009 11:53:52 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 771DE8FC27 for ; Thu, 12 Nov 2009 11:53:51 +0000 (UTC) Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id 4Bl21d0090b6N64AABtsDD; Thu, 12 Nov 2009 11:53:52 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by OMTA03.emeryville.ca.mail.comcast.net with comcast id 4Btr1d00C3S48mS8PBtrWF; Thu, 12 Nov 2009 11:53:51 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 2FA501E3035; Thu, 12 Nov 2009 03:53:50 -0800 (PST) Date: Thu, 12 Nov 2009 03:53:50 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20091112115350.GA18542@icarus.home.lan> References: <20091112103308.GA2536@hiMolde.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091112103308.GA2536@hiMolde.no> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: /bin/sh core dumps on FreeBSD 7.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2009 11:53:52 -0000 On Thu, Nov 12, 2009 at 11:33:08AM +0100, Hans F. Nordhaug wrote: > Suddenly /bin/sh started to crash all the time with core dumps. I'm > running FreeBSD 7.2-RELEASE-p4 (i386) and I have not updated anything > lately. The /bin/sh binary seems to be untouched. It might be some > hardware trouble, but the machine seems to run OK now. (I had to > replace /bin/sh with a symlink to /rescue/sh.) > > I would like to track down the problem, but running sh I only get > "Segmentation fault: 11 (core dumped)". I would be happy to run > gdb and give you a backtrace. Any clues? > > PS! I tried to run "freebsd-update IDS" to see if any files are > broken, but it stops at > Inspecting system... sha256: ///boot/kernel/utopia.ko.symbols: Input/output error Hardware problem. Take your pick: bad RAM, bad hard disk, bad motherboard, bad PSU, bad cabling. You can rule out hard disk problems by installing smartmontools from ports (sysutils/smartmontools). Please provide output from the following command: smartctl -a /dev/{disk} Where {disk} is "ad4", "da0", or similar -- and NOT something like "ad8s1" or "da0s1d". If multiple disks are in your machine -- the one you want is the disk you boot from (where /boot exists, and/or root filesystem). I can teach you how to decode/read SMART statistics correctly. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |