From owner-freebsd-current@FreeBSD.ORG Thu Oct 23 18:57:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FDF1106566C; Thu, 23 Oct 2008 18:57:11 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 85EE68FC22; Thu, 23 Oct 2008 18:57:10 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (e180179094.adsl.alicedsl.de [85.180.179.94]) by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id m9NIv5wu017195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Oct 2008 20:57:06 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.2/8.14.2) with ESMTP id m9NIticb004278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Oct 2008 20:55:45 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.2/8.14.2/Submit) id m9NItiZA004277; Thu, 23 Oct 2008 20:55:44 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Thu, 23 Oct 2008 20:55:44 +0200 From: Ulrich Spoerlein To: David Adam Message-ID: <20081023185544.GB1595@roadrunner.spoerlein.net> Mail-Followup-To: David Adam , John Baldwin , freebsd-current@freebsd.org References: <200810221113.30424.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: CURRENT kernel crashes on boot with BTX error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2008 18:57:11 -0000 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.