From owner-freebsd-bugs Wed Jan 29 10:31:54 2003 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D241037B401 for ; Wed, 29 Jan 2003 10:31:52 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BA4543F79 for ; Wed, 29 Jan 2003 10:31:52 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0TIVpNt005129; Wed, 29 Jan 2003 10:31:51 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0TIVpwT005128; Wed, 29 Jan 2003 10:31:51 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Wed, 29 Jan 2003 10:31:50 -0800 From: David Schultz To: jjramsey@pobox.com Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Revisiting the semirandom bug/issue in FreeBSD's ATA querying Message-ID: <20030129183150.GB3139@HAL9000.homeunix.com> Mail-Followup-To: jjramsey@pobox.com, freebsd-bugs@FreeBSD.ORG References: <20030129015852.GB1989@HAL9000.homeunix.com> <20030129142553.22666.qmail@web10708.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030129142553.22666.qmail@web10708.mail.yahoo.com> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thus spake James J. Ramsey : > --- David Schultz > wrote: > > That's absolutely bizarre. So the problem happens > > *only* on > > FreeBSD, and only when you use bad cables *and* have > > two devices > > on the controller. Well, thanks for being patient > > about it. So it sounds like the problem is specific to the CDROM drive and ATA66 cables. But even if the drive doesn't support ATA66, that shouldn't screw up the probe... > I'm not so sure the cables are even bad. I've tried > two different ATA66 cables and can reproduce the > problem using either one of them. I doubt that *both* > of them are bad. > > On the bright side, the problem seems to be narrowed > down some. :) > > Sidenote: After actually *seeing* an ATA33 cable, I > can tell that both the cables I had been using (before > doing my most recent test) were for ATA66. I hadn't > realized before that the difference between an ATA33 > and an ATA66 cable was so obvious (I found out that > ATA33 cable wires are fatter.) The ATA66 cables have 80 conductors instead of 40, but still only 40 pins. There is a slight electrical difference that each device uses to detect (sometimes incorrectly) whether the cables are ATA66 or not. The ATA spec requires that for this to work, it is necessary to first probe the slave, and then the master, which the FreeBSD driver does. No delay is supposed to be required between probing the slave and probing the master, other than waiting for the command to complete, but the Linux driver has one anyway. I don't understand ATA very well, but perhaps that has something to do with the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message