From seggers@semyam.dinoco.de  Mon Oct 13 22:36:17 1997
Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23890
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 13 Oct 1997 22:36:14 -0700 (PDT)
          (envelope-from seggers@semyam.dinoco.de)
Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.6.6) with UUCP id HAA07497 for FreeBSD-gnats-submit@freebsd.org; Tue, 14 Oct 1997 07:35:23 +0200 (MET DST)
Received: (from seggers@localhost)
	by semyam.dinoco.de (8.8.5/8.8.5) id HAA00541;
	Tue, 14 Oct 1997 07:29:13 +0200 (CEST)
Message-Id: <199710140529.HAA00541@semyam.dinoco.de>
Date: Tue, 14 Oct 1997 07:29:13 +0200 (CEST)
From: Stefan Eggers <seggers@semyam.dinoco.de>
Reply-To: seggers@semyam.dinoco.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: fd0 read access panics after unsuccessfull read on it
X-Send-Pr-Version: 3.2

>Number:         4760
>Category:       i386
>Synopsis:       fd0 read access panics after unsuccessfull read on it
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 13 22:40:00 PDT 1997
>Closed-Date:    Tue Oct 28 08:42:30 MET 1997
>Last-Modified:  Tue Oct 28 08:43:43 MET 1997
>Originator:     Stefan Eggers
>Release:        FreeBSD 2.2.2-RELEASE i386
>Organization:
>Environment:

Happens on an 386/33 without Cache (Cache is known not to work)
with a no-name I/O and FD/HD card.  The machine has 16 MByte RAM
and just an ISA bus system.

/dev/fd0 was renamed to /dev/fd0.default and /dev/fd0.720 to
/dev/fd0 to make mtools access 720 KByte floppies.

>Description:

fd0 driver can cause kernel panic.  The message was "isa_dmastart:
channel 2 bus 4" and afterward "fatal trap 9: general protection
fault while in kernel mode" with a lot of other information which
unfortunately I don't have in electronical form, yet.

>How-To-Repeat:

Try to do "mdir A:" w/o a disk in the floppy drive.  Now insert a
propperly formatted one (I used DD as /dev/fd0 was the 720 KByte
device) and try again.  The machine paniced.

>Fix:
	

>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: seggers@semyam.dinoco.de
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: i386/4760: fd0 read access panics after unsuccessfull read on it
Date: Tue, 14 Oct 1997 15:04:05 +0200

 As Stefan Eggers wrote:
 
 > >Release:        FreeBSD 2.2.2-RELEASE i386
 
 > >Description:
 > 
 > fd0 driver can cause kernel panic.  The message was "isa_dmastart:
 > channel 2 bus 4" and afterward "fatal trap 9: general protection
 > fault while in kernel mode" with a lot of other information which
 > unfortunately I don't have in electronical form, yet.
 
 Please verify that the problem still exists in 2.2.5-BETA.  One of
 the reasons for this kind of panics has been found and fixed by
 Bruce Evans quite some time ago.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)

From: Martin Kammerhofer <dada@sbox.tu-graz.ac.at>
To: Stefan Eggers <seggers@semyam.dinoco.de>
Cc: FreeBSD problems <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: i386/4760: fd0 read access panics after unsuccessfull read on it
Date: Thu, 16 Oct 1997 13:48:12 +0200 (CEST)

 On Tue, 14 Oct 1997, Stefan Eggers wrote:
 > >Synopsis:       fd0 read access panics after unsuccessfull read on it
 > >Release:        FreeBSD 2.2.2-RELEASE i386
 > >Environment:
 > 
 > Happens on an 386/33 without Cache (Cache is known not to work)
 > with a no-name I/O and FD/HD card.  The machine has 16 MByte RAM
 > and just an ISA bus system.
 > 
 > /dev/fd0 was renamed to /dev/fd0.default and /dev/fd0.720 to
 > /dev/fd0 to make mtools access 720 KByte floppies.
 > 
 
 It's probably not related to your hardware or /dev/fd0* setup. I
 experienced the same panic on a VLB 486 when I tried to repeat it.
 Oh, it's FreeBSD 2.2.2 and mtools 3.0 with just one 1.44M floppy.
 
 Regards,
 	Martin
 

From: Martin Kammerhofer <dada@sbox.tu-graz.ac.at>
To: Stefan Eggers <seggers@semyam.dinoco.de>
Cc: FreeBSD problems <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: i386/4760: fd0 read access panics after unsuccessfull read on it
Date: Mon, 20 Oct 1997 00:03:28 +0200 (CEST)

 On Tue, 14 Oct 1997, Stefan Eggers wrote:
 
 > >Synopsis:       fd0 read access panics after unsuccessfull read on it
 > ....
 > device) and try again.  The machine paniced.
 > 
 After upgrading from mtools 3.0 to mtools 3.8 (from the ports collection)
 this bug apparently has gone, at least on my machine ;-)
 
 Regards,
 	Martin
 
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Tue Oct 28 08:42:30 MET 1997 
State-Changed-Why:  

Nobody seems to be able to reproduce it with a more recent system 
(i.e., after Bruce's fix). 
>Unformatted:
