I can't build glibc-2.12.90-8 for s390x and s390 because the build logs get filled with repeated "in signal handler/on alternate stack" messages and this continues for hundreds of MB (I got even a 2GB+ log), normal build log is about 400 KB so I cancel the build. Please see the URLs for more details. wrong/canceled build: http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=203936 I was able to do a successful build of 2.12.90-7 a month ago and its results are at http://s390.koji.fedoraproject.org/koji/buildinfo?buildID=34963 If I can trust IRC logs then it was with kernel -44.1.el6 on the builders and cpuplugd disabled. I've tried multiple kernels kernel-2.6.32-44.1.el6.s390x kernel-2.6.32-71.el6.s390x and also tried disabling the cpuplugd daemon (enabled by default) that turns cpus online/offline depending on the load. interesting parts of the logs: glibc-2.12.90-7 =============== + echo ====================TESTING DETAILS================= ++ sed -n 's|^.*\*\*\* \[\([^]]*\.out\)\].*$|\1|p' build-s390x-linuxnptl/check.log =====/builddir/build/BUILD/glibc-2.12-85-g73507d3/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out===== + for i in '`sed -n '\''s|^.*\*\*\* \[\([^]]*\.out\)\].*$|\1|p'\'' build-*-linux*/check.log`' + echo =====/builddir/build/BUILD/glibc-2.12-85-g73507d3/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out===== + cat /builddir/build/BUILD/glibc-2.12-85-g73507d3/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out not on alternate stack in signal handler on alternate stack ============ glibc-2.12.90-8 =============== + cd .. + echo ====================TESTING DETAILS================= ++ sed -n 's|^.*\*\*\* \[\([^]]*\.out\)\].*$|\1|p' build-s390x-linuxnptl/check.log =====/builddir/build/BUILD/glibc-2.12-118-ga7ab6ec/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out===== + for i in '`sed -n '\''s|^.*\*\*\* \[\([^]]*\.out\)\].*$|\1|p'\'' build-*-linux*/check.log`' + echo =====/builddir/build/BUILD/glibc-2.12-118-ga7ab6ec/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out===== + cat /builddir/build/BUILD/glibc-2.12-118-ga7ab6ec/build-s390x-linuxnptl/debug/tst-longjmp_chk2.out not on alternate stack in signal handler on alternate stack in signal handler on alternate stack in signal handler on alternate stack in signal handler on alternate stack ...........
I cannot reproduce that on RHEL5.
This issue first occurred when we switched the builders to RHEL6 Beta2. Let me know (I'm "dhorak" on internal IRC) if you would need access to one of the Fedora builders.
build of glibc-2.12.90-10 failed with the same problem, this time only on s390 and s390x was OK, see http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=205809 for details
I'm unable to reproduce that on RHEL6 either.
Seems it's not 100% reproducible. I did 2 builds (s390x) today in the Fedora 14 chroot running on top of RHEL6 and the first run successful, but in the second one I got the endless loop.
glibc-2.12.90-13 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/glibc-2.12.90-13
glibc-2.12.90-13 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update glibc'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/glibc-2.12.90-13
Builds and runs fine on s390(x), thanks for the fix.
glibc-2.12.90-14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update glibc'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/glibc-2.12.90-14
glibc-2.12.90-14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.