From: wanghanlin@corp.netease.com
To: libc-help@sourceware.org, gcc-help@gcc.gnu.org
Subject: __pthread_mutex_lock assertion error with a simple test program
Date: Thu, 20 Feb 2020 04:28:00 -0000 [thread overview]
Message-ID: <72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com> (raw)
Dear All,
Recently on my X86 server one problem hit.
../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
The test program of appendix [1] is very simple.
Strangely, there are hundreds of identical servers, but only two have this problem.
OS is debian 9.9 with kernel 4.9.0-3.
CPU model: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz
libc version: 2.24-11+deb9u4
gcc version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
appendix [1]:
#include <pthread.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#define MAX_THREAD 50
static pthread_mutex_t seq_mutex = PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP;
static void *proc(void *arg)
{
do {
usleep(10);
pthread_mutex_lock(&seq_mutex);
pthread_mutex_unlock(&seq_mutex);
pthread_mutex_lock(&seq_mutex);
pthread_mutex_unlock(&seq_mutex);
} while (1);
return NULL;
}
int main()
{
int err = 0;
pthread_t thread[MAX_THREAD] = {0};
pthread_attr_t attr;
pthread_attr_init(&attr);
for (int i = 0; i < MAX_THREAD; i++) {
err = pthread_create(&thread[i], &attr, proc, NULL);
if (err) {
printf("create thread error");
return 1;
}
}
pthread_join(thread[0], NULL);
return 0;
}
Regards & Thanks,
Hanlin
next reply other threads:[~2020-02-20 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 4:28 wanghanlin [this message]
2020-02-20 5:07 ` Paul Pluzhnikov via libc-help
2020-02-20 9:02 ` Jonathan Wakely
2021-09-27 14:35 libc-help&sourceware org
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=72ad57af.1380.17060da4702.Coremail.wanghanlin@corp.netease.com \
--to=wanghanlin@corp.netease.com \
--cc=gcc-help@gcc.gnu.org \
--cc=libc-help@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).