Did I understand you correctly that you were seeing the issue before the upgrade as well, but more frequent now?
Yes, we saw it also before during the last 12m using the "previous" version (lxc container image) of our subversion service. But this was to seldom to really care about. Now, with the "current" version -- refreshed this days -- it happens within hours. To build software here, there's also an about one year more current build chain or system libs like the glibc. This could cause a mutex issue to become more problematic because of different timings. We never observe the issue in our test or approval stage, but there's no "real world load" on the subversion service. The container is also executed together with a whole bunch on one of our blade server with 112 cores, but the Subversion container is limited to two cores.
Reading up on it, I see that this is exactly the same failure you got. I'm leaning towards an APR issue (possibly related to the exact kernel/libpthread you are using), I never got around to float it on the APR list since it is still quite a bit of "Subversion code" involved. My next step would be to try to write a minimum reproduction application with a bunch of threads all randomy trying to get and release the same mutex.
If you provide me the source code I'm probably able to compile an run it here, too. Some more information about the Gentoo environment and toolchain: "Current": root@prodsub0 ~ # emerge --info Portage 3.0.65 (python 3.12.6-final-0, default/linux/amd64/23.0/split-usr, gcc-13, glibc-2.39-r6, 6.6.13-gentoo x86_64) ================================================================= System uname: Linux-6.6.13-gentoo-x86_64-Intel-R-_Xeon-R-_Gold_6348_CPU_@_2.60GHz-with-glibc2.39 KiB Mem: 2097152 total, 748420 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Tue, 15 Oct 2024 00:45:00 +0000 Head commit of repository gentoo: 69d7fc43e592f00620f0eaaf16ab70a0b1e1dc76 sh bash 5.2_p37 ld GNU ld (Gentoo 2.42 p6) 2.42.0 app-misc/pax-utils: 1.3.7::gentoo app-shells/bash: 5.2_p37::gentoo dev-build/autoconf: 2.71-r7::dnb dev-build/automake: 1.16.5-r2::dnb dev-build/libtool: 2.4.7-r4::dnb dev-build/make: 4.4.1-r1::gentoo dev-lang/perl: 5.40.0::gentoo dev-lang/python: 3.12.6_p4::gentoo sys-apps/baselayout: 2.15::gentoo sys-apps/openrc: 0.55.1::gentoo sys-apps/sandbox: 2.39::gentoo sys-devel/binutils: 2.42-r2::gentoo sys-devel/binutils-config: 5.5.2::gentoo sys-devel/gcc: 13.3.1_p20240614::gentoo sys-devel/gcc-config: 2.11::gentoo sys-kernel/linux-headers: 6.11::gentoo (virtual/os-headers) sys-libs/glibc: 2.39-r6::Gentoo "Previous": root@prodsub1 ~ # emerge --info Portage 3.0.51 (python 3.11.5-final-0, default/linux/amd64/17.1, gcc-13, glibc-2.38-r10, 6.6.13-gentoo x86_64) ================================================================= System uname: Linux-6.6.13-gentoo-x86_64-Intel-R-_Xeon-R-_Gold_6348_CPU_@_2.60GHz-with-glibc2.38 KiB Mem: 2097152 total, 1635388 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Tue, 17 Oct 2023 00:45:01 +0000 Head commit of repository gentoo: 1c4daa1fb10eb099c36746a2fb19a9e0df304860 sh bash 5.1_p16-r6 ld GNU ld (Gentoo 2.40 p5) 2.40.0 app-misc/pax-utils: 1.3.5::gentoo app-shells/bash: 5.1_p16-r6::gentoo dev-lang/perl: 5.38.0-r1::gentoo dev-lang/python: 3.11.5::gentoo dev-util/cmake: 3.24.3::gentoo sys-apps/baselayout: 2.14::gentoo sys-apps/openrc: 0.51::gentoo sys-apps/sandbox: 2.38::gentoo sys-devel/autoconf: 2.71-r1::gentoo sys-devel/automake: 1.15.1-r2::gentoo, 1.16.5::gentoo sys-devel/binutils: 2.40-r5::gentoo sys-devel/binutils-config: 5.5::gentoo sys-devel/gcc: 13.2.1_p20230826::gentoo sys-devel/gcc-config: 2.11::gentoo sys-devel/libtool: 2.4.7-r1::gentoo sys-devel/make: 4.4.1-r1::gentoo sys-kernel/linux-headers: 6.5-r1::gentoo (virtual/os-headers) sys-libs/glibc: 2.38-r10::dnb
