From owner-freebsd-bugs  Thu Oct 16 05:00:06 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA23647
          for bugs-outgoing; Thu, 16 Oct 1997 05:00:06 -0700 (PDT)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA23622;
          Thu, 16 Oct 1997 05:00:02 -0700 (PDT)
          (envelope-from gnats)
Date: Thu, 16 Oct 1997 05:00:02 -0700 (PDT)
Message-Id: <199710161200.FAA23622@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Martin Kammerhofer <dada@sbox.tu-graz.ac.at>
Subject: Re: i386/4760: fd0 read access panics after unsuccessfull read on it
Reply-To: Martin Kammerhofer <dada@sbox.tu-graz.ac.at>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR i386/4760; it has been noted by GNATS.

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