From owner-freebsd-stable@FreeBSD.ORG Thu Nov 12 10:46:25 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 5CD3F106566C for ; Thu, 12 Nov 2009 10:46:25 +0000 (UTC) (envelope-from michal@sharescope.co.uk) Received: from mail1.sharescope.co.uk (pm1.ionic.co.uk [85.159.80.19]) by mx1.freebsd.org (Postfix) with ESMTP id 185D58FC08 for ; Thu, 12 Nov 2009 10:46:24 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail1.sharescope.co.uk (Postfix) with ESMTP id 2DD1BFC102; Thu, 12 Nov 2009 10:46:24 +0000 (UTC) X-Virus-Scanned: amavisd-new at sharescope.co.uk Received: from mail1.sharescope.co.uk ([127.0.0.1]) by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Dd1xNZdtNfy; Thu, 12 Nov 2009 10:46:19 +0000 (GMT) Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2]) (Authenticated sender: chris@sharescope.co.uk) by mail1.sharescope.co.uk (Postfix) with ESMTPSA id C2B3DFC0D7; Thu, 12 Nov 2009 10:46:19 +0000 (GMT) Message-ID: <4AFBE77A.8060605@sharescope.co.uk> Date: Thu, 12 Nov 2009 10:46:18 +0000 From: Michal User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Hans.F.Nordhaug@hiMolde.no, freebsd-stable@freebsd.org References: <20091112103308.GA2536@hiMolde.no> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: 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 10:46:25 -0000 Ivan Voras wrote: > Hans F. Nordhaug wrote: >> Hi! >> >> 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? >> >> Hans >> >> 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 > > All of this points to a hardware problem. > Last time I saw things like this it was either a hard drive on the way out, or a PSU dying. Run some pre-OS tests (Ultimate boot cd or something) to try and get some results outside of the OS > I think the best thing you can try is to manually get a hash fingerprint > of your sh and compare it with another, known good copy. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"