From owner-freebsd-hackers  Sun Sep 14 02:49:10 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA03107
          for hackers-outgoing; Sun, 14 Sep 1997 02:49:10 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA03099
          for <hackers@FreeBSD.ORG>; Sun, 14 Sep 1997 02:49:07 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA11346;
	Sun, 14 Sep 1997 02:51:11 -0700 (PDT)
Message-Id: <199709140951.CAA11346@implode.root.com>
To: Joe McGuckin <joe@via.net>
cc: hackers@FreeBSD.ORG
Subject: Re: 2.2.2R panics 
In-reply-to: Your message of "Sun, 14 Sep 1997 00:14:42 PDT."
             <199709140714.AAA06192@monk.via.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 14 Sep 1997 02:51:10 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>
>2.2.2R on my news machine will die 30 to 90 minutes after a reboot.
>
>The msg looks like:
>
>  Fatal trap 12: page fault while in kernel mode.
>  Superuser read: page not present.
>  Stopped at allocbuf+0x463	btrl ....

   A few obvious questions: Does it always panic in exactly the same
way? If not, do the failures look fairly random or is there a common theme?
What was the configuration of the machine when it worked? If possible, why
not go back to that configuration? Did you try updating to 2.2-stable? Did
you try a previous release (2.2.1 or perhaps 2.1.7.1) to see if this gets
rid of the problem? How much from the standard GENERIC kernel config does
your kernel config file deviate?

-DG

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