From owner-freebsd-current  Wed Jan 13 05:19:46 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA29987
          for freebsd-current-outgoing; Wed, 13 Jan 1999 05:19:46 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29807
          for <freebsd-current@FreeBSD.ORG>; Wed, 13 Jan 1999 05:18:53 -0800 (PST)
          (envelope-from green@unixhelp.org)
Received: from localhost (green@localhost)
	by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA18782;
	Wed, 13 Jan 1999 07:49:26 -0500 (EST)
Date: Wed, 13 Jan 1999 07:49:26 -0500 (EST)
From: Brian Feldman <green@unixhelp.org>
X-Sender: green@janus.syracuse.net
To: Archie Cobbs <archie@whistle.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Weird file corruption?
In-Reply-To: <199901130527.VAA10163@bubba.whistle.com>
Message-ID: <Pine.BSF.4.05.9901130746260.18618-100000@janus.syracuse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 12 Jan 1999, Archie Cobbs wrote:

> Brian Feldman writes:
> > Then I experienced problems compiling i86.c, which should have been (once
> > extracted again, this part of the archive wasn't corrupted)
> > static void i_xchg_axcx(void)    /* Opcode 0x91 */
> > {
> >     XchgAXReg(CX);    
> > }
> > but was
> > static 
> > static voidaxcx(void)    /* Opcode 0x91 */
> > {
> >     XchgAXReg(CX);
> > }
> > 
> > So far, I really haven't seen this much, but I'm getting worried. Anyone have
> > any idea wha the problem is?
> 
> Bad memory?
> Overclocking?
> Wasn't libz recently updated? (Does gzip use it?)

If it was libz, it would have to be doing some sort of actual modification
of the stream during a gzread :( It's not overclocking, because I set my
CPU at its standard 300 MHz. Maybe it is bad memory... should I go into the
BIOS and try setting the memory's speed lower? I just really want to find
the underlying cause, because this corruption is a very bad thing, and it
happened to my cvsup records file a little while back... I wonder if it could
be anything else.

> 
> -Archie
> 
> ___________________________________________________________________________
> Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 

 Brian Feldman					  _ __  ___ ___ ___  
 green@unixhelp.org			      _ __ ___ | _ ) __|   \ 
	     http://www.freebsd.org/	 _ __ ___ ____ | _ \__ \ |) |
 FreeBSD: The Power to Serve!	   _ __ ___ ____ _____ |___/___/___/ 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message