From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: glibc 2.35 failures in elf/tst-cpu-features-cpuinfo-static.
Date: Fri, 14 Jan 2022 19:13:17 +0100 [thread overview]
Message-ID: <87tue6p4n6.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOocJ+WKTMNZV738Rk5bSk5XgoRY31fCv9DWUte_NnfD2A@mail.gmail.com> (H. J. Lu's message of "Fri, 14 Jan 2022 10:05:22 -0800")
* H. J. Lu:
> On Fri, Jan 14, 2022 at 9:00 AM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> * Carlos O'Donell via Libc-alpha:
>>
>> > Checking HAS_CPU_FEATURE (RTM):
>> > HAS_CPU_FEATURE (RTM): 1
>> > cpuinfo (rtm): 0
>> > *** failure ***
>>
>> Could you pin this test to specific CPUs and see if it behaves
>> differently depending on the CPU?
>>
>
> Hi Carlos,
>
> I believe you ran into:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28033
> https://www.intel.com/content/www/us/en/support/articles/000059422/processors.html
>
> Specifically your CPU is listed as
>
> 06_9EH <=0xC 8th/9th Generation Intel® Core™ Processors and Intel®
> Pentium® Processors based on Coffee Lake microarchitecture
>
> I think we should black list all CPUs on the list.
I think Siddhesh ran into this before, after laptop suspend. It's a
firmware or kernel bug that the CPUID state across cores is inconsistent
after suspend. It's not a glibc issue.
Thanks,
Florian
next prev parent reply other threads:[~2022-01-14 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 16:43 Carlos O'Donell
2022-01-14 17:00 ` Florian Weimer
2022-01-14 18:05 ` H.J. Lu
2022-01-14 18:13 ` Florian Weimer [this message]
2022-01-14 21:09 ` Carlos O'Donell
2022-01-14 21:11 ` Florian Weimer
2022-01-14 22:10 ` Carlos O'Donell
2022-01-14 22:23 ` Florian Weimer
2022-01-14 22:30 ` Carlos O'Donell
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=87tue6p4n6.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).