From owner-freebsd-current Thu Jul 19 14:30: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from oahu.WURLDLINK.NET (oahu.WURLDLINK.NET [216.235.52.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F35D37B403 for ; Thu, 19 Jul 2001 14:29:59 -0700 (PDT) (envelope-from vince@oahu.WURLDLINK.NET) Received: from localhost (vince@localhost) by oahu.WURLDLINK.NET (8.11.3/8.11.3) with ESMTP id f6JLTlk41135; Thu, 19 Jul 2001 11:29:47 -1000 (HST) (envelope-from vince@oahu.WURLDLINK.NET) Date: Thu, 19 Jul 2001 11:29:46 -1000 (HST) From: Vincent Poy To: David Wolfskill Cc: Subject: Re: -current kernel hangs? In-Reply-To: <200107191321.f6JDLKu69528@bunrab.catwhisker.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Thu, 19 Jul 2001, David Wolfskill wrote: > >Date: Thu, 19 Jul 2001 02:48:10 -1000 (HST) > >From: Vincent Poy > > > With a July 18, 2001 sources, it seems like the kernel hands at > >the entropy harvesting stage.... ctrl-t shows: > > >load : 098 cmd : sycctl 51 [running] 4.51u 210.37s 0% 172k > > > It will just sit there forever until ctrl-c is hit. Anyone knows > >what's wrong? Thanks. > > This was discussed (to some extent) aboust a week & a half ago in -current. > It seems (pointed out by Alexander Leidinger ) > that -- for some of us, at least -- "sysctl -a" (used in the entropy > harvesting by /etc/rc -- fails to terminate. > > Also (again, for me) "sysctl -N -a" outputs a (non-terminating) stream of > > net.inet.accf.373 > > lines using my (slightly customized) kernel, but with GENERIC, it exhibits > similar behavior, but outputs a stream of > > net.inet.accf.372 > > lines. > > > Unfortunately, I'm not sufficiently clueful to figure out how the notion > of what sysctls exist on the system could get so confused as to do that. > > Given the behavior, though, my current (wild) guess is that some code is > stomping on a data structure in a somewhat configuration-dependent way. > > Clues would be quite welcome.... Interesting... I just didn't see anyone mention it this week so I thought it was fixed already but is there a work around this so ctrl-c doesn't have to be hit on each reboot? Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message