From owner-freebsd-stable@FreeBSD.ORG Tue Sep 6 01:28:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 7BDFD16A41F for ; Tue, 6 Sep 2005 01:28:19 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13F9F43D46 for ; Tue, 6 Sep 2005 01:28:18 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so971818wra for ; Mon, 05 Sep 2005 18:28:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EQ2+xG/BBn/5oo5t5ZU7taLY3emGaFeWWToJmM7OHHHkComSRidXmlalyXb/9pX7zjw55NFRlyg4dez3l0+Qkx+Yy2AnCJWIZelFZJira5ur3BYtQ/DOv9ofR5rkrvYvnsOfNxfXQYSTc/ipK7GgoQDQcA6w3bFiLbbxBDv7aHM= Received: by 10.54.56.77 with SMTP id e77mr4464958wra; Mon, 05 Sep 2005 18:28:17 -0700 (PDT) Received: by 10.54.154.14 with HTTP; Mon, 5 Sep 2005 18:28:17 -0700 (PDT) Message-ID: <35de0c30050905182851e63376@mail.gmail.com> Date: Mon, 5 Sep 2005 21:28:17 -0400 From: Bryan Fullerton To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: 6.0BETA3 - READ_DMA timeouts on UDMA33 drive? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2005 01:28:19 -0000 Howdy, I've been tracking 6.0BETA on a P3/450 machine that's been running extremely solidly for several years. I've been cvsup'ing and rebuilding once a week or so. It's not a hugely busy machine, just has a squid cache and DNS for my home network and storage of remote backups. After an update to 6.0BETA3 as of last week I've started seeing intermittant READ_DMA timeout errors (warnings?) from a standard UDMA33 drive. I'm building BETA4 now and will see if that still has problems. Aug 31 00:55:25 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D33212179 Aug 31 00:58:58 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D18832671 Aug 31 02:21:49 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D12707583 Aug 31 05:55:41 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D30539199 Aug 31 20:24:29 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D2663743 Aug 31 20:55:46 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D17535935 Aug 31 20:58:06 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D1371539 Sep 1 00:48:14 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D17523487 Sep 1 07:26:19 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D75323491 Sep 1 08:19:52 katana kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=3D9808191 ATA related items from dmesg: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xb800-0xb80f at device 4.1 on pci0 ata0: on atapci0 ata1: on atapci0 ad0: 39266MB at ata0-master UDMA33 ad1: 29314MB at ata0-slave UDMA33 acd0: CDRW at ata1-master PIO4 Any ideas what's up with that? Are these errors or warnings? Is this something that's always been happening but wasn't being reported before, or something being erroneously reported? smartmontools reports that ad0 has zero SMART errors or failures, so it doesn't appear to be an issue with the drive itself. A short SMART test also passes with no errors. Thanks, Bryan