From owner-freebsd-current@FreeBSD.ORG Tue Sep 11 09:24:26 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C07816A417; Tue, 11 Sep 2007 09:24:26 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id A9DC813C47E; Tue, 11 Sep 2007 09:24:25 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.12] (helo=mx2.freenet.de) by mout0.freenet.de with esmtpa (Exim 4.68-dev) (envelope-from ) id 1IV1ym-0004s3-N4; Tue, 11 Sep 2007 11:24:20 +0200 Received: from x0221.x.pppool.de ([89.59.2.33]:55955 helo=peedub.jennejohn.org) by mx2.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.68-dev #12) id 1IV1ym-0006LE-Gg; Tue, 11 Sep 2007 11:24:20 +0200 Date: Tue, 11 Sep 2007 11:24:19 +0200 From: Gary Jennejohn To: "Hidetoshi Shimokawa" Message-ID: <20070911112419.68e8ec0d@peedub.jennejohn.org> In-Reply-To: <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> References: <3979a4b0707291120v4927a20cm357b845f6d1f3567@mail.gmail.com> <46BE1D6C.6040903@cran.org.uk> <626eb4530708221937h31c8f37fu9527e941ed4000b6@mail.gmail.com> Organization: DENX Softwre Engineering GmbH X-Mailer: Claws Mail 3.0.0 (GTK+ 2.10.13; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: console hangs after setting hostname X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2007 09:24:26 -0000 On Thu, 23 Aug 2007 11:37:20 +0900 "Hidetoshi Shimokawa" wrote: > It looks that the low level console is not locked though the high level console > is locked by Giant. > > Could you try the attached patch? > This patch solves the problem and should definitely be committed bfore 7.0. -- Gary Jennejohn