From owner-freebsd-bugs Mon Jun 3 9: 7:22 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from refuge.Colorado.EDU (refuge.Colorado.EDU [128.138.196.38]) by hub.freebsd.org (Postfix) with ESMTP id 4D24B37B400 for ; Mon, 3 Jun 2002 09:07:09 -0700 (PDT) Received: from refuge.Colorado.EDU (orrie@localhost [127.0.0.1]) by refuge.Colorado.EDU (8.10.1/8.10.1/UnixOps+Hesiod) with ESMTP id g53G78D14948 for ; Mon, 3 Jun 2002 10:07:08 -0600 (MDT) Message-Id: <200206031607.g53G78D14948@refuge.Colorado.EDU> To: freebsd-bugs@freebsd.org Subject: ATA PIO problems with 4.5 Date: Mon, 03 Jun 2002 10:07:07 -0600 From: Orrie 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 Hi, We are having the following problem. Our system is the following: Gigabyte GA-7DPXDW motherboard AMD 760MPX chipset Promise Fasttrack 100 onboard IDE-RAID Athlon MP 1800+ 1GB PC2100 ECC ram We are running 4.5-RELEASE-p5. When our Maxtor 160GB disks are connected to the built-in onboard controller (NOT the Promise Fasttrack), we see transfer rates in the 80Megabit range as expected and the drives are in dma mode. When using the onboard Promise Fasttrack 100, the drives switch to PIO mode and our transfer rates are, obviously, way to slow to do much. We know the cables are fine since they have all been tested. This is the first machine we have with the Promise Fasttrack built on the board. Here is the ATA stuff from messages: atapci0: port 0xb000-0xb00f at device 7.1 on pci0 atapci1: port 0xa400-0xa43f,0xa000-0xa003,0x9c00-0x9 c07,0x9800-0x9803,0x9400-0x9407 mem 0xf4020000-0xf403ffff irq 10 at device 8.0 on pci2 ad0: 156334MB [317632/16/63] at ata0-master BIOSDMA ad1: 156334MB [317632/16/63] at ata0-slave BIOSDMA ad2: 156334MB [317632/16/63] at ata1-master BIOSDMA ad3: 156334MB [317632/16/63] at ata1-slave BIOSDMA ad6: 156334MB [317632/16/63] at ata3-master UDMA100 and the most common errors we receive are: ad1: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad1: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad1: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad1: WRITE command timeout tag=0 serv=0 - resetting ad1: trying fallback to PIO mode ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ad0: trying fallback to PIO mode ata0: resetting devices .. done Does anyone have any thoughts on what could be occuring? Orrie orrie@colorado.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message