Hi Riccardo, Am 26.03.2015 um 16:12 schrieb Riccardo Mottola <[email protected]>: > did you have perhaps time investigating why I got those lockups on the > solaris 9 build hosts?
Yes. As I wrote earlier it is some kind of locking problem. The stacktrace looks like this: unstable9s% pstack 15521 15521: git am --ignore-space-change --ignore-whitespace /home/dam/mgar/pkg/ar ff3dcba4 lwp_park (0, 0, 0) ff3d3d3c s9_lwp_park (0, 0, 0, 0, 0, 0) + 6c ff3dcb08 s9_handler (0, 0, 0, 0, 0, 0) + 90 feca11bc mutex_lock_queue (fecb8c04, 0, feda2408, 0, 0, 0) + 104 feca18cc mutex_lock_internal (0, 0, fecb0000, 0, 0, 0) + 610 fed78a28 atfork_append (0, 0, fef1d060, feda2404, feda2408, 0) + 4 fed78b94 pthread_atfork (0, 0, fef1d060, fffbf8dc, 40400, 406e0) + 24 fef1d0dc ???????? (fef1d060, fef63a18, 0, 6000, fef63a18, 6000) fed78d70 run_postfork_child (feda23f0, feda2408, 2526c, fec9cfa8, 5, 0) + 24 fec9cfa8 fork1 (1, 1afc8, 0, 0, 0, 0) + f4 fec9d05c fork (0, 4, ffbff3b8, 223544, 1b5d80, 0) + 28 00151534 start_command (ffbff49c, 0, 9, 0, 0, 0) + 220 00151b80 run_command (ffbff49c, 0, 20, 0, 8, 8) + 4 00151cac run_command_v_opt (ffbff658, 28, 1e6c00, 223544, 1b5d80, 0) + 14 000212a8 ???????? (ffbff658, ffffffff, 1fc000, 223544, 1aadd0, 0) 00021308 ???????? (ffbff634, ffbff638, ffbffa90, 1dadc8, 0, 1b5000) 00021448 main (ffbff658, ffbff634, 1fc818, 1b6fe8, ffbff638, ffbff7a0) + f8 0001f840 _start (0, ffbff654, 1, ff3dca78, ff3ee850, ff3ee000) + 108 I just updated unstable9s to the latest Solaris 9 patchcluster with no change in behaviour. If anyone has suggestions I am all ears. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
smime.p7s
Description: S/MIME cryptographic signature
