From owner-freebsd-bugs Sat Feb 1 8:17:33 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 70D8E37B405 for ; Sat, 1 Feb 2003 08:17:31 -0800 (PST) Received: from web10702.mail.yahoo.com (web10702.mail.yahoo.com [216.136.130.210]) by mx1.FreeBSD.org (Postfix) with SMTP id D51B243F75 for ; Sat, 1 Feb 2003 08:17:30 -0800 (PST) (envelope-from jjramsey_6x9eq42@yahoo.com) Message-ID: <20030201161730.64166.qmail@web10702.mail.yahoo.com> Received: from [66.219.135.59] by web10702.mail.yahoo.com via HTTP; Sat, 01 Feb 2003 08:17:30 PST Date: Sat, 1 Feb 2003 08:17:30 -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: <20030129191417.GA5337@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 > > > > I guess the next question is whether FreeBSD has a > > delay between probing of master and slave as Linux > > does. > > No, it doesn't, although the kernel image I sent you > a link to > earlier does. Alternatively, you can add one > yourself. The patch > below won't apply cleanly on -CURRENT, but it's easy > enough to add > the lines manually. > > Index: ata-all.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v > retrieving revision 1.50.2.42 > diff -p -u -r1.50.2.42 ata-all.c > --- src/sys/dev/ata/ata-all.c 2002/11/01 22:04:06 > 1.50.2.42 -- rest of patch not shown -- I've tried the patch and it seems to work. I've had no luck getting my patched kernel to fail to identify my hard drive, and I've tried repeatedly to do so. However, getting the GENERIC kernel to fail has not been so easy. To reproduce the failure, I've had to do my little trick of starting an install from a floppy and rebooting before committing, then booting the GENERIC kernel. That said, I haven't been able to trip the patched kernel the way I've been able to trip up the GENERIC one. So far, so good. Any ideas on how to test if the patch really works or if I've just been lucky so far? __________________________________________________ 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