Date: Wed, 13 Nov 1996 18:46:29 +0100 (MET) From: robsch@robkaos.ruhr.de (Robert Schien) To: j@uriah.heep.sax.de (J Wunsch) Cc: freebsd-hardware@freebsd.org Subject: Re: broken floppy driver Message-ID: <m0vNjOQ-00061sC@robkaos.ruhr.de> In-Reply-To: <199611131359.OAA24940@uriah.heep.sax.de> from J Wunsch at "Nov 13, 96 02:59:25 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0vNjOQ-00061sC>