From owner-freebsd-stable@FreeBSD.ORG Thu Jun 29 13:43:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 074D316A403 for ; Thu, 29 Jun 2006 13:43:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C6A843D46 for ; Thu, 29 Jun 2006 13:43:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E21C546C3B; Thu, 29 Jun 2006 09:43:23 -0400 (EDT) Date: Thu, 29 Jun 2006 14:43:23 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: User Freebsd In-Reply-To: <20060628225524.Q43909@ganymede.hub.org> Message-ID: <20060629144146.R30355@fledge.watson.org> References: <20060628211703.Y43909@ganymede.hub.org> <20060628211837.L43909@ganymede.hub.org> <44A32939.8040104@alumni.rice.edu> <20060628225524.Q43909@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Expensive timeout? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 13:43:28 -0000 On Wed, 28 Jun 2006, User Freebsd wrote: > On Wed, 28 Jun 2006, Jonathan Noack wrote: > >> Please don't top-post... >> >> User Freebsd wrote: >>> On Wed, 28 Jun 2006, User Freebsd wrote: >>>> Just got this on the console of one of hte servers that has been causing >>>> problems ... >>>> >>>> Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s >>>> >>>> not a very informative error, and that is all that was there, nothing >>>> before, nothing after ... >>> >>> Oh, wait, does this have something to do with the Deadlock options I just >>> added to the kernel? >> >> Yes, if you look in /sys/kern/kern_timeout.c you'll note that the >> "Expensive timeout(9) function" printf is inside an "#ifdef DIAGNOSTIC". > > 'k, but is this something that I should be concerned about, or just ignore? You can convert it to a function name using the addr2line command combining the function pointer, 0xc0520e18, with your kernel.debug, then let us know. This is an advisory diagnostic message to let developers know a kernel function running in a time-critical path is taking too long to run, and is worth reporting. You probably don't want to run with DIAGNOSTIC unless you really want to. INVARIANTS+WITNESS are sufficient for most debugging. Robert N M Watson Computer Laboratory University of Cambridge