From owner-freebsd-stable@FreeBSD.ORG Mon Apr 5 14:56:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FFB2106564A for ; Mon, 5 Apr 2010 14:56:23 +0000 (UTC) (envelope-from jfb@mr-happy.com) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [IPv6:2001:470:b:28:f::1]) by mx1.freebsd.org (Postfix) with ESMTP id 246EE8FC08 for ; Mon, 5 Apr 2010 14:56:23 +0000 (UTC) Received: from crow.mr-happy.com (crow.mr-happy.com [10.1.0.2]) by vexbert.mr-paradox.net (Postfix) with ESMTP id C64A4845B5 for ; Mon, 5 Apr 2010 10:56:22 -0400 (EDT) Received: by crow.mr-happy.com (Postfix, from userid 16139) id 1C75EBA0D; Mon, 5 Apr 2010 10:56:22 -0400 (EDT) Date: Mon, 5 Apr 2010 10:56:22 -0400 From: Jeff Blank To: freebsd-stable@freebsd.org Message-ID: <20100405145622.GA61334@mr-happy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e X-Virus-Scanned: ClamAV 0.94.2/10701/Mon Apr 5 05:08:57 2010 on vexbert.mr-paradox.net X-Virus-Status: Clean Subject: sysctl(?) problem on boot in 8-STABLE 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: Mon, 05 Apr 2010 14:56:23 -0000 Hi, I upgraded an 8-STABLE box to r206119 and am now unable to boot multi-user. I found that it hangs at line 58/59 of /etc/rc.d/initrandom: ( ps -fauxww; sysctl -a; date; df -ib; dmesg; ps -fauxww ) \ | dd of=/dev/random bs=8k 2>/dev/null when I run each of these commands by hand, I get only as far as 'sysctl -a', which seems to exit normally but leaves my keyboard unresponsive (actually acting like I'm leaning on the key). more digging reveals 'sysctl dev.uart' to be what triggers it. this is the entirety of dev.uart from r204154: dev.uart.0.%desc: 16550 or compatible dev.uart.0.%driver: uart dev.uart.0.%location: handle=\_SB_.PCI0.UAR1 dev.uart.0.%pnpinfo: _HID=PNP0501 _UID=1 dev.uart.0.%parent: acpi0 dev.uart.0.wake: 0 seems about the same from r206119. I've attached boot output from r206119. Any ideas? any other info I need to provide? thanks much, Jeff