From owner-freebsd-current@FreeBSD.ORG Wed Jul 1 14:46:03 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEA24106566C for ; Wed, 1 Jul 2009 14:46:03 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from fujibayashi.jp (karas.fujibayashi.jp [77.221.159.4]) by mx1.freebsd.org (Postfix) with ESMTP id 96D5F8FC12 for ; Wed, 1 Jul 2009 14:46:03 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from [192.168.0.10] (datacenter.telecombusinessconsulting.net [77.221.137.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fujibayashi.jp (Postfix) with ESMTPSA id 2565078FA9; Wed, 1 Jul 2009 18:46:02 +0400 (MSD) Message-ID: <4A4B76C2.90406@haruhiism.net> Date: Wed, 01 Jul 2009 18:46:26 +0400 From: Kamigishi Rei User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Pegasus Mc Cleaft References: <895D2AA2E9964CEE970A64C74D2FF622@PegaPegII> <4A4B724D.10506@haruhiism.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Has anyone been able to actually boot the AMD64 kernel after r194958? 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: Wed, 01 Jul 2009 14:46:04 -0000 Pegasus Mc Cleaft wrote: > I use ZFS Boot with a three-way mirror (A seperate GPT slice on > each of the drives) and the swap-space is spanned across 3 other > slices (one on each of the boot drives). I think its giving me that > error because it never gets far enough in the boot to swapon those > slices before it panics. Another symptom of this is that it dosent get > far enough to clear the nextboot flag, so when it does go boom, I have > to manually tell it to boot from the working kernel (r194958). Well, then you won't be able to get a core, because by the time doadump starts the filesystem layer is already dead. The kernel just won't be able to save the dump to something as complicated as a 3-disk-span swap space - it can't even dump to a gmirror-based swapspace properly, you know ;) And if you're using ZFS boot, you probably have ZFS built into kernel so I'm not sure if booting without loading zfs.ko is possible as it's already inside... -- Kamigishi Rei KREI-RIPE