From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 10 20:44:32 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1429916A4CF; Wed, 10 Nov 2004 20:44:32 +0000 (GMT) Date: Wed, 10 Nov 2004 20:44:32 +0000 From: Kris Kennaway To: Chris Jones Message-ID: <20041110204432.GS56766@hub.freebsd.org> References: <200411100810.iAA8AUoR023993@freefall.freebsd.org> <20041110191311.GP56766@hub.freebsd.org> <41927CB1.2060106@novusordo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41927CB1.2060106@novusordo.net> User-Agent: Mutt/1.4.1i cc: Kris Kennaway 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:44:32 -0000 On Wed, Nov 10, 2004 at 01:40:17PM -0700, Chris Jones wrote: > 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.... I think there have been some changes, so just to be sure you should proceed as above. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe