From owner-freebsd-questions@FreeBSD.ORG Mon Mar 10 06:08:48 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69F551065676 for ; Mon, 10 Mar 2008 06:08:48 +0000 (UTC) (envelope-from pyotr@pisem.net) Received: from mx1.samaradom.ru (june.samaradom.ru [85.113.63.225]) by mx1.freebsd.org (Postfix) with ESMTP id 32D1E8FC1D for ; Mon, 10 Mar 2008 06:08:48 +0000 (UTC) (envelope-from pyotr@pisem.net) Received: from [10.62.201.191] (helo=[127.0.0.1]) by mx1.samaradom.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1JYan0-0001ZV-Ss for freebsd-questions@freebsd.org; Mon, 10 Mar 2008 09:43:10 +0400 Message-ID: <47D4CA5B.7040905@pisem.net> Date: Mon, 10 Mar 2008 09:42:51 +0400 From: "pyotr@pisem.net" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071030 SeaMonkey/1.1.6 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080309-0, 09.03.2008), Outbound message X-Antivirus-Status: Clean Subject: gmirror panic on smp unloaded but not nextboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Mar 2008 06:08:48 -0000 Hello everyone, I tried the 6.3 to 7.0 upgrade with cvsup & Co. i already had the gmirror device functioning properly after first mergemaster -p i did boot the 7.0 with nextboot to try. ok, the second mergemaster passed smooth and i tried to boot with old kernel cause forgot about the nextboot last time. ok, on the console i saw the error about wrong gmirror labels version. So to boot the built 7.0 kernel i used the oot loader commands: === unload ( means to unload ALL kernel AND modules, the 6.3 stuff gets completely unloaded ) load /boot/kernel/kernel.70 boot -s === And... see kernel trap 1 right after ata0 and ata1 detection! Sorry no debug information to attach cause it's remote kvm system... More about the hardware: celeron 1.6 dual / 1G / atapi 2x80. Should i submit a PR?