From owner-freebsd-current@FreeBSD.ORG Thu Jun 9 05:21:27 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 39D5D16A41C; Thu, 9 Jun 2005 05:21:27 +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 F35B343D1F; Thu, 9 Jun 2005 05:21:26 +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 7170A46B8A; Thu, 9 Jun 2005 01:21:26 -0400 (EDT) Date: Thu, 9 Jun 2005 06:22:33 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: <20050608205912.I16943@mail.chesapeake.net> Message-ID: <20050609062151.Y1075@fledge.watson.org> References: <20050609010700.V95135@fledge.watson.org> <20050608205912.I16943@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: glebius@freebsd.org, current@freebsd.org Subject: Re: 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 05:21:27 -0000 On Wed, 8 Jun 2005, Jeff Roberson wrote: >> 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. > > If you save a ktrdump right when that message is generated it'll be easy > to understand if other threads are interfering. Unfortunately, I'm not sure how reproduceable this is. I've only had it that one time, but will keep an eye out for it again. Robert N M Watson