From owner-freebsd-questions Thu Jan 2 10:43:31 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985BC37B47C; Thu, 2 Jan 2003 10:43:27 -0800 (PST) Received: from level.uwaterloo.ca (level.uwaterloo.ca [129.97.50.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB1943EA9; Thu, 2 Jan 2003 10:43:26 -0800 (PST) (envelope-from bruce@engmail.uwaterloo.ca) Received: from level.uwaterloo.ca (localhost [127.0.0.1]) by level.uwaterloo.ca (8.12.3/8.12.3) with ESMTP id h02Ig35n071399; Thu, 2 Jan 2003 13:42:03 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) Received: (from www@localhost) by level.uwaterloo.ca (8.12.3/8.12.3/Submit) id h02Ig3ka071398; Thu, 2 Jan 2003 13:42:03 -0500 (EST) X-Authentication-Warning: level.uwaterloo.ca: www set sender to bruce@engmail.uwaterloo.ca using -f Received: from 129.97.50.50 ( [129.97.50.50]) as user bruce@engmail.uwaterloo.ca by www.nexusmail.uwaterloo.ca with HTTP; Thu, 2 Jan 2003 13:42:03 -0500 Message-ID: <1041532923.3e1487fb50a0e@www.nexusmail.uwaterloo.ca> Date: Thu, 2 Jan 2003 13:42:03 -0500 From: Bruce Campbell To: Francesco Casadei Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <20030102163812.GA2350@goku.kasby> In-Reply-To: <20030102163812.GA2350@goku.kasby> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 / FreeBSD-4.6.2 X-Originating-IP: 129.97.50.50 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quoting Francesco Casadei : > On Tue, Dec 31, 2002 at 03:57:16PM -0500, Bruce Campbell wrote: > > > > I am seeing a problem with ata disks on 4 new systems, which > > I believe is either a bug in the ata driver, or a problem with > > the onboard IDE controller, or something else. Systems are as follows: > > ... > > Motherboard: ASUS A7M266-D > > CPUs : 2 x 2000+ AMD MP > > Memory : 2 x 512MB Crucial part: CT6472Y265 > > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > - > > resetting > > Dec 30 23:26:59 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ad0: timeout waiting for cmd=ef s=d0 > e=00 > > Dec 30 23:27:00 ecserv13 /kernel: ad0: trying fallback to PIO mode > > Same problem here, but slightly different configuration: > > # atacontrol list > ATA channel 0: > Master: ad0 ATA/ATAPI rev 5 > Slave: no device present > ATA channel 1: > Master: acd0 ATA/ATAPI rev 0 > Slave: no device present > ATA channel 2: > Master: ad4 ATA/ATAPI rev 5 > Slave: no device present > ATA channel 3: > Master: ad6 ATA/ATAPI rev 5 > Slave: no device present > > ad4 and ad6 are attached to a Promise FastTrak 100 TX2 ATA RAID controller. > > # atacontrol mode 0 > Master = UDMA100 > Slave = ??? > > # atacontrol mode 1 > Master = PIO4 > Slave = ??? > > # atacontrol mode 2 > Master = UDMA100 > Slave = ??? > > # atacontrol mode 3 > Master = PIO4 > Slave = ??? > > ad6 falls back to PIO mode on heavy I/O activity, i.e. when the system does > a > level 0 file systems dump from the RAID 1 array (ad4,ad6) to the backup disk > ad0. > Rebooting and rebuilding the array with the Promise BIOS utility temporarily > solve the problem. The system may be up and running for 1-4 weeks doing a > level 0 dump every morning at 5:30am and then one day the drive ad6 falls > back > to PIO mode again (little before the completion of fs dump). > > Do the hard drives you are using support the ATA tagged queuing? And if so, > do > you have TQ enbled? I don't have it enabled: hw.ata.tags: 0 I've manually set: atacontrol mode 0 UDMA33 UDMA33 and the problem has not recurred. -- Bruce Campbell Engineering Computing CPH-2374B University of Waterloo (519)888-4567 ext 5889 ---------------------------------------- This mail sent through www.mywaterloo.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message