Re: CURRENT kernel crashes on boot with BTX error

On Thu, 23.10.2008 at 14:16:44 +0800, David Adam wrote:
> I did try a loader from the CURRENT sources, which produced the same 
> output.
> 
> However, the plot thickens. When I don't specify the kernel name with 
> nextboot(8), but instead interrupt the loader and use 'unload; load 
> /boot/kernel/gd-8; load /boot/kernel/gd-8/geom_mirror.ko' and so on for my 
> other modules, the kernel boots quite happily - both using the 7.0 loader 
> and the new one from the CURRENT sources.
> 
> Are there likely to be big differences in the boot process between using 
> nextboot(8) and the unload/load method? I've used nextboot(8) to 
> successfully load other kernels on this machine before.
> 
> In any case, now that I have a successful workaround I can try the patches 
> I was after in the first place. If there's any more information I can 
> provide, or you'd like access to this system (it has serial console and 
> remote power control), let me know.

Wild guess: I think acpi is no longer built as module on recent -CURRENT
but included in the kernel. Perhaps the unload dance you did above
"fixed" the double loading of the module? Could you check if your
nextboot kernel is containing/missing ACPI directly?

Cheers,
Ulrich Spoerlein

PS: I'm not saying ACPI code is at fault, but rather loader code that
loads the modules
-- 
It is better to remain silent and be thought a fool,
than to speak, and remove all doubt.