From owner-freebsd-hardware  Thu Nov 14 01:14:13 1996
Return-Path: owner-hardware
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA25442
          for hardware-outgoing; Thu, 14 Nov 1996 01:14:13 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA25437
          for <freebsd-hardware@FreeBSD.org>; Thu, 14 Nov 1996 01:14:06 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA06709; Thu, 14 Nov 1996 20:10:24 +1100
Date: Thu, 14 Nov 1996 20:10:24 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199611140910.UAA06709@godzilla.zeta.org.au>
To: robsch@robkaos.ruhr.de, thomas@ghpc8.ihf.rwth-aachen.de
Subject: Re: broken floppy driver
Cc: freebsd-hardware@FreeBSD.org, j@uriah.heep.sax.de
Sender: owner-hardware@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>I have the same problem (dma channel 2 busy) and the occasional panic
>(2.2-961014-SNAP). No more details currently, the machine is at home
>and I wanted to try to get more information first.
>
>BTW, I'm sure the floppies I feed my drive are good; written here at
>work on a 2.1.0-machine and I can read them back without problems.

The message "isa_dmastart: channel 2 busy" is normal after floppy i/o
errors.  It is caused by the fd driver's poor error handling.  This
shouldn't cause a panic.  However, syscons' and probably pcvt's output
routines are not reentrant, so its quite possible for interrupting
normal console i/o to print a panic message to cause a panic :-(.

Bruce