{"id":2614,"date":"2019-09-30T16:48:49","date_gmt":"2019-09-30T23:48:49","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=2614"},"modified":"2019-09-30T16:48:49","modified_gmt":"2019-09-30T23:48:49","slug":"kernel-5-4-rc1-released-odd-quirks-with-kernel-symbols","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=2614","title":{"rendered":"Kernel – 5.4-rc1 Released – Odd Quirks with Kernel Symbols"},"content":{"rendered":"

Kernel 5.4-rc1<\/strong> is out – a day later than usual, and brief details are here: http:\/\/lkml.iu.edu\/hypermail\/linux\/kernel\/1909.3\/04895.html<\/a><\/p>\n

My tests with VMware and NVIDIA revealed some odd errors\/warning relating to kernel symbols..<\/p>\n

With the latest NVIDIA (435.21<\/strong>) I got the following:<\/p>\n

# make<\/span><\/strong>
\nmake[1]: Entering directory '\/usr\/src\/linux-5.4-rc1'<\/span><\/strong>
\nThe Module.symvers file is missing, or does not contain any<\/span><\/strong>
\nsymbols exported from the kernel. This could cause the NVIDIA<\/span><\/strong>
\nkernel modules to be built against a configuration that does<\/span><\/strong>
\nnot accurately reflect the actual target kernel.<\/span><\/strong>
\nThe Module.symvers file check can be disabled by setting the<\/span><\/strong>
\nenvironment variable IGNORE_MISSING_MODULE_SYMVERS to 1.<\/span><\/strong>
\nmake[2]: *** [\/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/Kbuild:181: module_symvers_sanity_check] Error 1<\/span><\/strong>
\nmake[1]: *** [Makefile:1670: \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel] Error 2<\/span><\/strong>
\nmake[1]: Leaving directory '\/usr\/src\/linux-5.4-rc1'<\/span><\/strong>
\nmake: *** [Makefile:81: modules] Error 2<\/span><\/strong><\/code>
\n– But… the file does<\/span> exist:
\n# ll \/usr\/src\/linux-5.4-rc1\/Module.symvers<\/span><\/strong>
\n-rw-r--r-- 1 root root 889339 Sep 30 14:47 \/usr\/src\/linux-5.4-rc1\/Module.symvers<\/span><\/strong><\/code><\/p>\n

To get the compile working:
\n# export IGNORE_MISSING_MODULE_SYMVERS=1<\/span><\/strong>
\n# make<\/span><\/strong>
\nmake[1]: Entering directory '\/usr\/src\/linux-5.4-rc1'<\/span><\/strong>
\nCONFTEST: hash__remap_4k_pfn<\/span><\/strong>
\nCONFTEST: set_pages_uc<\/span><\/strong>
\nCONFTEST: list_is_first<\/span><\/strong>
\nCONFTEST: set_memory_uc<\/span><\/strong>
\nCONFTEST: set_memory_array_uc<\/span><\/strong>
\nCONFTEST: acquire_console_sem<\/span><\/strong>
\n..................<\/span><\/strong><\/code>
\nbut then:
\n.............<\/span><\/strong>
\nSYMLINK \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-modeset\/nv-modeset-kernel.o<\/span><\/strong>
\nLD [M] \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-modeset.o<\/span><\/strong>
\nCC [M] \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-drm\/nvidia-drm.o<\/span><\/strong>
\nCC [M] \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-drm\/nvidia-drm-drv.o<\/span><\/strong>
\n\/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-drm\/nvidia-drm-drv.c:662:44: error: \u2018DRIVER_PRIME\u2019 undeclared here (not in a function); did you mean \u2018DRIVER_PCI_DMA\u2019?<\/span><\/strong>
\n662 | .driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER,<\/span><\/strong>
\n| ^~~~~~~~~~~~<\/span><\/strong>
\n| DRIVER_PCI_DMA<\/span><\/strong>
\nmake[2]: *** [scripts\/Makefile.build:266: \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel\/nvidia-drm\/nvidia-drm-drv.o] Error 1<\/span><\/strong>
\nmake[1]: *** [Makefile:1670: \/home\/rgadsdon\/kernel\/NVIDIA-Linux-x86_64-435.21\/kernel] Error 2<\/span><\/strong>
\nmake[1]: Leaving directory '\/usr\/src\/linux-5.4-rc1'<\/span><\/strong>
\nmake: *** [Makefile:81: modules] Error 2<\/span><\/strong><\/code><\/p>\n

So – more investigation is needed here..<\/p>\n

With VMware 15.5.0<\/strong>, there is a 5.4 patched version of vmmon\/vmnet<\/strong> at https:\/\/github.com\/mkubecek\/vmware-host-modules\/tree\/tmp\/workstation-15.5.0-k5.4<\/a>
\nI applied these, and the vmmon\/vmnet compile completed, but with some odd warnings (output truncated):
\n.....................<\/span><\/strong>
\nWARNING: module vmmon uses symbol alloc_pages_current from namespace uptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol kmalloc_caches from namespace nterruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __kmalloc from namespace ock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol up_read from namespace _lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __put_devmap_managed_page from namespace e, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vmalloc from namespace _lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol schedule_hrtimeout from namespace ruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol gdt_page from namespace lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vm_node_stat from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol init_timer_key from namespace nterruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vfree from namespace ex_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __get_user_1 from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol tsc_khz from namespace _lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol cpu_number from namespace ck_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vmemmap_base from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol kthread_create_on_node from namespace ible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol jiffies from namespace _lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol down_read from namespace ock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vm_zone_stat from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol _copy_to_user from namespace interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol misc_register from namespace interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol del_timer_sync from namespace nterruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol memset from namespace x_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __default_kernel_pte_mask from namespace e, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vmalloc_to_pfn from namespace nterruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol current_task from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol printk from namespace x_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol kthread_stop from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol _totalram_pages from namespace terruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol ktime_get_raw_ts64 from namespace ruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vmap from namespace tex_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol _cond_resched from namespace interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __x86_indirect_thunk_rbx from namespace le, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol down from namespace tex_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol mod_timer from namespace ock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol poll_freewait from namespace interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol add_timer from namespace ock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol up_write from namespace lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol down_write from namespace ck_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol fput from namespace tex_lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol poll_initwait from namespace interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol page_offset_base from namespace erruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol kmem_cache_alloc from namespace erruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __free_pages from namespace _interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol smp_call_function from namespace rruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol ioremap_nocache from namespace terruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol cpu_khz from namespace _lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __get_free_pages from namespace erruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __stack_chk_fail from namespace erruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol schedule_timeout from namespace erruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol schedule from namespace lock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol __x86_indirect_thunk_rax from namespace le, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol wake_up_process from namespace terruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol msleep_interruptible from namespace ptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol _raw_spin_lock from namespace nterruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol vsnprintf from namespace ock_interruptible, but does not import it.<\/span><\/strong>
\nWARNING: module vmmon uses symbol free_pages from namespace ck_interruptible, but does not import it.<\/span><\/strong>
\n...etc, etc ..........<\/span><\/strong><\/code>
\n– and with similar warnings for vmnet<\/strong><\/span>..
\nDespite this, the modules install, and #vmare<\/span><\/strong> seems to work OK? (tested with Win7 guest).<\/p>\n

I did think that this might be a kernel config problem at my end, but installed the pre-compiled Fedora (Rawhide) kernel version – 5.4.0-0.rc0.git6.1.fc32.x86_64<\/strong><\/span> – and got similar results.<\/p>\n

So.. more investigation needed!<\/p>\n

Robert Gadsdon. September 30th 2019.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Kernel 5.4-rc1 is out – a day later than usual, and brief details are here: http:\/\/lkml.iu.edu\/hypermail\/linux\/kernel\/1909.3\/04895.html My tests with VMware and NVIDIA revealed some odd errors\/warning relating to kernel symbols.. With the latest NVIDIA (435.21) I got the following: # make make[1]: Entering directory ‘\/usr\/src\/linux-5.4-rc1’ The Module.symvers file is missing, or does not contain any symbols exported …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[6,10,11,14,15,18,19,1533,25],"tags":[2103,2104,2106,2105],"class_list":["post-2614","post","type-post","status-publish","format-standard","hentry","category-crash-and-burn","category-fedora","category-hacks","category-kernel","category-linux-2","category-nvidia","category-opinion","category-patches","category-vmware","tag-kernel-5-4-rc1-out","tag-module-symvers-warnings","tag-nvidia-435-21-fails","tag-patched-vmware-15-5-ok"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2614","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2614"}],"version-history":[{"count":3,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2614\/revisions"}],"predecessor-version":[{"id":2617,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2614\/revisions\/2617"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2614"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2614"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2614"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}