From owner-freebsd-stable  Fri Mar  6 09:59:54 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA23946
          for freebsd-stable-outgoing; Fri, 6 Mar 1998 09:59:54 -0800 (PST)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23917
          for <freebsd-stable@FreeBSD.ORG>; Fri, 6 Mar 1998 09:59:27 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id JAA00705;
	Fri, 6 Mar 1998 09:54:59 -0800 (PST)
Message-Id: <199803061754.JAA00705@implode.root.com>
To: Chris Timmons <skynyrd@opus.cts.cwu.edu>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: panic in vfs_bio.c getnewbuf+0x21f 
In-reply-to: Your message of "Fri, 06 Mar 1998 07:05:21 PST."
             <Pine.BSF.3.96.980306070113.28799A-100000@opus.cts.cwu.edu> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 06 Mar 1998 09:54:59 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk

>My kernel.old is from saturday (2/28) and doesn't display the problem. 
>Did I mention that I'm running a P90 overclocked to 333mhz?  (Just
>kidding, the hardware is conventional and very stable.) 

   Can you try backing out just the vfs_bio.c change and see if this also
cures the problem?

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

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