From owner-freebsd-stable Thu Aug 22 12:24: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 8AA6C37BD0E for ; Thu, 22 Aug 2002 12:24:30 -0700 (PDT) Received: from spork.pantherdragon.org (spork.pantherdragon.org [206.29.168.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F2243E75 for ; Thu, 22 Aug 2002 12:24:29 -0700 (PDT) (envelope-from dmp@pantherdragon.org) Received: from sparx.pantherdragon.org (evrtwa1-ar10-4-61-252-210.evrtwa1.dsl-verizon.net [4.61.252.210]) by spork.pantherdragon.org (Postfix) with ESMTP id 6D0BC1005F; Thu, 22 Aug 2002 12:01:34 -0700 (PDT) Received: from pantherdragon.org (speck.techno.pagans [172.21.42.2]) by sparx.pantherdragon.org (Postfix) with ESMTP id 7096FAB39; Thu, 22 Aug 2002 12:01:30 -0700 (PDT) Message-ID: <3D65350A.42B4331B@pantherdragon.org> Date: Thu, 22 Aug 2002 12:01:30 -0700 From: Darren Pilgrim X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obie@bmarkt.de Cc: freebsd-stable@freebsd.org Subject: Re: ATA driver is doing a fallback to pio mode4 on Promise Ultra66 References: <1030020619.1710.35.camel@interruptus.heim6.tu-clausthal.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Oliver Biermann wrote: > > 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: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. I've had similar problems myself from 4.2-R on, but only because I didn't have any ATA66+ hardware until after I was using at least 4.2-R everywhere. As long as the drive itself isn't a problem, switching controller/cable combinations has always removed the problem. It seems that heterogenous ATA66+ configurations with lots of drives is a crap-shoot at best. Have you tried swaping the cable out with a premium non-rounded ATA/100 cable (the kind you buy seperately for $20+ each)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message