[Bug nptl/30058] New: error: xpthread_check_return.c:32: pthread_create: Resource temporarily unavailable

[Bug nptl/30058] New: error: xpthread_check_return.c:32: pthread_create: Resource temporarily unavailable

[danglin at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=30058

            Bug ID: 30058
           Summary: error: xpthread_check_return.c:32: pthread_create:
                    Resource temporarily unavailable
           Product: glibc
           Version: 2.38
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: danglin at gcc dot gnu.org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
              Host: hppa*-*-linux*
            Target: hppa*-*-linux*
             Build: hppa*-*-linux*

dave@mx3210:~/gnu/glibc/objdir$ make test t=nptl/tst-pthread-timedlock-lockloop
make -r PARALLELMFLAGS="" -C ../glibc objdir=`pwd` test
make[1]: Entering directory '/home/dave/gnu/glibc/glibc'
make subdir=nptl -C nptl/ ..=../
/home/dave/gnu/glibc/objdir/nptl/tst-pthread-timedlock-lockloop.out
make[2]: Entering directory '/home/dave/gnu/glibc/glibc/nptl'
env GCONV_PATH=/home/dave/gnu/glibc/objdir/iconvdata
LOCPATH=/home/dave/gnu/glibc/objdir/localedata LC_ALL=C  
/home/dave/gnu/glibc/objdir/elf/ld.so.1 --library-path
/home/dave/gnu/glibc/objdir:/home/dave/gnu/glibc/objdir/math:/home/dave/gnu/glibc/objdir/elf:/home/dave/gnu/glibc/objdir/dlfcn:/home/dave/gnu/glibc/objdir/nss:/home/dave/gnu/glibc/objdir/nis:/home/dave/gnu/glibc/objdir/rt:/home/dave/gnu/glibc/objdir/resolv:/home/dave/gnu/glibc/objdir/mathvec:/home/dave/gnu/glibc/objdir/support:/home/dave/gnu/glibc/objdir/crypt:/home/dave/gnu/glibc/objdir/nptl
/home/dave/gnu/glibc/objdir/nptl/tst-pthread-timedlock-lockloop  >
/home/dave/gnu/glibc/objdir/nptl/tst-pthread-timedlock-lockloop.out; \
../scripts/evaluate-test.sh nptl/tst-pthread-timedlock-lockloop $? false false
> /home/dave/gnu/glibc/objdir/nptl/tst-pthread-timedlock-lockloop.test-result
make[2]: Leaving directory '/home/dave/gnu/glibc/glibc/nptl'
FAIL: nptl/tst-pthread-timedlock-lockloop
original exit status 1
error: xpthread_check_return.c:32: pthread_create: Resource temporarily
unavailable
error: 1 test failures
make[1]: Leaving directory '/home/dave/gnu/glibc/glibc'

The error seems timing dependent and occurs on one machine but not another.

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

[Bug nptl/30058] error: xpthread_check_return.c:32: pthread_create: Resource temporarily unavailable

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30058

Florian Weimer <fweimer at redhat dot com> changed:

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

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
This could be a result of these set of kernel bugs:

Task exit is signaled before task resource deallocation, leading to bogus
EAGAIN errors
<https://bugzilla.kernel.org/show_bug.cgi?id=154011>

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

[Bug nptl/30058] error: xpthread_check_return.c:32: pthread_create: Resource temporarily unavailable

[dave.anglin at bell dot net]

https://sourceware.org/bugzilla/show_bug.cgi?id=30058

--- Comment #2 from dave.anglin at bell dot net ---
I believe this test started to fail some time between May 24, 2022 and November
5 2022.

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

[Bug nptl/30058] error: xpthread_check_return.c:32: pthread_create: Resource temporarily unavailable

[dave.anglin at bell dot net]

https://sourceware.org/bugzilla/show_bug.cgi?id=30058

--- Comment #3 from dave.anglin at bell dot net ---
On 2023-01-30 9:42 a.m., John David Anglin wrote:
> I believe this test started to fail some time between May 24, 2022 and November 5 2022.
>
No.  It's a futex issue.

[pid 30913] futex(0x18430, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 2,
{t
v_sec=1675127290, tv_nsec=128582675}, FUTEX_BITSET_MATCH_ANY <unfinished ...>
[pid 30912] <... clock_gettime64 resumed>{tv_sec=1675127290,
tv_nsec=137582773})
  = 0
[pid 30911] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30910] <... clock_gettime64 resumed>{tv_sec=1675127290,
tv_nsec=137582773}) = 0
[pid 30903] mmap2(NULL, 83890176, PROT_NONE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0 <unfinished ...>
[pid 30921] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30920] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30919] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30918] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30917] <... clock_gettime64 resumed>{tv_sec=1675127290,
tv_nsec=137582773}) = 0
[pid 30916] clock_gettime64(CLOCK_REALTIME,  <unfinished ...>
[pid 30915] <... futex resumed>)        = 0
[pid 30914] <... clock_gettime64 resumed>{tv_sec=1675127290,
tv_nsec=137582773}) = 0
[pid 30913] <... futex resumed>)        = -1 EAGAIN (Resource temporarily
unavailable)

Dave

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