From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 10 20:40:20 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D26016A4CF; Wed, 10 Nov 2004 20:40:20 +0000 (GMT) Received: from idiom.novusordo.net (novusordo.net [216.194.67.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFDE643D1F; Wed, 10 Nov 2004 20:40:19 +0000 (GMT) (envelope-from cdjones@novusordo.net) Received: from [127.0.0.1] (localhost.novusordo.net [127.0.0.1]) by idiom.novusordo.net (Postfix) with ESMTP id CB6C454D1; Wed, 10 Nov 2004 13:40:17 -0700 (MST) Message-ID: <41927CB1.2060106@novusordo.net> Date: Wed, 10 Nov 2004 13:40:17 -0700 From: Chris Jones User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <200411100810.iAA8AUoR023993@freefall.freebsd.org> <20041110191311.GP56766@hub.freebsd.org> In-Reply-To: <20041110191311.GP56766@hub.freebsd.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/73757: vinum fails to load from rc.conf and kernel panics; works fine if started after boot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2004 20:40:20 -0000 Kris Kennaway wrote: > On Wed, Nov 10, 2004 at 08:10:30AM +0000, Chris Jones wrote: > > >> Hi, Ruslan --- I tried adding 'vinum_load="YES"' into my >> /boot/loader.conf, as errata.html suggests, but this didn't help with >> getting vinum to load properly; I still got trap 12 on booting. >> Unfortunately, I don't have the exact addresses for the {instruction, >> stack, frame} pointers from that attempt handy at the moment, but I'll >> send them your way as soon as possible. > > > I see from your original message that you compiled your own kernel, > suggesting you upgraded from source from a previous installation. > Make sure your vinum.ko is up-to-date; you'll often get this kind of > failure if you try and load an old module with a new kernel. From a fresh 5.3R install using the mini-install CD, I got the source using the RELENG_5_3 tag out of CVS, copied the GENERIC kernel configuration to one named ISIS, and then did a buildkernel KERNCONF=ISIS followed by an installkernel. Unless there are changes between the 5.3R install and the RELENG_5_3 tag, this shouldn't be an issue....