On Tue, Jan 21, 2020 at 12:33 AM Frantisek Rysanek <Frantisek.Rysanek@xxxxxxx> wrote: > Initially I was wondering if the format of the keytable file was > correct for your version of ir-keytable (because I believe I've seen > two different formats in the recent past) but looking at that stack > trace, currently I'm wondering about two possible theories: > > a) either ir-keytable is using strlen (by calling strdup(), actually) > in an unsafe way, trying to find a null character in a buffer that is > not null-terminated for some reason > > b) or, avx2 sounds like something rather hot off the press. Sounds > like the libc contains several versions of the strlen function and > patches the fastest flavour in at runtime, depending on the hardware > it finds itself running on. But... is this avx2-based strlen() > variant the culprit here? Who knows... I am assuming that your CPU is > capable of avx2 = that the CPU feature detection in libc works > fine... And I'm assuming that strlen() is so ubiquitous throughout > the user space, that it's hardly the culprit here. Your distro > probably wouldn't be able to boot if this was the problem. > > Unfortunately I have no hard data :-) just guesses. > > Also, at a more superficial level, what distro is this? Arch? I don't > know Arch, I'm conservative, most of my machines run Debian oldstable > :-) You seem to be using a pretty new kernel, that's why I'm asking. > Not that the kernel would seem to be implicated in this misbehavior. > But if you're using some bleeding-edge "rolling release", that might > be a part of the explanation (= perhaps not as thoroughly tested as > my favourite late-adopter relics). > > Frank > Hello, Frank- CPU is [kodiuser@kodiarch ~]$ grep "model name" /proc/cpuinfo | head -1 model name : Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz [kodiuser@kodiarch ~]$ /proc/cpuinfo shows cpu is capable of it, i believe [kodiuser@kodiarch ~]$ grep flags /proc/cpuinfo | head -1 | grep avx2 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 est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp [kodiuser@kodiarch ~]$ Any pointers on how to check to see if the feature detection for that is working correctly in libc? Yes, this is Arch. Problem was first noticed while running a slightly older kernel, but don't know if that is the initial cause. Did a full upgrade before posting this bug (where it picked up the current kernel). Thank you for the input :) c
