From owner-freebsd-current  Sat Sep 23 14:29:19 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA02029
          for current-outgoing; Sat, 23 Sep 1995 14:29:19 -0700
Received: (from dyson@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA02018
          ; Sat, 23 Sep 1995 14:29:15 -0700
From: John Dyson <dyson>
Message-Id: <199509232129.OAA02018@freefall.freebsd.org>
Subject: Re: more core dumps
To: jleppek@suw2k.ess.harris.com (James Leppek)
Date: Sat, 23 Sep 1995 14:29:14 -0700 (PDT)
Cc: freebsd-current@freefall.FreeBSD.org
In-Reply-To: <9509231955.AA07295@borg.ess.harris.com> from "James Leppek" at Sep 23, 95 03:55:55 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 586       
Sender: owner-current@FreeBSD.org
Precedence: bulk

> 
> netscape worked yesterday but today's kernel causes a core dump (sig 11)
> I have tried netscape 1.0 and 1.1 and they both core :-(
> This is with a kernel that has doclusterread as 0.
> 
> anyone else seeing this?
> 
> Jim Leppek
> 
I haven't seen it, but one of the underlying problems that was covered
up by the work-around could still cause problems.  The problem was with
buffer cache corruption, and that has been fixed in the latest commit.
Try the latest stuff with doclusterread == 0, and your problem might
go away.  Then, turn on read clustering, it should work.

John