From owner-freebsd-emulation@FreeBSD.ORG Wed Nov 9 19:20:25 2005 Return-Path: X-Original-To: freebsd-emulation@hub.freebsd.org Delivered-To: freebsd-emulation@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13F2B16A41F for ; Wed, 9 Nov 2005 19:20:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2CBC43D58 for ; Wed, 9 Nov 2005 19:20:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jA9JKNxL010300 for ; Wed, 9 Nov 2005 19:20:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jA9JKN2a010299; Wed, 9 Nov 2005 19:20:23 GMT (envelope-from gnats) Date: Wed, 9 Nov 2005 19:20:23 GMT Message-Id: <200511091920.jA9JKN2a010299@freefall.freebsd.org> To: freebsd-emulation@FreeBSD.org From: Stephen Hurd Cc: Subject: Re: ports/88694: emulators/rtc: rtc kld module panic FreeBSD 6.0 kernel X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen Hurd List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 19:20:25 -0000 The following reply was made to PR ports/88694; it has been noted by GNATS. From: Stephen Hurd To: Laurent LEVIER Cc: bug-followup@FreeBSD.org Subject: Re: ports/88694: emulators/rtc: rtc kld module panic FreeBSD 6.0 kernel Date: Wed, 09 Nov 2005 13:14:00 -0600 Laurent LEVIER wrote: >> Boot into single user mode, mount all the filesystems, delete the rtc >> port, then rebuild it from source. > > I did this to save my neck, but I would like to have the rtc port work. > Maybe you should contact the maintener so he updates his apparently > old port? Kernel modules MUST be updated when the kernel is. It's not a port out-of-date thing, it's a module out of sync with kernel thing. You'll see this behavior with any kernel modules from the ports tree (the nvidia drivers are another common one). The rtc kernel module is only good for the kernel that was installed when it was built. I'm using that port also, it's working fine now that I rebuilt it under 6.0. the only thing I could suggest is that UPDATING or possibly the upgrade section of the handbook include a list of ports which will cause problems and should be rebuilt before going multi-user. Once again, the problem is caused by loading a kernel module for 4.x or 5.x into the 6.0 kernel. Rebuilding the module for the 6.0 kernel fixes the problem.