From owner-freebsd-stable@FreeBSD.ORG Mon Apr 5 18:18:36 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 5DCE71065672 for ; Mon, 5 Apr 2010 18:18:36 +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 3F8B78FC1D for ; Mon, 5 Apr 2010 18:18:36 +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 A06FF845AE; Mon, 5 Apr 2010 14:18:34 -0400 (EDT) Received: by crow.mr-happy.com (Postfix, from userid 16139) id D0C0CBA34; Mon, 5 Apr 2010 14:18:33 -0400 (EDT) Date: Mon, 5 Apr 2010 14:18:33 -0400 From: Jeff Blank To: Mikolaj Golub Message-ID: <20100405181833.GA62189@mr-happy.com> References: <20100405145622.GA61334@mr-happy.com> <86aathahwk.fsf@kopusha.onet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86aathahwk.fsf@kopusha.onet> 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/10703/Mon Apr 5 13:07:08 2010 on vexbert.mr-paradox.net X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: 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 18:18:36 -0000 On Mon, Apr 05, 2010 at 09:11:39PM +0300, Mikolaj Golub wrote: > On Mon, 5 Apr 2010 10:56:22 -0400 Jeff Blank wrote: > > 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. > kern/143040 looks similar. Ah, you're right, it does. Could someone please take a look at that PR then? Looks like it was submitted in January but hasn't been assigned yet. thanks, Jeff