From owner-freebsd-stable Thu Aug 22 5:50:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F368C37B401 for ; Thu, 22 Aug 2002 05:50:22 -0700 (PDT) Received: from sinfonix.rz.tu-clausthal.de (sinfonix.rz.tu-clausthal.de [139.174.2.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D13C43E77 for ; Thu, 22 Aug 2002 05:50:21 -0700 (PDT) (envelope-from Oliver.Biermann@tu-clausthal.de) Received: from interruptus.heim6.tu-clausthal.de (obie@interruptus.heim6.tu-clausthal.de [139.174.246.166]) by sinfonix.rz.tu-clausthal.de (8.9.3/8.9.3) with ESMTP id OAA08019 for ; Thu, 22 Aug 2002 14:50:19 +0200 (MET DST) Subject: ATA driver is doing a fallback to pio mode4 on Promise Ultra66 From: Oliver Biermann Reply-To: obie@bmarkt.de To: freebsd-stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 22 Aug 2002 14:50:19 +0200 Message-Id: <1030020619.1710.35.camel@interruptus.heim6.tu-clausthal.de> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I've Problems with the ATA driver in 4-STABLE (cvsupped the source today, but the problem exists for me since back to 4.6-RELEASE as far as I remember). The driver is doing a fallback from UDMA66 mode to PIO4 mode on my Promise Ultra66 controller. (On the onboard controller of my mainboard [UDMA100] and on my HighPoint UDMA66 controller this does not happen). Here are the messages I receive: Aug 22 14:05:56 interruptus /kernel: ad8: READ command timeout tag=0 serv=0 - resetting Aug 22 14:05:56 interruptus /kernel: ata4: resetting devices .. done Aug 22 14:06:06 interruptus /kernel: ad8: READ command timeout tag=0 serv=0 - resetting Aug 22 14:06:07 interruptus /kernel: ata4: resetting devices .. done Aug 22 14:06:16 interruptus /kernel: ad8: READ command timeout tag=0 serv=0 - resetting Aug 22 14:06:16 interruptus /kernel: ata4: resetting devices .. done Aug 22 14:06:26 interruptus /kernel: ad8: READ command timeout tag=0 serv=0 - resetting Aug 22 14:06:26 interruptus /kernel: usb1: scheduling overrun Aug 22 14:06:26 interruptus /kernel: usb0: scheduling overrun Aug 22 14:06:26 interruptus /kernel: usb1: scheduling overrun Aug 22 14:06:26 interruptus /kernel: usb0: scheduling overrun Aug 22 14:06:26 interruptus /kernel: ad8: trying fallback to PIO mode Aug 22 14:06:26 interruptus /kernel: ata4: resetting devices .. done Aug 22 14:06:36 interruptus /kernel: ad8: READ command timeout tag=0 serv=0 - resetting Aug 22 14:06:36 interruptus /kernel: ata4: resetting devices .. done The machine was booted 25 minutes ago, and I was listening to some music from this hdd via samba 2.2.5 on my windows box... I had this behaviour quite often in the last days: booting, ata-driver in UDMA66 mode and then after some time using the hdd a fallback to PIO4... I would say it's not a cable-problem, because I checked my cables and run the same configuration on the other controllers where all seems ok. here is my dmesg output: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.6-STABLE #0: Wed Aug 21 23:34:50 CEST 2002 root@interruptus.heim6.tu-clausthal.de:/usr/src/sys/compile/INTERRUPTUS Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (896.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 536805376 (524224K bytes) avail memory = 518537216 (506384K bytes) Preloaded elf kernel "kernel" at 0xc03b5000. netsmb_dev: loaded Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00f7810 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 5 isab0: at device 2.0 on pci0 isa0: on isab0 ohci0: mem 0xcfffe000-0xcfffefff irq 5 at device 2.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xcffff000-0xcfffffff irq 11 at device 2.3 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered atapci0: port 0xff00-0xff0f at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcm0: port 0xcc00-0xcc3f,0xd000-0xd0ff irq 12 at device 2.7 on pci0 fxp0: port 0xc800-0xc81f mem 0xcfe00000-0xcfefffff,0xbd9ff000-0xbd9fffff irq 11 at device 11.0 on pci0 fxp0: Ethernet address 00:08:c7:8c:3d:39 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0xbc00-0xbcff,0xc000-0xc003,0xc400-0xc407 irq 12 at device 13.0 on pci0 ata2: at 0xc400 on atapci1 atapci2: port 0xd400-0xd4ff,0xd800-0xd803,0xdc00-0xdc07 irq 12 at device 13.1 on pci0 ata3: at 0xdc00 on atapci2 atapci3: port 0xa800-0xa83f,0xac00-0xac03,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 mem 0xcffc0000-0xcffdffff irq 5 at device 15.0 on pci0 ata4: at 0xb800 on atapci3 ata5: at 0xb000 on atapci3 sym0: <896> port 0xa000-0xa0ff mem 0xc6000000-0xc6001fff,0xc8000000-0xc80003ff irq 11 at device 17.0 on pci0 sym0: No NVRAM, ID 7, Fast-40, SE, parity checking sym1: <896> port 0xa400-0xa4ff mem 0xca000000-0xca001fff,0xcc000000-0xcc0003ff irq 12 at device 17.1 on pci0 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking pcib1: on motherboard pci2: on pcib1 orm0: