Date: Wed, 21 May 1997 08:21:52 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-chat@freebsd.com Cc: thompson@squirrel.tgsoft.com (mark thompson) Subject: Re: floppy flaky Message-ID: <19970521082152.SV25872@uriah.heep.sax.de> In-Reply-To: <19970520132403.10028.qmail@squirrel.tgsoft.com>; from mark thompson on May 20, 1997 13:24:03 -0000 References: <19970520085019.JZ36841@uriah.heep.sax.de> <19970520132403.10028.qmail@squirrel.tgsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As mark thompson wrote: > Writing a floppy can only detect catastrophic errors (sector marks not > found). Data-field only errors remain undetected. > True. But the read should detect a bad checksum, not just return bad > bits, nicht wahr? It will only detect the bad CRC if the FDC correctly announces it. If your FDC is broken and doesn't report an error, there's not much the driver could do. For me, the FDC detects more errors than i would ever love to see :), basically proving the driver works correctly here: uriah /kernel: fd0c: hard error reading fsbn 0 (ST0 40<abnrml> ST1 1<no_am> ST2 0 cyl 0 hd 0 sec 1) This was a missing mark in the address (aka. ID) field. A missing address mark in the data field would return <no_am> for both, ST1 and ST2. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970521082152.SV25872>