From owner-freebsd-current@FreeBSD.ORG  Sun Oct 14 22:45:04 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2CC6416A41A
	for <freebsd-current@freebsd.org>; Sun, 14 Oct 2007 22:45:04 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id 0824413C45D;
	Sun, 14 Oct 2007 22:45:02 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47129BEA.5010308@FreeBSD.org>
Date: Mon, 15 Oct 2007 00:44:58 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= <askbill@conducive.net>
References: <20071015.034121.120532311.hrs@allbsd.org>
	<471291CA.3020404@conducive.net>
In-Reply-To: <471291CA.3020404@conducive.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: freebsd-current@freebsd.org
Subject: Re: panic in 8-CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sun, 14 Oct 2007 22:45:04 -0000

韓家標 Bill Hacker wrote:
> Hiroki Sato wrote:
>> I got the following panic with the Oct 14 8-CURRENT kernel.  A 2-way
>> (Opteron) box running GENERIC FreeBSD/i386 kernel with serial console
>> access, and typing some keys just after "Trying to mount..." line
>> appears seems to prevent this panic.  Without typing any keys the box
>> remain stopped after displaying the line, and then typing a key will
>> cause this panic.  Whether the panic occurs depends on the time
>> between displaying the line and typing a key.
>>
> 
> *snip*
> 
> ..serial console...
> 
> Things to check:
> 
> Are you set to headless all the time? Or does that change during the 
> bootup?
> 
> What of /etc/ttys?
> 
> Thinking that even if you are experienced in adjusting these to work 
> with serial terminal (HP-200-LX here), it is easy to forget to edit the 
> requisites when loading up a brand-new snapshot.

Well, none of those things will cause a deadlock ;)

Kris