public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
	Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: glibc 2.35 i686 failures in tst-memset-rtm (bug 28033)
Date: Fri, 14 Jan 2022 17:16:47 -0500	[thread overview]
Message-ID: <ef42d13c-f3fb-179b-6a38-fb366bbae804@redhat.com> (raw)
In-Reply-To: <87ee5aow53.fsf@oldenburg.str.redhat.com>

On 1/14/22 16:16, Florian Weimer wrote:
> * Carlos O'Donell via Libc-alpha:
> 
>> On Fedora 35, at commit eb024343726ee3b2e644b72ae03df9023898cf01, I see
>> the following somewhat random failures:
>>
>> [carlos@fedora ~]$ cat ~/build/glibc-review-i686/string/tst-memset-rtm.out
>> error: ../sysdeps/x86/tst-string-rtm.h:63: TSX abort rate: 100.00% (3000 out of 3000)
>> error: 1 test failures
>> [carlos@fedora ~]$ cat ~/build/glibc-review-i686/string/tst-memset-rtm.test-result 
>> FAIL: string/tst-memset-rtm
>> original exit status 1
>> [carlos@fedora ~]$ 
>>
>> Is this the same root cause as this issue?
>> https://sourceware.org/pipermail/libc-alpha/2022-January/135323.html
> 
> Please see <https://sourceware.org/bugzilla/show_bug.cgi?id=27398#c3>
> and check if you can reproduce this phenomenon.
> 
> This is a kernel/firmware bug.  RTM is not correctly disabled after
> resume.

Confirmed. Pinning to cpu 0 reproduces the problem. CPUs 1-7 are fine.

-- 
Cheers,
Carlos.


      reply	other threads:[~2022-01-14 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 21:09 Carlos O'Donell
2022-01-14 21:16 ` Florian Weimer
2022-01-14 22:16   ` Carlos O'Donell [this message]

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=ef42d13c-f3fb-179b-6a38-fb366bbae804@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.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).