When launched, the rtc module (rtc-2004.02.24.1_5) panic the FreeBSD kernel. Unfortunately, I cant give you the panic message, it is not logged. How-To-Repeat: start rtc module. I need it for VMware (and so Linux compatibility). On 4.11, it was working fine. I moved to 5.3 than 6.0 in a single day, recompiled many things as VMware, Linux compat & rtc. MY only problem is now this rtc module panicing the kernel.
Responsible Changed From-To: freebsd-ports-bugs->freebsd-emulation Over to maintainer(s).
Sounds like an old version of rtc is installed. Since this is a kernel module, you cannot leave an old one sitting around. Boot into single user mode, mount all the filesystems, delete the rtc port, then rebuild it from source.
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.
State Changed From-To: open->closed Apparently this was a problem of trying to use an older binary with a current kernel. That won't work.