Tracker item #2658928, was opened at 2009-03-03 23:24 Message generated for change (Comment added) made by eisiware You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2658928&group_id=204462
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: kernel modules Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sisternicky (eisiware) Assigned to: Nobody/Anonymous (nobody) Summary: vsock module not loadable into the kernel (2.6.28.7) Initial Comment: Hi, on my new kernel, the module vsock will not load. On modprobing, it returns the following error message: root [ ~ ]# modprobe -v vsock insmod /lib/modules/2.6.28.7/kernel/net/vsock/vsock.ko FATAL: Error inserting vsock (/lib/modules/2.6.28.7/kernel/net/vsock/vsock.ko): Unknown symbol in module, or unknown parameter (see dmesg) and here follows the kernel log: Mar 3 23:18:40 landfrauen kernel: [ 1912.571989] vsock: no symbol version for VMCIMemcpyToQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.572151] vsock: Unknown symbol VMCIMemcpyToQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.572285] vsock: no symbol version for VMCIEvent_Unsubscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.572382] vsock: Unknown symbol VMCIEvent_Unsubscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.572514] vsock: no symbol version for VMCIQueuePair_Alloc Mar 3 23:18:40 landfrauen kernel: [ 1912.572595] vsock: Unknown symbol VMCIQueuePair_Alloc Mar 3 23:18:40 landfrauen kernel: [ 1912.572864] vsock: no symbol version for VMCIDatagram_Send Mar 3 23:18:40 landfrauen kernel: [ 1912.572946] vsock: Unknown symbol VMCIDatagram_Send Mar 3 23:18:40 landfrauen kernel: [ 1912.572953] vsock: no symbol version for VMCI_GetContextID Mar 3 23:18:40 landfrauen kernel: [ 1912.572959] vsock: Unknown symbol VMCI_GetContextID Mar 3 23:18:40 landfrauen kernel: [ 1912.573510] vsock: no symbol version for VMCIQueuePair_Detach Mar 3 23:18:40 landfrauen kernel: [ 1912.573594] vsock: Unknown symbol VMCIQueuePair_Detach Mar 3 23:18:40 landfrauen kernel: [ 1912.573977] vsock: no symbol version for VMCIMemcpyFromQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.574062] vsock: Unknown symbol VMCIMemcpyFromQueueV Mar 3 23:18:40 landfrauen kernel: [ 1912.574395] vsock: no symbol version for VMCI_DeviceGet Mar 3 23:18:40 landfrauen kernel: [ 1912.574471] vsock: Unknown symbol VMCI_DeviceGet Mar 3 23:18:40 landfrauen kernel: [ 1912.574636] vsock: no symbol version for VMCIEvent_Subscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.574713] vsock: Unknown symbol VMCIEvent_Subscribe Mar 3 23:18:40 landfrauen kernel: [ 1912.574947] vsock: no symbol version for VMCIDatagram_DestroyHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575027] vsock: Unknown symbol VMCIDatagram_DestroyHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575162] vsock: no symbol version for VMCIDatagram_CreateHnd Mar 3 23:18:40 landfrauen kernel: [ 1912.575240] vsock: Unknown symbol VMCIDatagram_CreateHnd all other modules load fine. Is there any fix known already? ---------------------------------------------------------------------- >Comment By: Sisternicky (eisiware) Date: 2009-03-04 23:32 Message: I'm using open-vm-tools-2009.02.18-148847 I did a toplevel build of the tools, the config.log is attached. File Added: config.log ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 22:48 Message: Also, what version of open-vm-tools are you using? ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 20:06 Message: Ok so we have established that it is a CONFIG_MODVERSIONS problem. Can you provide some more details about what steps you took to build the vsock module. Did you do a top level make in open-vm-tools or something else? I'd still like to get to the bottom of why you ended up with a module that wasn't built against VMCI symbols. ---------------------------------------------------------------------- Comment By: Sisternicky (eisiware) Date: 2009-03-04 17:42 Message: Yes, it does. My modules are modprobed by bootscript (all of the vmware modules), with vsock being last. ---------------------------------------------------------------------- Comment By: Giandomenico De Tullio (kheru) Date: 2009-03-04 15:36 Message: Are VMCI* symbols exported by vmci.ko module ?! If you modprobe vmci.ko BEFORE modprobe-ing vsock returns the same error? dependencies problem ?! ( depmod -a ? ^.- ) ---------------------------------------------------------------------- Comment By: Sisternicky (eisiware) Date: 2009-03-04 08:40 Message: Hi again, thanks for the quick answer. There is an (empty) Module.symvers file in the module build directory modprobe --dump-modversions ./vsock.ko: 0x4f8d5728 struct_module 0x7faa1013 release_sock 0x33c3a362 per_cpu__current_task 0x12da5bb2 __kmalloc 0x5e22aa50 sock_init_data 0xb279da12 pv_lock_ops 0xd42b7232 _write_unlock_bh 0x3f4d635c sock_no_setsockopt 0xc8b57c27 autoremove_wake_function 0xa1801a2e sock_no_getsockopt 0xbe447f76 sock_no_ioctl 0x973873ab _spin_lock 0x8949858b schedule_work 0x5acb8506 sock_queue_rcv_skb 0x6729d3df __get_user_4 0x47a346b3 skb_recv_datagram 0xed06ac02 sock_no_sendpage 0xbd31d52f sock_no_mmap 0x4ba758f9 misc_register 0x7afd8702 sock_no_socketpair 0x2254d547 sk_alloc 0xa2a1e5c9 _write_lock_bh 0xb72397d5 printk 0xc642a151 lock_sock_nested 0x2da418b5 copy_to_user 0xa8eb44f9 sock_no_listen 0xd2123419 sock_no_accept 0x293beace sk_free 0x748caf40 down 0xa368017a init_net 0x7dceceac capable 0x934b1816 proto_register 0xb2fd5ceb __put_user_4 0x85c9c6af __alloc_skb 0x82673561 schedule_delayed_work 0x3c9b4b67 sock_register 0xd62c833f schedule_timeout 0x7f8da821 kfree_skb 0x0fc26794 proto_unregister 0x88dff1b9 skb_copy_datagram_iovec 0x2253d3c5 sk_receive_skb 0x6111e1bc init_timer 0x57a6504e vsnprintf 0x3aa1dbcf _spin_unlock_bh 0x037a0cba kfree 0x0e762d6e request_module 0x33d92f9a prepare_to_wait 0x62737e1d sock_unregister 0x9fb3dd30 memcpy_fromiovec 0x3f1899f1 up 0x9ccb2622 finish_wait 0x08a56041 skb_dequeue 0x701d0ebd snprintf 0x93cbd1ec _spin_lock_bh 0xc5456b60 skb_put 0xf2a644fb copy_from_user 0xc5b0fa1a misc_deregister 0xb052f6a9 skb_free_datagram 0x0da10ec3 security_sock_graft and you are right :) with --force-modversion the module loads find. Hope the info helps. ---------------------------------------------------------------------- Comment By: Aaron Rolett (microchip21) Date: 2009-03-04 01:08 Message: It sounds like you have a newer kernel built with CONFIG_MODVERSIONS and the vsock module doesn't know about the vmci module symbol versions so the kernel is refusing to load it. This should work ... I'm interested to figure out what went wrong. First let me say that you should be able to force the kernel to load the module by using --force-modversion (although then you bypass CONFIG_MODVERSIONS which we would like to avoid). Is there a Module.symvers file in the vsock module build directory? If so, what are the contents? What is the contents of the __versions section of the module? modprobe --dump-modversions ./vsock.ko should give the info. It would also be interesting to see the output of nm ./vmci.ko | grep __crc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2658928&group_id=204462 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
