From owner-freebsd-current Thu Dec 12 14:19:32 2002 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 74B3C37B401 for ; Thu, 12 Dec 2002 14:19:31 -0800 (PST) Received: from mailhost.nxad.com (lan.ext.nxad.com [66.250.180.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 220AE43ED1 for ; Thu, 12 Dec 2002 14:19:31 -0800 (PST) (envelope-from sean@nxad.com) Received: from perrin.int.nxad.com (perrin.int.nxad.com [192.168.1.251]) by mailhost.nxad.com (Postfix) with ESMTP id E0770212EEB; Thu, 12 Dec 2002 14:19:30 -0800 (PST) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id 8084021058; Thu, 12 Dec 2002 14:19:30 -0800 (PST) Date: Thu, 12 Dec 2002 14:19:30 -0800 From: Sean Chittenden To: Don Bowman Cc: current@FreeBSD.org Subject: Re: sysctl -a loops forever... Message-ID: <20021212221930.GE6097@perrin.int.nxad.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 6CEB 1B06 BFD3 70F6 95BE 7E4D 8E85 2E0A 5F5B 3ECB X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Anyone seen sysctl -a loop forever? I haven't been able to track > > down the MIB that it's gettinng hung up on, but it looks like > > there's a flaw in the algo that is walking through the MIBs. > > Given that this halts the machine while trying to collect entropy > > (sysctl -a is used to help feed /dev/random) at system start up, I > > think it's something worth addressing or pointing out. -sc > > I've observed this when e.g. I had too many nmbclusters configured, > ie when vm.kvm_free was too low (0 in my case :) Ah, hrm, I think you're onto something here. I haven't played with vm.kvm_free, but I do run with 65536 mbuf clusters. Hrm... this is outside of my expertise. I have 4.X boxes running with 130K mbuf clusters (and I actually need to find a way to increase this further!) so this is definately something I'll run into and likely others will when they update their production boxen. Is this a sysctl data presentation issue? -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message