From nobody  Wed Feb 10 12:35:47 1999
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA15961;
          Wed, 10 Feb 1999 12:35:47 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199902102035.MAA15961@hub.freebsd.org>
Date: Wed, 10 Feb 1999 12:35:47 -0800 (PST)
From: jegelhof@cloud9.net
To: freebsd-gnats-submit@freebsd.org
Subject: msdos floppy disk mounts
X-Send-Pr-Version: www-1.0

>Number:         10013
>Category:       kern
>Synopsis:       msdos floppy disk mounts
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 10 12:40:00 PST 1999
>Closed-Date:    Wed Jun 23 07:16:10 PDT 1999
>Last-Modified:  Wed Jun 23 07:17:13 PDT 1999
>Originator:     james Egelhof
>Release:        FreeBSD 3.0-RELEASE
>Organization:
Cloud 9 Consulting, Inc.
>Environment:
FreeBSD longjing.cloud9.net 3.0-RELEASE FreeBSD 3.0-RELEASE #0: 
Sat Jan 16 15:02:08 EST 1999     
root@newlongjing.cloud9.net:/usr/src/sys/compile/LONGJING  i386
>Description:

Working with MS-DOS floppy disks results in random reboots when any
intensive use of the disk is made.
>How-To-Repeat:

Mount a MS-DOS disk and attempt to use it.  Commands like 'file' and
'less' have resulted in reboots.
>Fix:
None known.
>Release-Note:
>Audit-Trail:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: jegelhof@cloud9.net
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/10013: msdos floppy disk mounts 
Date: Mon, 21 Jun 1999 19:20:40 +0200

 James, could you confirm that the problem exists in a more recent
 version of FreeBSD, preferably 3.2-RELEASE or 3.2-STABLE?
 
 If so, can you send a more definitive How-To-Repeat? I ran a few
 concurrent copy / file / cat / rm jobs on an msdos floppy using FreeBSD
 4.0-CURRENT and couldn't reproduce the problem.
 
 Ideally, what we'd want is your kernel config and a set of shell
 commands that reproduces the fault (along with an indication of how long
 one can expect for the fault to occur).
 
 You might also try it on another machine, in case you have broken
 hardware?
 
 Thanks,
 Sheldon.
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Tue Jun 22 03:30:09 PDT 1999 
State-Changed-Why:  
Waiting on submitter for feedback. 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Wed Jun 23 07:16:10 PDT 1999 
State-Changed-Why:  
I can't reproduce the problem in CURRENT and submitter confirms that 
the problem isn't reproducible in 3.2-RELEASE . 
>Unformatted:
