Date: Wed, 20 Sep 2000 00:10:03 -0700 (PDT) From: Soren Schmidt <sos@freebsd.dk> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/21410: ATA driver problems when UDMA66 is used with wrong cable Message-ID: <200009200710.AAA80050@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/21410; it has been noted by GNATS. From: Soren Schmidt <sos@freebsd.dk> To: john@nlc.net.au Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/21410: ATA driver problems when UDMA66 is used with wrong cable Date: Wed, 20 Sep 2000 09:12:07 +0200 (CEST) It seems john@nlc.net.au wrote: > > In the situation where a UDMA66 controller is available but the drive is > connected with the old style 33MHz cable, the BIOS detects that an 80 > pin cable is not present. However the ATA driver tries to negotiate > UDMA66 mode then fails with some nasty error messages, then drops to > PIO mode. > > Sep 19 20:57:26 pacer /kernel: ad0: UDMA ICRC READ ERROR blk# 0 retrying > Sep 19 20:57:26 pacer last message repeated 2 times > Sep 19 20:57:26 pacer /kernel: ad0: UDMA ICRC READ ERROR blk# 0ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA > Sep 19 20:57:27 pacer /kernel: falling back to PIO mode What did the driver say it set the drive to ?? Verbose boot dmesg please!! > Can the 80 pin cable be detected by the driver? If so then only try UDMA33 as the > first step. If not then upon an error, drop back to UDMA33 before PIO mode. Possibly > print an error message that the 80 pin cable may not be installed, or a device not > cable of UDMA66 is present. The ata driver does check for the type of cable used by asking the disks, however if the disks reports the wrong cable, well..... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009200710.AAA80050>