From owner-freebsd-hardware Wed Nov 13 23:30:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA20602 for hardware-outgoing; Wed, 13 Nov 1996 23:30:24 -0800 (PST) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA20583 for ; Wed, 13 Nov 1996 23:30:20 -0800 (PST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.12/8.6.9) id IAA27917; Thu, 14 Nov 1996 08:29:39 +0100 From: Thomas Gellekum Message-Id: <199611140729.IAA27917@ghpc6.ihf.rwth-aachen.de> Subject: Re: broken floppy driver To: robsch@robkaos.ruhr.de (Robert Schien) Date: Thu, 14 Nov 1996 08:29:38 +0100 (MET) Cc: j@uriah.heep.sax.de, freebsd-hardware@FreeBSD.org In-Reply-To: from Robert Schien at "Nov 13, 96 06:46:29 pm" Organization: Institut f. Hochfrequenztechnik, RWTH Aachen X-Mailer: ELM [version 2.4ME+ PL11 (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 Robert Schien wrote: > > As David Greenman wrote: > > > > > 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. > > BTW, the panic is produced my a general protection fault while in kernel mode. 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. tg