public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27398] New: Sporadic failures in tst-cpu-features-cpuinfo Date: Fri, 12 Feb 2021 04:44:31 +0000 [thread overview] Message-ID: <bug-27398-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27398 Bug ID: 27398 Summary: Sporadic failures in tst-cpu-features-cpuinfo Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: siddhesh at sourceware dot org CC: drepper.fsp at gmail dot com, hjl.tools at gmail dot com Target Milestone: --- The following tests fail sporadically on my machine: Checking HAS_CPU_FEATURE (HLE): HAS_CPU_FEATURE (HLE): 1 cpuinfo (hle): 0 *** failure *** -- Checking HAS_CPU_FEATURE (RTM): HAS_CPU_FEATURE (RTM): 1 cpuinfo (rtm): 0 *** failure *** Whenever it succeeds, HAS_CPU_FEATURE is 0 in both cases but every once in a while it returns 1. To reproduce: while ./testrun.sh elf/tst-cpu-features-cpuinfo; do /bin/true; done This exits on the first failed run. My /proc/cpuinfo: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz stepping : 12 microcode : 0xde cpu MHz : 877.111 cache size : 8192 KB physical id : 0 siblings : 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes 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 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple shadow_vmcs pml ept_mode_based_exec bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit srbds bogomips : 4199.88 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-02-12 4:44 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-12 4:44 siddhesh at sourceware dot org [this message] 2021-02-12 4:52 ` [Bug libc/27398] " siddhesh at sourceware dot org 2021-02-12 9:46 ` [Bug libc/27398] x86: " fweimer at redhat dot com 2021-02-12 9:59 ` siddhesh at sourceware dot org 2021-02-12 13:45 ` hjl.tools at gmail dot com 2021-02-12 13:51 ` hjl.tools at gmail dot com 2021-02-12 14:00 ` siddhesh at sourceware dot org 2022-01-14 22:20 ` carlos at redhat dot com 2022-01-14 22:21 ` [Bug libc/27398] x86: Improve testing false positive for tst-cpu-features-cpuinfo with bad hardware carlos at redhat dot com 2022-01-14 22:26 ` hjl.tools at gmail dot com 2022-01-14 22:57 ` hjl.tools at gmail dot com 2022-01-14 22:57 ` hjl.tools at gmail dot com 2022-01-17 14:09 ` carlos at redhat dot com 2022-01-17 15:17 ` hjl.tools at gmail dot com 2022-01-17 15:17 ` hjl.tools at gmail dot com 2022-01-18 3:49 ` carlos at redhat dot com 2022-01-18 3:50 ` carlos at redhat dot com 2022-01-18 14:22 ` hjl.tools at gmail dot com 2022-01-18 14:24 ` hjl.tools at gmail dot com 2022-01-18 16:17 ` carlos at redhat dot com 2022-01-18 16:32 ` hjl.tools at gmail dot com 2022-01-18 16:35 ` carlos at redhat dot com 2022-01-18 16:38 ` carlos at redhat dot com 2022-01-18 22:21 ` cvs-commit at gcc dot gnu.org 2022-01-18 22:22 ` hjl.tools at gmail dot com 2022-01-25 18:19 ` carlos at redhat dot com 2022-01-25 18:41 ` hjl.tools at gmail dot com 2022-01-25 18:42 ` hjl.tools at gmail dot com 2022-01-26 19:30 ` carlos at redhat dot com 2022-02-01 13:54 ` cvs-commit at gcc dot gnu.org 2022-02-01 14:08 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:26 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:36 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:59 ` cvs-commit at gcc dot gnu.org 2022-02-01 16:06 ` cvs-commit at gcc dot gnu.org 2022-02-01 17:16 ` cvs-commit at gcc dot gnu.org 2022-05-02 10:42 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27398-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).