From owner-freebsd-hardware  Sun Nov 10 02:38:11 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA29229
          for hardware-outgoing; Sun, 10 Nov 1996 02:38:11 -0800 (PST)
Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [193.100.176.38])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA29223
          for <freebsd-hardware@freebsd.org>; Sun, 10 Nov 1996 02:38:02 -0800 (PST)
Received: by mail.ruhrgebiet.individual.net (8.7.1/8.6.12) with UUCP id LAA15597 for freebsd.org!freebsd-hardware; Sun, 10 Nov 1996 11:32:45 +0100 (MET)
Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1)
	id <m0vMXAu-00061sC@robkaos.ruhr.de>; Sun, 10 Nov 96 11:31 MET
Message-Id: <m0vMXAu-00061sC@robkaos.ruhr.de>
From: robsch@robkaos.ruhr.de (Robert Schien)
Subject: Floppy broken in SNAP-2.2-961014 ?
To: freebsd-hardware@freebsd.org
Date: Sun, 10 Nov 1996 11:31:36 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

When I read a floppy (doesn't matter if 1.44 or 1.2 M) which
has some errors on it, so that error messages appear on the console
the kernel panics after entering the next command. 
(message: dma channel busy. ) If the floppy is perfectly good then
all goes well.
This behaviour appeared in the SNAP of Oct, 14. In earlier
releases the floppy worked perfectly.

I noticed this yesterday while browsing through a bunch of
old floppies.

Is this error fixed meanwhile?

TIA
Robert