From owner-freebsd-bugs Wed Jan 29 6:25:56 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 AD68E37B401 for ; Wed, 29 Jan 2003 06:25:54 -0800 (PST) Received: from web10708.mail.yahoo.com (web10708.mail.yahoo.com [216.136.130.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 3FC2143F3F for ; Wed, 29 Jan 2003 06:25:54 -0800 (PST) (envelope-from jjramsey_6x9eq42@yahoo.com) Message-ID: <20030129142553.22666.qmail@web10708.mail.yahoo.com> Received: from [66.219.135.59] by web10708.mail.yahoo.com via HTTP; Wed, 29 Jan 2003 06:25:53 PST Date: Wed, 29 Jan 2003 06:25:53 -0800 (PST) From: "James J. Ramsey" Reply-To: jjramsey@pobox.com Subject: Re: Revisiting the semirandom bug/issue in FreeBSD's ATA querying To: freebsd-bugs@freebsd.org In-Reply-To: <20030129015852.GB1989@HAL9000.homeunix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 --- David Schultz wrote: > Thus spake James J. Ramsey > : > > --- "Wojciech S. Czarnecki" wrote: > > > James J. Ramsey wrote: > > > [on Thu, Jan 23, 2003 at 05:01:05PM -0800] > > > (>) Owego dnia James J. Ramsey napisał(a): > > > > ad0: 8866663634010175MB > > > > > > > > [16955114026566160/17/63] at ata0-master PIO4 > > > Check cables twice. > > > For the test: change cable to ATA33 (40wire) > cable. > > > > I did this and could not get FreeBSD to fail. The > > kernel messages were nice and healthy-looking: > > > > ad0: DMA limited to UDMA33, non-ATA66 cable or > device > > ad0: 19595MB > [39813/16/63] > > at ata0-master UDMA33 > > > > (The hard drive was primary master, and my CD-ROM > > primary slave.) > > 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. 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.) __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message