From owner-freebsd-current@FreeBSD.ORG Thu Nov 11 19:04:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EFF616A4CE for ; Thu, 11 Nov 2004 19:04:05 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE55243D53 for ; Thu, 11 Nov 2004 19:04:04 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iABJ43hL019838; Thu, 11 Nov 2004 14:04:04 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 11 Nov 2004 14:04:02 -0500 To: "Zoltan Frombach" , From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 19:04:05 -0000 At 7:58 PM -0800 11/9/04, Zoltan Frombach wrote: >Well, since I posted my original message, I investigated >this a bit further. And according to this post >http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027235.html >this is not necessarily an indication of a failing hard >drive... (Quote: "there is no harm done, but the taskqueue >was slow to respond...") And I can also tell you that this >very same hard drive *never* produced this error message in >the past 6 months while running FreeBSD 5.2-CURRENT (from >May 9, 2004). Fwiw, I am also seeing this warning/error message on a brand new machine with a brand new SATA hard disk in it. I have seen the message on multiple installs into different partitions on the same hard drive. I turned off some sysctl (hw.ata.ata_dma, *I think*) to see if that would avoid the problem, but it did not seem to. I usually do not notice any problem at the same time as the message, but I have seen a few buildworlds which just happened to abort at the same second this warning message appeared in /var/log/message. So, I am not sure the message is benign in all circumstances. I'm a bit busy with a variety of other issues right now, but I should have some time this coming weekend to run any tests or patches that might help to pin this down. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu