From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 9 16:35:32 2006 Return-Path: X-Original-To: hardware@freebsd.org Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFA6C16A420; Thu, 9 Mar 2006 16:35:32 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A46B543D48; Thu, 9 Mar 2006 16:35:32 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 4DA6A1A4D9B; Thu, 9 Mar 2006 08:35:32 -0800 (PST) Date: Thu, 9 Mar 2006 08:35:32 -0800 From: Alfred Perlstein To: re@freebsd.org, sos@freebsd.org, hardware@freebsd.org Message-ID: <20060309163532.GH23971@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: ATA problems with 5.5-PRERELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2006 16:35:33 -0000 Hello, we recently began deploying 5.5-PRERELEASE dated March 7th. Across all (7 so far) of our machines we're getting the following error: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=32176383 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15514623 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=34480383 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=31408319 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=15718783 On FreeBSD 5.4-stable from September we were fine. This is the ata hardware present: atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 38166MB [77545/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 >From mysql on one of the hosts: 060309 5:28:48 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:29:40 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:02 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:30:14 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' 060309 5:34:40 [ERROR] Got error 134 when reading table './romatch/profile_acti ve' #define HA_ERR_RECORD_DELETED 134 /* Intern error-code */ Looks like we were getting corrupt data. Any hints? Can this be looked into please? -- - Alfred Perlstein - CTO Okcupid.com / FreeBSD Hacker / All that jazz -