Date: Tue, 6 May 1997 19:14:39 +0200 (MET DST) From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: floppy related kernel messages Message-ID: <199705061714.TAA07066@gil.physik.rwth-aachen.de>
next in thread | raw e-mail | index | archive | help
In 3.0-current I'm seeing floppy problems on several machines. They're all manifesting in some kind of isa_dmastart: cannel 2 busy which seems to occur as the first message after an fdc error, e.g. door open or write locked with the next access after fixing the condition that led to the first error. In consequence of this I seemed to have had a system crash (reboot w/o panic) a couple of minutes ago. Here is an excerpt of my messages file: May 6 18:18:49 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:49 bach /kernel: fdc0: direction bit not set May 6 18:18:49 bach /kernel: fdc0: cmd e6 failed at out byte 1 of 9 May 6 18:18:49 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:49 bach /kernel: fd0c: hard error reading fsbn 0 (No status) May 6 18:18:49 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:49 bach /kernel: fdc0: direction bit not set May 6 18:18:49 bach /kernel: fdc0: cmd e6 failed at out byte 1 of 9 May 6 18:18:49 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:50 bach /kernel: fd0c: hard error reading fsbn 0 (No status) May 6 18:18:50 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:50 bach /kernel: fdc0: direction bit not set May 6 18:18:50 bach /kernel: fdc0: cmd e6 failed at out byte 1 of 9 May 6 18:18:50 bach /kernel: isa_dmastart: channel 2 busy May 6 18:18:50 bach /kernel: fd0c: hard error reading fsbn 0 (No status) May 6 18:20:18 bach /kernel: isa_dmastart: channel 2 busy -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705061714.TAA07066>