From owner-freebsd-bugs Sun Jul 1 19: 0:15 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A3D5037B405 for ; Sun, 1 Jul 2001 19:00:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f6220CA37505; Sun, 1 Jul 2001 19:00:12 -0700 (PDT) (envelope-from gnats) Date: Sun, 1 Jul 2001 19:00:12 -0700 (PDT) Message-Id: <200107020200.f6220CA37505@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Gregory Bond Subject: Re: kern/28616: ATA probe problem with VIA 82C686 Reply-To: Gregory Bond 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 The following reply was made to PR kern/28616; it has been noted by GNATS. From: Gregory Bond To: Alec Wolman Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/28616: ATA probe problem with VIA 82C686 Date: Mon, 02 Jul 2001 11:55:35 +1000 > ata0: mask=03 ostat0=a0 ostat2=b0. > The delay appears to be occuring in the loop in the ata_reset() > subroutine - the busy bit is always set so we just keep going > through the loop. This occurs because the initial status0 and > status1 values are 0xa0 and 0xb0, which is clearly not what the > ata driver expects to see when there are no devices present. I found a similar thing probing ata1 with quite different hardware (old P-100 system from a long-defunct manufacturer) with: disk on ata0-master CD-ROM on ata0-slave disk on ata1-master no ata1-slave I just put it down to errors in the ATA BIOS and learned to put up with it. If it turns out to be a real bug, I can happily send any relevent info.... Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message