[Bug nptl/24924] New: nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] New: nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

            Bug ID: 24924
           Summary: nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64
           Product: glibc
           Version: 2.29
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: [hidden email]
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
            Target: aarch64-*-*

nptl/tst-rwlock9 and nptl/tst-rwlock18 never finish, with an infinite stream of
"reader thread %d tries again".

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
I don't think we have seen that in our testing.  Would you please share more
details about the environment (kernel and silicon)?  Thanks.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #2 from Andreas Schwab <[hidden email]> ---
It's using the standard Factory kernel, which is 5.2.8 right now.  The hardware
is probably a Cavium ThunderX1.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #3 from Andreas Schwab <[hidden email]> ---
It looks like the tests only fail when run on a ThunderX1.  Other build
workers, even those with a ThunderX2, do not cause them to fail.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

Andreas Schwab <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.29                        |2.30

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

Andreas Schwab <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|aarch64-*-*                 |
               Host|                            |aarch64-*-*

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #4 from Andreas Schwab <[hidden email]> ---
That appears to be a regression introduced between 2019-07-07 and 2019-07-14.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #5 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
The test was recently changed to cover pthread_rwlock_clock*. Is this what is
failing? Which kind of failure

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #6 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Adhemerval Zanella from comment #5)
> The test was recently changed to cover pthread_rwlock_clock*. Is this what
> is failing? Which kind of failure

I hit send prior to finishing the last sentence.  Which return value
pthread_rwlock_* shows in the loop?

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #7 from Andreas Schwab <[hidden email]> ---
It's ETIMEDOUT of course, otherwise the loop would stop.  It's the
CLOCK_REALTIME test that fails.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #8 from Andreas Schwab <[hidden email]> ---
And the CLOCK_MONOTONIC test fails in the same way.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/24924] nptl/tst-rwlock9 and nptl/tst-rwlock18 fail on aarch64

cvs-commit at gcc dot gnu.org
In reply to this post by cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=24924

--- Comment #9 from Andreas Schwab <[hidden email]> ---
When I comment out the "reader thread tries again" messages (and skip the
timedlock test), all I see is this:

writer thread 0 tries again
writer thread 1 tries again
writer thread 0 succeeded
writer thread 2 tries again
writer thread 3 tries again
writer thread 4 tries again
writer thread 5 tries again
writer thread 6 tries again
writer thread 7 tries again
writer thread 8 tries again
writer thread 9 tries again
writer thread 10 tries again
writer thread 11 tries again
writer thread 12 tries again
writer thread 13 tries again
writer thread 14 tries again
writer thread 0 released
writer thread 0 tries again
writer thread 2 tries again
writer thread 3 tries again
writer thread 4 tries again
writer thread 5 tries again
writer thread 6 tries again
writer thread 7 tries again
writer thread 8 tries again
writer thread 9 tries again
writer thread 10 tries again
writer thread 11 tries again
writer thread 12 tries again
writer thread 13 tries again
writer thread 14 tries again

--
You are receiving this mail because:
You are on the CC list for the bug.