Date: Thu, 21 Feb 2013 08:48:31 -0800 From: John-Mark Gurney <jmg@funkthat.com> To: Shawn Webb <lattera@gmail.com> Cc: FreeBSD-current <freebsd-current@freebsd.org> Subject: Re: r247095 Boot Failure Message-ID: <20130221164831.GU55866@funkthat.com> In-Reply-To: <CADt0fhyCwon6E%2B0dP47Hz-GxOXPO3ihZH%2BZZNbMwRUf5ppSt5g@mail.gmail.com> References: <CADt0fhyCwon6E%2B0dP47Hz-GxOXPO3ihZH%2BZZNbMwRUf5ppSt5g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Shawn Webb wrote this message on Thu, Feb 21, 2013 at 10:28 -0500: > I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm > running ZFS as root with a mirrored root pool. > > Here's a pic of the box failing: > https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/AAAAAAAAGoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg > > There isn't much useful information in the pic. No crash dump is generated. > Where do I go from here? > > I can boot into kernel.old and that works as a workaround for now. Some how, my changes to gcc in r247012 is causing this, even when using the default of clang as cc... I was able to reproduce a crash myself, and then I just backed my change and the new kernel booted... I'm about to do a binary diff between the broken kernel and the new kernel (since I only installed the kernel, not userland) and figure out which part of the system.. But clearly, we are still using gcc somehow in our kernel builds... If I don't figure out what it is in a few hours, I'll back out the change... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130221164831.GU55866>