From owner-freebsd-current@FreeBSD.ORG  Wed Nov 10 10:35:40 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 7C3AC16A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 10 Nov 2004 10:35:40 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E99A43D2D
	for <freebsd-current@freebsd.org>;
	Wed, 10 Nov 2004 10:35:40 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAAAYQ3w073776;
	Wed, 10 Nov 2004 05:34:26 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iAAAYQPh073773;
	Wed, 10 Nov 2004 10:34:26 GMT
	(envelope-from robert@fledge.watson.org)
Date: Wed, 10 Nov 2004 10:34:26 +0000 (GMT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
In-Reply-To: <4191E21C.5040307@DeepCore.dk>
Message-ID: <Pine.NEB.3.96L.1041110102656.60848Y-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
cc: Zoltan Frombach <tssajo@hotmail.com>
cc: freebsd-current@freebsd.org
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2004 10:35:40 -0000


On Wed, 10 Nov 2004, S=F8ren Schmidt wrote:

> > I'm still a bit skeptical that the task queue is at fault -- I run my
> > notebook with continuous measurement of the latency to schedule tasks,
> > generating a warning for any latency > .5 seconds, and the only time I
> > ever see that sort of latency is during the boot process when ACPI has
> > scheduled a task to run, but the task queue thread has not yet been
> > allowed to run:
>=20
> Right, the timeout is 5 secs. I havn't looked into how the taskqueues
> are handled recently, but in case of ATA read/writes it is the
> bio_taskqueue handled by geom thats in use not the catchall ones, does
> your timing cover that as well?=20

Nope -- I had assumed that the suggested task problems in question was the
use of taskqueue_enqueue() in ata-queue for the timeout, rather than the
bio_taskqueue() ata_completed() call.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research