From owner-freebsd-alpha Mon Jul 5 21:11: 0 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D755B1533C for ; Mon, 5 Jul 1999 21:10:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA11167; Mon, 5 Jul 1999 21:10:56 -0700 Date: Mon, 5 Jul 1999 21:10:52 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Steve Price Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: panic in recent kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 5 Jul 1999, Steve Price wrote: > On Mon, 5 Jul 1999, Matthew Jacob wrote: > > # > # Brain idiocy on my part. I couldn't figure out why this kept panic'ing for > # ccdconfig when I hadn't config'd ccd in. It turns out there *are* .ko > # modules in /modules- they're way out of date because the interfaces > # changed. > # > # phk rev'd the kernel version, but that didn't stop the modules from > # loading. Somebody file the appropriate bugs. > > Sorry for being clueless here... What you are saying is that if > I install new modules the new kernel will work? I'd be happy to That I don't know. Remove the modules first. See if things work. If they do, then install new modules. If things work and the modules load then the problem here is that the module loading isn't cognizant of an incompatible interface change. It's my understanding that if you bump a kernel revision (__FreeBSD_Version), kernel modules and other things that depend upon kernel APIs and data structures need to be recompiled. The module loading code should not have us spend a day to find out that this is what happened. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message