From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 14 01:38: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 AC1191065673 for ; Thu, 14 Jul 2011 01:38:28 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 683138FC18 for ; Thu, 14 Jul 2011 01:38:28 +0000 (UTC) Received: by vxg33 with SMTP id 33so6378602vxg.13 for ; Wed, 13 Jul 2011 18:38:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zjj1UmtgVUpNnrZiI0SDqUl4bihKg7SfYlHxzfo0WQw=; b=dSqKgXymIFQOrivLTDS3HUi+5yMJnEHCuh9T5hoVyXqmpvzeno21kg77Ye9PreJ1qa CwT9emQQ45qMrAYxgBIt7ZYDzWDesw1He2KRYtqIsuQFssja7XaAogAAHP+3xaqhiI2O rRmnQPD5QQ1hM47ATT026PpGXsQJAmk83Qmu4= MIME-Version: 1.0 Received: by 10.220.117.74 with SMTP id p10mr488361vcq.141.1310607507322; Wed, 13 Jul 2011 18:38:27 -0700 (PDT) Received: by 10.220.72.75 with HTTP; Wed, 13 Jul 2011 18:38:27 -0700 (PDT) In-Reply-To: <4E1E42FC.3080407@gamozo.org> References: <4E1CC63D.6040606@gamozo.org> <201107130749.35335.jhb@freebsd.org> <4E1D9FA3.30403@gamozo.org> <4E1DC0B2.5070909@FreeBSD.org> <4E1E42FC.3080407@gamozo.org> Date: Wed, 13 Jul 2011 18:38:27 -0700 Message-ID: From: Garrett Cooper To: Brandon Falk Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org 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: Thu, 14 Jul 2011 01:38:28 -0000 On Wed, Jul 13, 2011 at 6:14 PM, Brandon Falk wrote: > On 7/13/2011 10:58 AM, John Baldwin wrote: >> >> On 7/13/11 9:37 AM, Brandon Falk wrote: >>> >>> On 7/13/2011 6:49 AM, John Baldwin wrote: >>>> >>>> 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.). >>>> >>> >>> Since it's on a native box, I have no good way of copying the text, so >>> perhaps later I'll copy it by hand. /boot/loader launches just fine, and >>> it's outputting messages just fine, until it just halts. It does not hit >>> sysinstall. This box also does not have net as LAN is shot on the >>> motherboard (hence getting the new motherboard). >> >> What is the last message it outputs before it hangs? >> > > Hello, > > Sorry, I've been busy with work and I can't be bothered with rebooting my > machine right now. But, it seems I have duplicated a very similar issue > under a VM. Under the 9.0-CURRENT-201105-amd64-bootonly.iso iso it 'locks' > up during boot with yet again no error message or crash. This only seems to > happen when 8 cores are allocated to the VM, everything is just fine and > dandy with 4, 2, or 1 core(s). (Note, on my native box I was using the > 8.2-RELEASE amd64 bootonly iso). > > On the VM the last messages I get are: > > SMB: AP CPU #x Launched! > > x being a number inclusive and between 1-7, in a random order (obviously the > cpus start at 'random' times). > > I cannot duplicate this error on a successfully installed > FreeBSD-8.2-RELEASE-amd64 using the same hardware settings. > > Hmm, I just thought perhaps it is a CD issue... I tried > FreeBSD-8.2-RELEASE-amd64-bootonly on 8, 4, 2, and 1 cores, and it seems to > work just fine... argh. Ok -- this sounds familiar. I saw something like that with the May FreeBSD CURRENT USB snapshot on an r710, but things worked after I properly configured the LSI RAID volume on the machine. Thanks, -Garrett