Re: [Xen-users] Xen 4.12.1/4.13.0-rc2 unable to load module coretemp

[Rishi <2rushikeshj@xxxxxxxxx>]

On Sat, Nov 16, 2019 at 4:29 AM Bobbi Sanchez <bobbisanchez@xxxxxx> wrote:
>
> Hi,
>
>
> i am using (Debian10) Kernel 5.3.7-amd64 self compiled with XEN-dom0 Options 
> activated and also Xen from source Version 4.12.1 and 4.13.0-rc2 self 
> compiled, everything seems to work find but i am not able to load the 
> coretemp.ko module, not possible under Xen4.12.1 and 4.13.0-rc2!
>
> If i dont load the xen.gz at boot, so that i only run Kernel 5.3.7 coretemp 
> is no problem to load!
>
>
> Thats the output if i try to load the coretemp module:
>
> sudo modprobe -vvvvv coretemp
> modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom logging 
> function 0x56006c91c150 registered
> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() 
> file=/lib/modules/5.3.7-4-xen0/modules.dep.bin
> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() 
> file=/lib/modules/5.3.7-4-xen0/modules.alias.bin
> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() 
> file=/lib/modules/5.3.7-4-xen0/modules.symbols.bin
> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open() 
> file=/lib/modules/5.3.7-4-xen0/modules.builtin.bin
> modprobe: DEBUG: ../libkmod/libkmod-module.c:556 
> kmod_module_new_from_lookup() input alias=coretemp, normalized=coretemp
> modprobe: DEBUG: ../libkmod/libkmod-module.c:562 
> kmod_module_new_from_lookup() lookup modules.dep coretemp
> modprobe: DEBUG: ../libkmod/libkmod.c:574 kmod_search_moddep() use mmaped 
> index 'modules.dep' modname=coretemp
> modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get module 
> name='coretemp' found=(nil)
> modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add 
> 0x56006d416f20 key='coretemp'
> modprobe: DEBUG: ../libkmod/libkmod-module.c:202 kmod_module_parse_depline() 
> 0 dependencies for coretemp
> modprobe: DEBUG: ../libkmod/libkmod-module.c:583 
> kmod_module_new_from_lookup() lookup coretemp=0, list=0x56006d4166d0
> modprobe: DEBUG: ../libkmod/libkmod.c:501 lookup_builtin_file() use mmaped 
> index 'modules.builtin' modname=coretemp
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1750 kmod_module_get_initstate() 
> could not open '/sys/module/coretemp/initstate': No such file or directory
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1760 kmod_module_get_initstate() 
> could not open '/sys/module/coretemp': No such file or directory
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=snd_pcsp mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=snd_usb_audio mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=cx88_alsa mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=snd_atiixp_modem mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=snd_intel8x0m mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=snd_via82xx_modem mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=loop mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=bonding mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393 kmod_module_get_options() 
> modname=dummy mod->name=coretemp mod->alias=(null)
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1750 kmod_module_get_initstate() 
> could not open '/sys/module/coretemp/initstate': No such file or directory
> modprobe: DEBUG: ../libkmod/libkmod-module.c:1760 kmod_module_get_initstate() 
> could not open '/sys/module/coretemp': No such file or directory
> modprobe: DEBUG: ../libkmod/libkmod-module.c:744 kmod_module_get_path() 
> name='coretemp' 
> path='/lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/coretemp.ko'
> modprobe: DEBUG: ../libkmod/libkmod-module.c:744 kmod_module_get_path() 
> name='coretemp' 
> path='/lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/coretemp.ko'
> insmod /lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/coretemp.ko
> modprobe: DEBUG: ../libkmod/libkmod-module.c:744 kmod_module_get_path() 
> name='coretemp' 
> path='/lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/coretemp.ko'
> modprobe: INFO: ../libkmod/libkmod-module.c:886 kmod_module_insert_module() 
> Failed to insert module 
> '/lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/coretemp.ko': No such device
> modprobe: ERROR: could not insert 'coretemp': No such device
> modprobe: DEBUG: ../libkmod/libkmod-module.c:468 kmod_module_unref() 
> kmod_module 0x56006d416f20 released
> modprobe: DEBUG: ../libkmod/libkmod.c:418 kmod_pool_del_module() del 
> 0x56006d416f20 key='coretemp'
> modprobe: INFO: ../libkmod/libkmod.c:331 kmod_unref() context 0x56006d4164e0 
> released
>
>
> The Module is there:
>
> ls -hal /lib/modules/5.3.7-4-xen0/kernel/drivers/hwmon/ | grep coretemp
> -rw-r--r--  1 root root  21K Nov 15 00:55 coretemp.ko
>
>
> Thats the xl info:
>
> sudo xl info
> host                   : nanadag
> release                : 5.3.7-4-xen0
> version                : #0 SMP PREEMPT Fri Nov 15 00:55:59 CET 2019
> machine                : x86_64
> nr_cpus                : 4
> max_cpu_id             : 3
> nr_nodes               : 1
> cores_per_socket       : 4
> threads_per_core       : 1
> cpu_mhz                : 2397.616
> hw_caps                : 
> bfebfbff:0000e3bd:20100800:00000001:00000000:00000000:00000000:00000000
> virt_caps              : pv hvm shadow
> total_memory           : 7101
> free_memory            : 128
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> outstanding_claims     : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 13
> xen_extra              : .0-rc
> xen_version            : 4.13.0-rc
> xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler          : credit2
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          :
> xen_commandline        : placeholder
> cc_compiler            : gcc (Debian 8.3.0-6) 8.3.0
> cc_compile_by          : benutzer
> cc_compile_domain      : dag
> cc_compile_date        : Fri Nov 15 22:15:27 CET 2019
> build_id               : ded65a38fabc4057e67d85d1bf6bf4165e88b6ca
> xend_config_format     : 4
>
>
> uname -a
> Linux nanadag 5.3.7-4-xen0 #0 SMP PREEMPT Fri Nov 15 00:55:59 CET 2019 x86_64 
> GNU/Linux
>
> and here from cat /proc/cpuinfo
>
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 15
> model name      : Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
> stepping        : 11
> cpu MHz         : 2397.616
> cache size      : 4096 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 4
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 10
> wp              : yes
> flags           : fpu de tsc msr pae mce cx8 apic sep mca cmov pat clflush 
> acpi mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl cpuid pni 
> monitor est ssse3 cx16 hypervisor lahf_lm
> bugs            : null_seg cpu_meltdown spectre_v1 spectre_v2 
> spec_store_bypass l1tf mds swapgs
> bogomips        : 4795.23
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> --- snip ---
>
>
> What can i do to ge the coretemp module loaded ?
>
> Best Regards
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-users

This change of behavior was introduced with
https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=72e038450d3d5de1a39f0cfa2d2b0f9b3d43c6c6
It was intended to hide Thermal info from PV guests but seems it got
hidden from Dom0 as well.

I was having same problem and there are 2 ways through which it could
be solved. Modify Xen to not hide EAX or modify linux Dom0 kernel.
To modify dom0 kernel, you'd have to edit
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/x86/kernel/cpu/common.c?h=v5.3.7#n913
-               c->x86_capability[CPUID_6_EAX] = cpuid_eax(0x00000006);
+               c->x86_capability[CPUID_6_EAX] = native_cpuid_eax(0x00000006);

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users