From owner-freebsd-stable  Wed Apr  3 11:58:52 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA18529
          for stable-outgoing; Wed, 3 Apr 1996 11:58:52 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA18523
          for <freebsd-stable@freebsd.org>; Wed, 3 Apr 1996 11:58:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id LAA17153; Wed, 3 Apr 1996 11:56:06 -0800 (PST)
Message-Id: <199604031956.LAA17153@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Frank E. Terhaar-Yonkers" <fty@mcnc.org>
cc: freebsd-stable@freebsd.org
Subject: Re: panic in latest -stable rev 
In-reply-to: Your message of "Wed, 03 Apr 1996 09:04:53 EST."
             <199604031404.JAA14615@robin.mcnc.org.mcnc.org> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 03 Apr 1996 11:56:05 -0800
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Latest SUP is not-so-stable ...
>
>I get an immediate panic on boot up of the latest -stable.  This
>happens via mount_msdosfs and results in a VM page fault.  Have dropped
>back to the rev of late March.  I took a dump on this, but savecore
>failed to find it.  Didn't match the magic #.

   The LKMs are no longer compatible and must be rebuilt. There was a change
to the vnode structure that was required to fix a critical bug and this now
requires that either build support for all your filesystems "static" or
you rebuild your LKMs before mounting the filesystems that they are for. I
suggest making msdosfs static by adding:

options "MSDOSFS"

    to your kernel config file.

-DG

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