From owner-freebsd-current  Fri Nov 17 03:01:13 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA24627
          for current-outgoing; Fri, 17 Nov 1995 03:01:13 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA24618
          for <current@freebsd.org>; Fri, 17 Nov 1995 03:01:05 -0800
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id DAA15733; Fri, 17 Nov 1995 03:01:04 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id CAA01067; Fri, 17 Nov 1995 02:57:31 -0800
Message-Id: <199511171057.CAA01067@corbin.Root.COM>
To: hwr@pilhuhn.de (Heiko W.Rupp)
cc: current@freebsd.org
Subject: Re: 2.1-stable bombs at umount 
In-reply-to: Your message of "Wed, 15 Nov 95 16:50:47 +0100."
             <m0tFk6p-0005KXC@pilhuhn.de> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 17 Nov 1995 02:57:31 -0800
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 ..

   I'm not able to reproduce this bug.

[implode:davidg] umount -f /mnt
umount: /mnt: not currently mounted


   When was the last time you updated your sources?

-DG