From owner-freebsd-hackers Fri Sep 12 16:12:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17086 for hackers-outgoing; Fri, 12 Sep 1997 16:12:31 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA17068 for ; Fri, 12 Sep 1997 16:12:25 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id IAA04680; Sat, 13 Sep 1997 08:42:14 +0930 (CST) Message-ID: <19970913084213.18186@lemis.com> Date: Sat, 13 Sep 1997 08:42:13 +0930 From: Greg Lehey To: Joerg Wunsch Cc: FreeBSD Hackers Subject: Re: Do *you* have problems with floppies? References: <19970912101014.37786@lemis.com> <19970912154815.HN39525@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970912154815.HN39525@uriah.heep.sax.de>; from J Wunsch on Fri, Sep 12, 1997 at 03:48:15PM +0200 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Sep 12, 1997 at 03:48:15PM +0200, J Wunsch wrote: > As Greg Lehey wrote: > >> I've seen a lot of reports recently about problems with floppies under >> FreeBSD. Now I can understand a lot of that: floppies must be the >> most unreliable data storage medium I can think of, not to mention the >> most expensive per byte. But I'm getting the feeling that there is >> more to it than that, that possibly there's a bug in the floppy driver >> and that we're blaming it on the inherent unreliability of the medium. > > Oh, Greg is going to take over maintenance of the FDC driver! > Congratulations! :-) Look carefully. I'm just gathering information: >> I'm looking for indications which would point towards the driver. One >> of these might be: >> >> 1. Floppy formatted under on the same machine. >> 2. FreeBSD runs into hardware problems with the floppy (typically >> things like checksum errors). >> 3. can read the entire floppy with no trouble. > > There's exactly one unexplained record open where 1 - 3 does fit, and > i have yet to see more user input data for this case (or have to get > the drive and floppy controller myself for debugging). There are more now. > Greg, please think a little more about reported problems before > starting this kind of postings. What has been triggering this was > plainly and clearly something where a user had a problem with *the > BIOS* reading the floppy. This should say enough about the media > quality... Now there's the misassumption. I've already mentioned medium quality and the general unreliability. Ignoring that, it still seems that there are a significant number of cases where other systems can read the floppy, and FreeBSD can't. I've had them myself, though not on my current hardware. >> In addition, if you have any other evidence I haven't thought of which >> would also point to an error in the floppy driver, please contact me. > > Good luck for fixing these errors... Does this mean you don't want to maintain the driver any more? > And don't forget to verify your changes on at least half a dozen of > drives and controllers. That's one of the reasons I want to get a larger populace involved. Obviously you (or I) can't test all hardware. We need the people who have reported the problems to help. Unfortunately, so far the evidence isn't as exact as I would have liked. I know that this is a pain. Nobody says it isn't. But it doesn't help to turn a blind eye to possible driver problems and blame them on the medium. Note that I haven't claimed there *is* a problem with the driver yet--I'm just trying to get some evidence before going to look for a problem that doesn't exist. Greg