Warning message in /var/log/messages on CentOS 8.3 with kernel 5.12.4

[jackywu0101]

We noticed some warning messages in /var/log/messages when running pcm-memory.x latest release 202104,

May 19 14:23:31 aep2 kernel: msr: Write to unrecognized MSR 0xc8d by pcm-memory.x (pid: 15168).
May 19 14:23:31 aep2 kernel: msr: See https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about for details.

And here's the configuration of our machine,

[root@aep2 ~]$ cat /etc/centos-release
CentOS Linux release 8.3.2011

[root@aep2 ~]$ uname -a
Linux aep2 5.12.4 #1 SMP Fri May 14 10:51:10 PDT 2021 x86_64 x86_64 x86_64 GNU/Linux

[root@aep2 tmp]# lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              96
On-line CPU(s) list: 0-95
Thread(s) per core:  2
Core(s) per socket:  24
Socket(s):           2
NUMA node(s):        2
Vendor ID:           GenuineIntel
CPU family:          6
Model:               85
Model name:          Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz
Stepping:            6
CPU MHz:             2400.000
CPU max MHz:         3900.0000
CPU min MHz:         1000.0000
BogoMIPS:            4800.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            1024K
L3 cache:            36608K
NUMA node0 CPU(s):   0-23,48-71
NUMA node1 CPU(s):   24-47,72-95
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc 

I did some search on web and found this article, https://www.phoronix.com/scan.php?page=news_item&px=Linux-Filter-Tightening-MSRs, where says,

The new default behavior starting with Linux 5.9 will be to log messages to dmesg whenever a MSR write from user-space happens with a "write to unrecognized MSR" notification.

I'm not sure whether you've already noticed this and have any plan to fix this?

[ogbrugge]

It is already fixed but I am not sure if it is available in a public release yet, My colleague can answer that.

…

On Thu, May 20, 2021 at 4:48 AM Jacky Wu ***@***.***> wrote: We noticed some warning messages in /var/log/messages when running pcm-memory.x latest release 202104, May 19 14:23:31 aep2 kernel: msr: Write to unrecognized MSR 0xc8d by pcm-memory.x (pid: 15168). May 19 14:23:31 aep2 kernel: msr: See https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about for details. And here's the configuration of our machine, ***@***.*** ~]$ cat /etc/centos-release CentOS Linux release 8.3.2011 ***@***.*** ~]$ uname -a Linux aep2 5.12.4 #1 <#1> SMP Fri May 14 10:51:10 PDT 2021 x86_64 x86_64 x86_64 GNU/Linux ***@***.*** tmp]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 96 On-line CPU(s) list: 0-95 Thread(s) per core: 2 Core(s) per socket: 24 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz Stepping: 6 CPU MHz: 2400.000 CPU max MHz: 3900.0000 CPU min MHz: 1000.0000 BogoMIPS: 4800.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 36608K NUMA node0 CPU(s): 0-23,48-71 NUMA node1 CPU(s): 24-47,72-95 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc I did some search on web and found this article, https://www.phoronix.com/scan.php?page=news_item&px=Linux-Filter-Tightening-MSRs, where says, > The new default behavior starting with Linux 5.9 will be to log messages to dmesg whenever a MSR write from user-space happens with a "write to unrecognized MSR" notification. I'm not sure whether you've already noticed this and have any plan to fix this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#297>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFQHV4EQZ54RZNJNZ5XMJVTTOR2APANCNFSM45F46JIA> .

[opcm]

this has been fixed in the master branch already

[opcm]

fixed in the latest release