Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!netnews.upenn.edu!dsinc!spool.mu.edu!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!bakul From: bakul@netcom.com (Bakul Shah) Subject: Re: FreeBSD, fd0d: hard error Message-ID: <bakulCvsBzq.KuH@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <33j9hp$41l@sol.sun.csd.unb.ca> <jmonroyCvozLK.5q9@netcom.com> <bakulCvpyuw.5nB@netcom.com> <34k55j$krm@kralizec.zeta.org.au> Date: Thu, 8 Sep 1994 00:28:38 GMT Lines: 20 bde@kralizec.zeta.org.au (Bruce Evans) writes: >Yes, it looks like a normal floppy media error. However, then fsbn 62 >outside the range 64-71 does not inspire confidence in the relevance >of the error message. The version of the fd driver just before 1.1.5 >came out printed completely bogus fsbn's in error messages but I think >that was fixed. Sigh.... If the error message is incorrect it is useless to speculate on how to fix the problem. The three status register values seem consistent with each other, though. >gap1 is 0x1B for 1.2M and 1.44M. This is normal. I think there's >a write timing bug somewhere else. Writes sometimes appear to >succeed, but the disk becomes unreadable. Thanks for the correction. Write timing bug sounds strange... 765A requires handshaking on pretty much everything.... Bakul Shah