From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 13 12:06:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15F891065670 for ; Wed, 13 Jul 2011 12:06:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E34508FC1B for ; Wed, 13 Jul 2011 12:06:27 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7EC0846B0A; Wed, 13 Jul 2011 08:06:27 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1C7438A02F; Wed, 13 Jul 2011 08:06:27 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 13 Jul 2011 07:49:35 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E1CC63D.6040606@gamozo.org> In-Reply-To: <4E1CC63D.6040606@gamozo.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107130749.35335.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 13 Jul 2011 08:06:27 -0400 (EDT) Cc: Brandon Falk Subject: Re: System Fails to Boot (Deadlock?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2011 12:06:28 -0000 On Tuesday, July 12, 2011 6:10:05 pm Brandon Falk wrote: > Hello, > > My machine somehow fails to boot into FreeBSD (off the cd, since it > fails to boot, I can't install it in the first place). It goes through > and ends up stopping deadlock style. No printouts of errors (besides a > ppc problem, which is not fatal) and no crash/oops/panic. It just... > stops and locks up. I know my motherboards PCI system has failed, as > well as lan (getting a new one tomorrow), which is probably what is > causing the problem. The thing is that Windows 7 and Linux happen to > boot just fine on my machine, so although my system has a failing > motherboard and may cause errors, I still feel like it shouldn't be > causing this much of an issue on boot. I tried verbose logging and got > no more information anyways. It will be nearly impossible to diagnose > this error so I'm looking for tips on where to look. How far does it get when it locks? Is it able to load /boot/loader off of the CD ok? Is it getting into the kernel far enough to output stuff to the console? Is it getting into sysinstall and hanging at some sysinstall screen? Also, is this host on the network and able to PXE? It's a lot easier to test custom kernels if needed using PXE than CDs (no need to burn a new CD each time, etc.). -- John Baldwin