Ralf Stephan wrote: > Does anyone else get these segfaults in the kernel log?
Yup. But they seem to originate from builds, not testing. (I also do have segfaults in some conftests which always "immediately" precede the one in gentourng, although regarding the pids, the former apparently belong to different packages.) And I don't have them on every machine. -leif > Aug 29 17:28:04 ark kernel: gentourng[1549]: segfault at 40065a02c ip > 00000000004018 > 1f sp 00007ffce9d03520 error 4 in gentourng[400000+19000] > Aug 30 17:03:54 ark kernel: gentourng[20347]: segfault at 401d4402c ip > 0000000000401 > 81f sp 00007ffe5bca7d60 error 4 in gentourng[400000+19000] > Aug 31 11:44:22 ark kernel: gentourng[1779]: segfault at 401f1502c ip > 00000000004018 > 1f sp 00007fff9a7f4720 error 4 in gentourng[400000+19000] > Aug 31 15:09:49 ark kernel: gentourng[10162]: segfault at 401d8502c ip > 0000000000401 > 81f sp 00007fff310eeea0 error 4 in gentourng[400000+19000] > > I can associate them with patchbot or ptestlong runs. > They go as far back as Apr 20 (limited by my kernel log). -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
