Date: Mon, 15 Oct 2007 00:44:58 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= <askbill@conducive.net> Cc: freebsd-current@freebsd.org Subject: Re: panic in 8-CURRENT Message-ID: <47129BEA.5010308@FreeBSD.org> In-Reply-To: <471291CA.3020404@conducive.net> References: <20071015.034121.120532311.hrs@allbsd.org> <471291CA.3020404@conducive.net>
next in thread | previous in thread | raw e-mail | index | archive | help
韓家標 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47129BEA.5010308>