* glibc 2.35 i686 failures in tst-memset-rtm (bug 28033)
@ 2022-01-14 21:09 Carlos O'Donell
2022-01-14 21:16 ` Florian Weimer
0 siblings, 1 reply; 3+ messages in thread
From: Carlos O'Donell @ 2022-01-14 21:09 UTC (permalink / raw)
To: libc-alpha, H.J. Lu, Florian Weimer
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
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: glibc 2.35 i686 failures in tst-memset-rtm (bug 28033)
2022-01-14 21:09 glibc 2.35 i686 failures in tst-memset-rtm (bug 28033) Carlos O'Donell
@ 2022-01-14 21:16 ` Florian Weimer
2022-01-14 22:16 ` Carlos O'Donell
0 siblings, 1 reply; 3+ messages in thread
From: Florian Weimer @ 2022-01-14 21:16 UTC (permalink / raw)
To: Carlos O'Donell via Libc-alpha
* 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.
Thanks,
Florian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: glibc 2.35 i686 failures in tst-memset-rtm (bug 28033)
2022-01-14 21:16 ` Florian Weimer
@ 2022-01-14 22:16 ` Carlos O'Donell
0 siblings, 0 replies; 3+ messages in thread
From: Carlos O'Donell @ 2022-01-14 22:16 UTC (permalink / raw)
To: Florian Weimer, Carlos O'Donell via Libc-alpha
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-14 22:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-14 21:09 glibc 2.35 i686 failures in tst-memset-rtm (bug 28033) Carlos O'Donell
2022-01-14 21:16 ` Florian Weimer
2022-01-14 22:16 ` Carlos O'Donell
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).