From owner-freebsd-hackers Thu Jun 12 08:15:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA02019 for hackers-outgoing; Thu, 12 Jun 1997 08:15:53 -0700 (PDT) Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA02013 for ; Thu, 12 Jun 1997 08:15:51 -0700 (PDT) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA12116 for ; Thu, 12 Jun 1997 08:15:35 -0700 (PDT) Received: (qmail 6347 invoked by uid 128); 12 Jun 1997 15:15:21 -0000 Date: 12 Jun 1997 15:15:21 -0000 Message-ID: <19970612151521.6346.qmail@squirrel.tgsoft.com> From: mark thompson To: hackers@freebsd.com Subject: floppy, redux Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I wrote some time back about problems with my floppy... how it regularly writes and reads without reporting errors, but the data is incorrect. Well, i have now looked at it a bit more and the problem is not that the data is "wrong" (ie. the bits were written/read incorrectly), but that the data has been scrambled (little strings of otherwise "correct" data written in the wrong places in the file). It appears that the data which has moved to the wrong places is "near" to where it should be, implying that it was probably part of a single write/read. This scrambling appears to occur on both reads and writes, since the data on the disk is wrong, and the data that i read back is more wrong. For other reasons, i have replaced the floppy cable. The drive itself would seem innocent, since it pretty much is just a record/playback device. The floppy controller/DMA unit comes in for suspicion. Unfortunately, this started shortly after going to 2.2.1 from 2.1.7, so i also suspect the driver. I am hoping that all of this will suggest something to one of the experts out there, because otherwise i fear it will be mondo difficult to track down. -mark