From owner-freebsd-current@FreeBSD.ORG Thu Jun 9 00:10:29 2005 Return-Path: X-Original-To: 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 3B90716A41C; Thu, 9 Jun 2005 00:10:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08D6343D1F; Thu, 9 Jun 2005 00:10:28 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 899D246BB0; Wed, 8 Jun 2005 20:10:28 -0400 (EDT) Date: Thu, 9 Jun 2005 01:11:33 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: glebius@FreeBSD.org Message-ID: <20050609010700.V95135@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: link state changes take a "long" time to execute X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 09 Jun 2005 00:10:29 -0000 I'm running with task queue instrumentation on my notebook, and generate warnings when task queues take more than 1/10th of a second to execute. Normally the warnings fire only during the boot when tasks start being scheduled by ACPI, but the ACPI task queue thread isn't yet being scheduled to run because the scheduler hasn't been kicked off yet. I saw one this afternoon as follows: taskqueue_run: warning, queue time of 0.133978201 for context 0xc0687c90 On my kernel, this function pointer resolves to: c0687c90 t do_link_state_change So it sounds like there's a substantial delay in the link change thread -- probably because another task takes a long time to execute, maybe blocking or delaying the task thread and preventing another task from running. On this box, I'm running with an idle if_xl, and an in-use if_wi, which probably went into the associated state about when the message was printed. Kernel source date is June 3. Robert N M Watson