Re: New builds won't boot (fwd)

On Sun, 7 Jun 2009, Tim Kientzle wrote:
> Chris Hedley wrote:
>> 
>> I was wondering if anybody has any suggestions for me.  Since around 
>> January this year, I've been unable to get new builds to boot on my 
>> system:...
>> 
>> I've just regressed to a version from mid January which boots without any 
>> problems,...
>
> The following information would help a lot:
> * dmesg output from a successful boot.
> * Latest checkout date of a kernel that does boot.
> * Earliest checkout date of a kernel that doesn't boot.
> * If it's not a GENERIC kernel, the kernel
> configuration.  (Diff against GENERIC is enough.)
>
> SVN revisions are even better than dates if
> you have them available.  (Most people
> don't; that's okay.)
>
> With this, someone can look through the
> changes that were made during that period
> and possibly come up with a few likely
> culprits.  Obviously, it's better if you
> can narrow it down to a shorter interval
> (a week is good, a day is better) by
> checking out sources from the half-way
> point and trying that.

Thanks for the reply!  I'm a bit late coming back with the requested 
information, it's taken a while when I've had a day free to test various 
configs (and, I admit, to be able to psych myself up to it--my system is 
not the speediest or most convenient to reboot!)

I've attached the dmesg, its config ("TEAPOT") and loader.conf files; 
apologies in advance for the slightly obtuse configuration layout, one of 
those "it seemed like a good idea at the time" efforts.

As for the versions of the kernel, I've narrowed it down to a half-day 
window, which is hopefully useful: the cvsup-specified dates I have are
2009.02.18.12.00.00 (working) and 2009.02.19.00.00.00 (not working).

If anybody has any ideas what to do next...  I'd /almost/ prefer to hear 
it was a configuration gaffe on my part (and I've already spotted a 
surplus nvram entry while writing this), even if it does mean no small 
amount of embarrassment.

Chris.