From owner-freebsd-current@FreeBSD.ORG Wed Jul 1 14:41:23 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 96C39106567C for ; Wed, 1 Jul 2009 14:41:23 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4B8EB8FC26 for ; Wed, 1 Jul 2009 14:41:23 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from PegaPegII (hydra.fletchermoorland.co.uk [78.33.209.59]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n61EfLb2012535; Wed, 1 Jul 2009 14:41:21 GMT (envelope-from ken@mthelicon.com) Message-ID: From: "Pegasus Mc Cleaft" To: "Kamigishi Rei" References: <895D2AA2E9964CEE970A64C74D2FF622@PegaPegII> <4A4B724D.10506@haruhiism.net> In-Reply-To: <4A4B724D.10506@haruhiism.net> Date: Wed, 1 Jul 2009 15:41:19 +0100 Organization: Feathers MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18005 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005 X-Antivirus: avast! (VPS 090630-0, 30/06/2009), Outbound message X-Antivirus-Status: Clean 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 Reply-To: Pegasus Mc Cleaft 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:41:23 -0000 > Pegasus Mc Cleaft wrote: >> I was wondering.. Has anyone actually been able to boot a kernel >> after r194958? On 2 different machine (simmilar archecture) the system >> will kernel-trap right after attemping to mount the ZFS filesystems. I >> dont know if it is ZFS related or not as I am not able to get a core. It >> complains that no dump device has been defined and then locks up... >> If there is a way that I can provide more information, please let me >> know how and I will post it. > > If your swap space is in zpool, you won't be able to dump. > Does the system boot in single user mode? Without starting /etc/rc.d/zfs I > mean. 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). I'll try in a few hours to see if it will allow me to go into single user and report back to everyone. I'm not infront of the console at the moment (I need to get a IP-KVM) :> Peg