From owner-freebsd-current@FreeBSD.ORG Mon Oct 15 05:24:24 2007 Return-Path: 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 B420416A41B for ; Mon, 15 Oct 2007 05:24:24 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 7501713C461 for ; Mon, 15 Oct 2007 05:24:24 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:62731 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IhIRC-000K6x-P6 for freebsd-current@freebsd.org; Mon, 15 Oct 2007 05:24:22 +0000 Message-ID: <4712F986.3070202@conducive.net> Date: Mon, 15 Oct 2007 01:24:22 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071015.034121.120532311.hrs@allbsd.org> <471291CA.3020404@conducive.net> <47129BEA.5010308@FreeBSD.org> In-Reply-To: <47129BEA.5010308@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 05:24:24 -0000 Kris Kennaway wrote: > 韓家標 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 > > No, but one of them can 'blind' your serial terminal to what is... ;-) Bill