bug ? glibc with nptl 0.60 hangs
Package: libc6 libc6-dev
Version: 2.3.2.ds1-20
Severity: critical/grave
The bug is technically against glibc I imagine, but after much testing,
it appears as though the version of glibc/nptl itself may be the
culprit, and since there is a newer one out (which other distros are
shipping) I suppose it should be a bug here.
I'm running Debian unstable on the following CPUs: Dual Xeon, Athlon,
P4, Via C3 1Ghz.
I'm running kernel versions 2.6.9, 2.6.10rc3, and 2.4.27.
Running 2.4.27, using linux threads results in thread hangs where the
hung threads peg the CPU.
Running 2.6.9 or 2.6.10rc3 and using NPTL also results in thread hangs.
Those hung threads are idle waiting for a notification that never
comes. There are rapidly triggerable. The latter set of thread hangs
appear to be fixed in glibc 2.3.3 and up (newer nptl anyway.)
Forcing the use of Linux Threads under the 2.6.x kernels appears to
resolve the latter issue, and the former hasn't cropped up yet either,
but may still be there.
NPTL working correctly would be good. I don't know whether this should
be a bug against the Debian glibc package for using a buggy NPTL
Recommendations? Upgrade schedule for libc6 on unstable?
Here are some links to more useful discussions of what may be related
issues...
http://www.blackdown.org/java-linux/java-linux@java.blackdown.org/java-linux-ms
g00089.html
https://bugzilla.redhat.com/bugzilla/long_list.cgi?buglist=108631
http://www.mail-archive.com/debian-glibc@lists.debian.org/msg10837.html
http://lists.debian.org/debian-glibc/2004/11/msg00006.html
http://forum.java.sun.com/thread.jspa?threadID=580350&messageID=2936747
Reply to: