Date: Wed, 28 Jun 2006 22:55:36 -0300 (ADT) From: User Freebsd <freebsd@hub.org> To: Jonathan Noack <noackjr@alumni.rice.edu> Cc: freebsd-stable@freebsd.org Subject: Re: Expensive timeout? Message-ID: <20060628225524.Q43909@ganymede.hub.org> In-Reply-To: <44A32939.8040104@alumni.rice.edu> References: <20060628211703.Y43909@ganymede.hub.org> <20060628211837.L43909@ganymede.hub.org> <44A32939.8040104@alumni.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060628225524.Q43909>