Bug#1040817: glibc: Please ignore some tests on sparc64
Source: glibc Version: 2.37-5 Severity: normal User: debian-sp...@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sp...@lists.debian.org Hi! The list of currently failing tests on sparc64 is: FAIL: elf/tst-audit24a FAIL: elf/tst-audit24b FAIL: elf/tst-audit24c FAIL: elf/tst-audit24d FAIL: elf/tst-rtld-run-static FAIL: nptl/tst-cancel24-static FAIL: nptl/tst-cancel30 FAIL: socket/tst-socket-timestamp FAIL: stdlib/isomac According to upstream, the following audit tests are not going to be fixed soon since the SPARC ABI makes it more difficult: FAIL: elf/tst-audit24a FAIL: elf/tst-audit24b FAIL: elf/tst-audit24c FAIL: elf/tst-audit24d These are going to be fixed upstream soon, the fixes are supposedly trivial: FAIL: elf/tst-rtld-run-static FAIL: nptl/tst-cancel24-static FAIL: nptl/tst-cancel30 This test is supposedly a kernel issue: FAIL: socket/tst-socket-timestamp And this one allegedly not related to sparc64: FAIL: stdlib/isomac So, my suggestion would be to ignore the following tests for now: FAIL: elf/tst-audit24a FAIL: elf/tst-audit24b FAIL: elf/tst-audit24c FAIL: elf/tst-audit24d FAIL: socket/tst-socket-timestamp FAIL: stdlib/isomac And looking at the testsuite results with 32-bit tests enabled [1], it looks like the failures are the same. So, I think we can just ignore the above tests and then re-enable testing on 32 bit as well. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.37-1&stamp=1684283585&raw=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1040716: libc6: Stack Traces
On Mon, 2023-07-10 at 23:17 +0200, Aurelien Jarno wrote: > Hi, > > On 2023-07-09 17:15, Tim McConnell wrote: > > Hi Aurelien, > > The Stack Traces started showing up in my System Event logs > > yesterday > > and has totaled up to 18 times so far. As far as issues, the system > > is > > slower than usual and occasionally freezes. > > I ran apt-file search lib.so and came up with libc6 so that's > > where I > > filed the bug. I tried running gdb on it (libc6) and it told me > > file > > not found, I'd be happy to give more information just tell me how > > to > > get it. > > Thanks for the details, however I am afraid it is not enough. libc6 > is a > library, for understanding the issue, I would need to know by which > program it is used in the corresponding stack traces. The issue might > not be in the library but in another library or another program. Do > you > have some more log entries around those stack traces? > > All that said, it appears that the locales package in versions 2.37-2 > to > 2.37-4 is buggy and might cause random crashes in libc6. You might > want > to upgrade to version 2.37-5 to check if it solves your issue. The > package is currently only available in sid, but it is expected to > migrate to testing in the next days. > > Regards > Aurelien > Checking Journalctl I found this: Jul 10 19:02:11 DebianTim systemd-coredump[3869]: [🡕] Process 992 (collectd) of user 0 dumped core. Module libudev.so.1 from deb systemd-252.11-1.amd64 Stack trace of thread 1424: #0 0x7f7cbbfce9f2 __memmove_ssse3 (libc.so.6 + 0x16d9f2) #1 0x7f7cbbd856d9 rrd_write (librrd.so.8 + 0x346d9) #2 0x7f7cbbd90acd n/a (librrd.so.8 + 0x3facd) #3 0x7f7cbbd92962 n/a (librrd.so.8 + 0x41962) #4 0x7f7cbbdec370 n/a (rrdtool.so + 0x3370) #5 0x7f7cbbee93ec start_thread (libc.so.6 + 0x883ec) #6 0x7f7cbbf69a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 1431: #0 0x7f7cbbee6156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f7cbbee8afc __pthread_cond_wait_common (libc.so.6 + 0x87afc) #2 0x5586e89f93a2 n/a (collectd + 0x123a2) #3 0x7f7cbbee93ec start_thread (libc.so.6 + 0x883ec) #4 0x7f7cbbf69a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 1432: #0 0x7f7cbbee6156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f7cbbee8afc __pthread_cond_wait_common (libc.so.6 + 0x87afc) #2 0x5586e89f93a2 n/a (collectd + 0x123a2) #3 0x7f7cbbee93ec start_thread (libc.so.6 + 0x883ec) #4 0x7f7cbbf69a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 1427: #0 0x7f7cbbee6156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f7cbbee8818 __pthread_cond_wait_common (libc.so.6 + 0x87818) #2 0x5586e89f7d1b n/a (collectd + 0x10d1b) #3 0x7f7cbbee93ec start_thread (libc.so.6 + 0x883ec) #4 0x7f7cbbf69a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 1429: #0 0x7f7cbbee6156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f7cbbee8818 __pthread_cond_wait_common (libc.so.6 + 0x87818) #2 0x5586e89f7d1b n/a (collectd + 0x10d1b) Stack trace of
Bug#1040716: libc6: Stack Traces
On Mon, 2023-07-10 at 23:17 +0200, Aurelien Jarno wrote: > Hi, > > On 2023-07-09 17:15, Tim McConnell wrote: > > Hi Aurelien, > > The Stack Traces started showing up in my System Event logs > > yesterday > > and has totaled up to 18 times so far. As far as issues, the system > > is > > slower than usual and occasionally freezes. > > I ran apt-file search lib.so and came up with libc6 so that's > > where I > > filed the bug. I tried running gdb on it (libc6) and it told me > > file > > not found, I'd be happy to give more information just tell me how > > to > > get it. > > Thanks for the details, however I am afraid it is not enough. libc6 > is a > library, for understanding the issue, I would need to know by which > program it is used in the corresponding stack traces. The issue might > not be in the library but in another library or another program. Do > you > have some more log entries around those stack traces? > > All that said, it appears that the locales package in versions 2.37-2 > to > 2.37-4 is buggy and might cause random crashes in libc6. You might > want > to upgrade to version 2.37-5 to check if it solves your issue. The > package is currently only available in sid, but it is expected to > migrate to testing in the next days. > > Regards > Aurelien > I'll check journalctl and see if that has better info. I'll also upgrade the package you were talking about to see if it fixes the issue . I will let you know.
Bug#1040716: libc6: Stack Traces
Hi, On 2023-07-09 17:15, Tim McConnell wrote: > Hi Aurelien, > The Stack Traces started showing up in my System Event logs yesterday > and has totaled up to 18 times so far. As far as issues, the system is > slower than usual and occasionally freezes. > I ran apt-file search lib.so and came up with libc6 so that's where I > filed the bug. I tried running gdb on it (libc6) and it told me file > not found, I'd be happy to give more information just tell me how to > get it. Thanks for the details, however I am afraid it is not enough. libc6 is a library, for understanding the issue, I would need to know by which program it is used in the corresponding stack traces. The issue might not be in the library but in another library or another program. Do you have some more log entries around those stack traces? All that said, it appears that the locales package in versions 2.37-2 to 2.37-4 is buggy and might cause random crashes in libc6. You might want to upgrade to version 2.37-5 to check if it solves your issue. The package is currently only available in sid, but it is expected to migrate to testing in the next days. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
