7.1-RC2: link_elf: symbol cp_time undefined

[Jan Henrik Sylvester]

Garrett Cooper wrote:
> On Dec 25, 2008, at 17:36, Jan Henrik Sylvester <me at janh.de> wrote:
> 
>> Garrett Cooper wrote:
>>> On Dec 25, 2008, at 3:44, Jan Henrik Sylvester <me at janh.de> wrote:
>>>> During boot I see: link_elf: symbol cp_time undefined
>>>>
>>>> I have realized it now with RC2, but looking at my logs, I have had 
>>>> that message during boot since upgrading this machine from 
>>>> 7.0-RELEASE to 7.1-RC1 via freebsd-update a at Dec-8. (I did 
>>>> recompile kernel modules from ports: fusefs-kmod and kqemu-kmod.)
>>>>
>>>> What is the easiest way to find out what tried to link to the 
>>>> unknown symbol? The context in which the messages appear is:
>>>>
>>>> savecore: no dumps found
>>>> Initial i386 initialization:.
>>>> Additional ABI support: linux.
>>>> Starting local daemons:kldload: can't load ntfs: File exists
>>>> link_elf: symbol cp_time undefined
>>>> kldload: can't load linprocfs: No such file or directory
>>>> link_elf: symbol cp_time undefined
>>>> mount: linprocfs : Operation not supported by device
>>>> .
>>>> Updating motd.
>>>> Starting fusefs.
>>>> fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
>>>> Mounting late file systems:.
>>>>
>>>> In my rc.local, I have
>>>> kldload ntfs
>>>> kldload linprocfs
>>>> mount -t linprocfs linprocfs /usr/compat/linux/proc
>>>> which used to work (I think). /boot/kernel/linprocfs.ko does exist.
>>>>
>>>> Cheers,
>>>> Jan Henrik
>>> Did you compile your kernel from scratch?
>>> -Garrett
>>
>> No, it came with freebsd-update (every possible freebsd-update since 
>> the install from the 7.0-BETA4 CD). Outside /etc, the IDS function of 
>> freebsd-update only reports a mismatch for /boot/kernel/linker.hints 
>> -- can this be the problem? (I will try to replace it tomorrow.)
>>
>> Cheers,
>> Jan Henrik
> 
> It shouldn't be the hints file. I would think it's a lack of Linux 
> support built into the updated kernel. I've never used freebsd-upgrade 
> though..
> -Garrett

Thanks for your answer. The problem is entirely my fault. From 7.0, I 
still had /boot/ulegeneric in my kern.module_path instead of 
/boot/kernel -- and /boot/ulegeneric is still there containing a 7.0-p6 
kernel with ULE scheduler, of which the modules do not work with the 
7.1-RC2 kernel (booted from /boot/kernel).

Sorry for the fuss.

Cheers,
Jan Henrik