From owner-freebsd-current  Tue Jul 16 15:26:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA01786
          for current-outgoing; Tue, 16 Jul 1996 15:26:46 -0700 (PDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA01778
          for <current@freebsd.org>; Tue, 16 Jul 1996 15:26:42 -0700 (PDT)
From: sthaug@nethelp.no
Received: (qmail-queue invoked from smtpd); 16 Jul 1996 22:26:14 +0000 (GMT)
Received: from localhost (HELO verdi.nethelp.no) (@127.0.0.1)
  by localhost with SMTP; 16 Jul 1996 22:26:14 +0000 (GMT)
To: current@freebsd.org
Subject: panic when ls /kern without KERNFS
X-Mailer: Mew version 1.05+ on Emacs 19.28.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 17 Jul 1996 00:26:14 +0200
Message-ID: <6182.837555974@verdi.nethelp.no>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Is this a known bug?

# mount_kernfs /kern /kern
# ls /kern
<panic: Fatal trap 12: page fault while in kernel mode>

when the kernel in question is compiled *without* the KERNFS option.
It's quite reproducible. This is with 2.2-960612-SNAP on AMD 5x86-133,
ASUS PVI-486SP3 board.

With KERNFS, everything works just fine.

I certainly agree that one shouldn't do mount_kernfs without KERNFS
in the kernel - but I'd expect an error message from mount_kernfs, not
a panic from the following ls.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no