From owner-freebsd-hardware Wed Nov 13 10:08:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA02844 for hardware-outgoing; Wed, 13 Nov 1996 10:08:46 -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 KAA02831 for ; Wed, 13 Nov 1996 10:08:35 -0800 (PST) Received: by mail.ruhrgebiet.individual.net (8.7.1/8.6.12) with UUCP id SAA01420; Wed, 13 Nov 1996 18:51:21 +0100 (MET) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Wed, 13 Nov 96 18:46 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: broken floppy driver In-Reply-To: <199611131359.OAA24940@uriah.heep.sax.de> from J Wunsch at "Nov 13, 96 02:59:25 pm" To: j@uriah.heep.sax.de (J Wunsch) Date: Wed, 13 Nov 1996 18:46:29 +0100 (MET) Cc: freebsd-hardware@freebsd.org 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 > 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. > > Robert has been reporting this to me previously, but he seems to > be the only one with this phenomenon, and i haven't seen a floppy- > caused panic for at least a year now. Of course, i'm heavily > stress-testing with known-to-be-broken floppies myself... > > Robert, any more data on this? Can you get a kernel dump out of > this, or a DDB traceback? > Of course, but how can one produce a kernel dump or a DDB traceback? I haven't done such things before. BTW, the panic is produced my a general protection fault while in kernel mode. Robert