From owner-freebsd-current Tue Oct 29 00:19:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA05462 for current-outgoing; Tue, 29 Oct 1996 00:19:58 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA05457 for ; Tue, 29 Oct 1996 00:19:56 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA12179; Tue, 29 Oct 1996 18:49:49 +1030 From: Michael Smith Message-Id: <199610290819.SAA12179@genesis.atrad.adelaide.edu.au> Subject: Re: Crashes (page faults) and odd behavior on current To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Tue, 29 Oct 1996 18:49:48 +1030 (CST) Cc: karl@Mcs.Net, current@FreeBSD.org In-Reply-To: <199610290554.VAA29224@freefall.freebsd.org> from "Justin T. Gibbs" at Oct 28, 96 09:54:44 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs stands accused of saying: > > I also started seeing this stuff sometime this weekend. My symptom is > tar complaing about a corrupted file when untaring something large (say > 11MB). Unmount/Remount the fs, and the tar extracts just fine. > I was going to play around with my RAM to see if it was the culpret, but > this second report makes it look like a software bug. On a kernel from around the 21st or so, we had the 'dead binary stays dead' problem last night, followed by a lockup of some sort. (Couldn't tell, as the machine was running X 8( ) Naturally, I'm upgrading again. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[