From owner-freebsd-bugs  Tue Jun  6 11:49:36 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA01856
          for bugs-outgoing; Tue, 6 Jun 1995 11:49:36 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA01850
          for <bugs@freebsd.org>; Tue, 6 Jun 1995 11:49:34 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA02306; Tue, 6 Jun 1995 11:51:25 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00541; Tue, 6 Jun 1995 11:48:16 -0700
Message-Id: <199506061848.LAA00541@corbin.Root.COM>
To: Stephen Hocking <sysseh@devetir.qld.gov.au>
cc: bugs@FreeBSD.org
Subject: Re: 2.0.5-A: Very disheartening? 
In-reply-to: Your message of "Tue, 06 Jun 95 11:04:31 GMT."
             <199506061104.LAA15596@netfl15a.devetir.qld.gov.au> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Tue, 06 Jun 1995 11:47:01 -0700
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>	Might this not have something to do with unzipping something
>executable into memory and then failing to invalidate the cache entries for
>the memory you've just unzipped into? It sounds like a failure mode that
>you'd see with machines that have split I/D caches. I know it's easy to yell
>suggestions from the sidelines, but wouldn't it be a good idea to invalidate
>the cache after the image has been unzipped into memory?

  No. If you don't have cache coherency for things the *CPU* writes to memory,
you may as well pack up your marbles and go home. The problem isn't likely
caused by any sort of cache problem (even though it is apparantly effected by
disabling the cache).

-DG