public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romain.geissler at amadeus dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26823] New: FAIL: elf/tst-cpu-features-cpuinfo with recent trunk: HAS_CPU_FEATURE (ERMS)
Date: Fri, 30 Oct 2020 21:29:31 +0000 [thread overview]
Message-ID: <bug-26823-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26823
Bug ID: 26823
Summary: FAIL: elf/tst-cpu-features-cpuinfo with recent trunk:
HAS_CPU_FEATURE (ERMS)
Product: glibc
Version: 2.33
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: romain.geissler at amadeus dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Hi,
I get failures with elf x86 test tst-cpu-features-cpuinfo. My configuration is
the following:
- glibc sources are from commit 21181d1c7b181c4bb71e587c7944e100d923b393
- I use an x86_64 machine
- I build and run tests for glibc in a --privileged docker container (not sure
this has any influence).
- My kernel is from RHEL 7: Linux 9f1b028ef771 3.10.0-1127.13.1.el7.x86_64 #1
SMP Fri Jun 12 14:34:17 EDT 2020 x86_64 GNU/Linux
- This machine is a VM.
The failure I get is this one:
Checking HAS_CPU_FEATURE (ERMS):
HAS_CPU_FEATURE (ERMS): 1
cpuinfo (erms): 0
*** failure ***
I am pasting /proc/cpuinfo for the first processor:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 63
model name : Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz
stepping : 0
microcode : 0x2000065
cpu MHz : 2400.000
cache size : 28160 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm
constant_tsc arch_perfmon nopl xt
opology tsc_reliable nonstop_tsc eagerfpu pni pclmulqdq ssse3 fma cx16 pcid
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand
hypervisor lahf_lm abm inv
pcid_single ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2 smep bmi2
invpcid xsaveopt arat md_clear spec_ctrl intel_stibp flush_l1d
arch_capabilities
bogomips : 4800.00
clflush size : 64
cache_alignment : 64
address sizes : 42 bits physical, 48 bits virtual
power management:
Is this something expected ?
Cheers,
Romain
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-10-30 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 21:29 romain.geissler at amadeus dot com [this message]
2020-10-30 21:31 ` [Bug build/26823] " romain.geissler at amadeus dot com
2020-12-05 14:12 ` romain.geissler at amadeus dot com
2021-02-03 6:09 ` romain.geissler at amadeus 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-26823-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: link
Be 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).