From nobody@FreeBSD.org  Sun Mar 20 19:40:05 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7C2B216A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 20 Mar 2005 19:40:05 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 15D6D43D1D
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 20 Mar 2005 19:40:05 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j2KJe491026403
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 20 Mar 2005 19:40:04 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j2KJe4G2026401;
	Sun, 20 Mar 2005 19:40:04 GMT
	(envelope-from nobody)
Message-Id: <200503201940.j2KJe4G2026401@www.freebsd.org>
Date: Sun, 20 Mar 2005 19:40:04 GMT
From: Kyryll A Mirnenko <mirya@innovativemarketing.com.ua>
To: freebsd-gnats-submit@FreeBSD.org
Subject: floppy umount crash
X-Send-Pr-Version: www-2.3

>Number:         79058
>Category:       kern
>Synopsis:       [panic] floppy umount crash on accidental remove/reinsert
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 20 19:50:02 GMT 2005
>Closed-Date:    Sun Mar 09 20:28:45 UTC 2008
>Last-Modified:  Sun Mar 09 20:28:45 UTC 2008
>Originator:     Kyryll A Mirnenko
>Release:        5.4-PRERELEASE
>Organization:
IMU
>Environment:
FreeBSD localhost 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #20: Sun Mar 13 19:07:18 EET 2005     root@localhost:/usr/src/sys/i386/compile/MY-O3  i386
>Description:
before umounting the floppy i have accidently removed it from the drive, then put it back & tried to umount (there were no attempts to flush disk buffers there while it was out of the drive). Got this:

fsync: giving up on dirty.
0xc16a5948: tag devfs, type VCHP, usecount 2, writecount 0, refcount 8
lock type devfs: EXCL (count 1)
by thread 0xc13e6960 (pid 557)
dev fd0

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x64
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0548077
stack pointer = 0x10:0xc7fdcc60
frame pointer = 0x10:0xc1650e10
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 = 561 (umount)
trap number = 12
panic: page fault

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x64
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0548077
stack pointer = 0x10:0xc7fdcaec
frame pointer = 0x10:0x0
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 = 561 (umount)
trap number = 12
panic: page fault

More info:
CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>How-To-Repeat:
as described above

>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: vwe 
State-Changed-When: Sun Mar 9 20:23:45 UTC 2008 
State-Changed-Why:  

Kyryll, 
I'm sorry to see your problem report being untouched for years. 
Unfortunately your report does not contain enough information for further 
inspection of your problem, but is an already known problem. 
The problem here is to remove the device while the filesystem on it 
is still mounted. We do have a lot of reports like this with different 
devices and are aware of that problem. It is on the other side not 
easy to solve and I'm pretty sure, it will take some more time  
to make FreeBSD more fail safe when removing active devices. 

As this is an already known problem _and_ your ticket does not contain 
much information for debugging, I'm going to close this ticket. 

If you think this should be held open, please feed back with more 
information. 

Again, sorry for not caring of your report for so long and thank 
you for reporting. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=79058 
>Unformatted:
