From owner-freebsd-current@FreeBSD.ORG  Tue Oct 19 22:43:34 2004
Return-Path: <owner-freebsd-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 101F616A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 19 Oct 2004 22:43:34 +0000 (GMT)
Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com
	[209.20.186.192])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C307D43D2F
	for <freebsd-current@freebsd.org>;
	Tue, 19 Oct 2004 22:43:33 +0000 (GMT)	(envelope-from randy@psg.com)
Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com)
	by ran.psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1CK2hZ-000FrO-6s; Tue, 19 Oct 2004 15:43:33 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16757.39060.602700.402490@ran.psg.com>
Date: Tue, 19 Oct 2004 15:43:32 -0700
To: Dan Nelson <dnelson@allantgroup.com>
References: <16757.28156.361400.647815@ran.psg.com>
	<20041019212148.GB93330@xor.obsecurity.org>
	<16757.35688.795976.719745@ran.psg.com>
	<20041019215625.GE83510@dan.emsphone.com>
cc: FreeBSD Current <freebsd-current@freebsd.org>
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: multi-user startup failure Pre-seeding PRNG:
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2004 22:43:34 -0000

> Does it really lock up, or does sysctl just not return?  Can you
> hit ^C?

it really locks up solid.  while i can hit ^C, it has no effect:-).

> Does ^T print anything?

nope

> Can you break into the debugger via Ctrl-Alt-ESC?

nope

> After you comment them out, does "sysctl -a" lock the system if
> you run it after the system boots up?

while in single-user, sysctl -a prints up to
  kern.diska: ad0
and then locks.  no response to ^C <ctl><alt><esc>, ^T ...

in multi-user, sysctl -a locks up after printing
"net.inet.tcp.isn_reseed_interval: 0"

> Something to try might be to change the script to run "truss
> sysctl -a"

easier to just run it manually, yes?  and the result is at
<http://rip.psg.com/~randy/041019.sysctl-lockup/>

run twice, it does not stop at the same place.

a possible hint: when shutting down this host, it hangs at
Stopping ACPI.  this is also a revert.

randy