From owner-freebsd-current  Tue Jul 16 18:14:55 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA28585
          for current-outgoing; Tue, 16 Jul 1996 18:14:55 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA28572
          for <current@freebsd.org>; Tue, 16 Jul 1996 18:14:52 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id LAA18225; Wed, 17 Jul 1996 11:12:19 +1000
Date: Wed, 17 Jul 1996 11:12:19 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199607170112.LAA18225@godzilla.zeta.org.au>
To: current@freebsd.org, sthaug@nethelp.no
Subject: Re: panic when ls /kern without KERNFS
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

># 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.

There was a fix on 1996/07/02 for ls -l panicing, but plain ls still
panics here with yesterday's kernel.

>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.

No, it should work.  kernfs is an lkm.

Bruce