Date: Mon, 5 Jul 1999 21:10:52 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Steve Price <sprice@hiwaay.net> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: panic in recent kernel Message-ID: <Pine.BSF.4.05.9907052108560.10459-100000@semuta.feral.com> In-Reply-To: <Pine.OSF.4.10.9907052115330.19262-100000@fly.HiWAAY.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9907052108560.10459-100000>