From owner-freebsd-current  Wed Nov 15 07:51:53 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA13451
          for current-outgoing; Wed, 15 Nov 1995 07:51:53 -0800
Received: from pilhuhn.de (pilhuhn.de [193.141.89.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA13442
          for <current@freebsd.org>; Wed, 15 Nov 1995 07:51:48 -0800
Received: by pilhuhn.de id <m0tFk6p-0005KXC> ; Wed, 15 Nov 95 16:51 MET
Message-Id: <m0tFk6p-0005KXC@pilhuhn.de>
From: hwr@pilhuhn.de (Heiko W.Rupp)
Subject: 2.1-stable bombs at umount
To: current@freebsd.org
Date: Wed, 15 Nov 1995 16:50:47 +0100 (MET)
X-Mailer: ELM [version 2.4 PL20]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 817       
Sender: owner-current@freebsd.org
Precedence: bulk

Hi,

I had that box under 2.1-stable running and did a 
umount -f /news  ; mount /news

the result was:

| Fatal trap 12: page fault while in kernel mode
| fault virtual address   = 0x80
| fault code              = supervisor read, page not present
| instruction pointer     = 0x8:0xf0172ee8
| code segment            = base 0x0, limit 0xfffff, type 0x1b
|                         = DPL 0, pres 1, def32 1, gran 1
| processor eflags        = interrupt enabled, resume, IOPL = 0
| current process         = 7171 (umount)
| interrupt mask          = 
| panic: page fault

I know that unmounting a filesystem which is not the best idea ... but
I think this should only lead to errors , not to panics ..

-- 
Heiko W.Rupp        Gerwigstr.5        D-76131  Karlsruhe    +49 721 9661524
Ein glueckliches Huhn dank neg ...