https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
--- Comment #94 from Don Lewis <[email protected]> --- In my latest experiment, I still restricted the steal_idle to the CCX of the current SMT thread. At the CCX level, I changed thresh back to 1, but I also excluded the current core so that stealing from the other SMT thread can only happen if the steal_thresh condition was met for it on the first pass. I still a fair amount of build fallout. In addition to the usual ghc SIGBUS, I also saw a couple of clang SIGABRT failures when building security/nss and www/webkit2-gtk3. Also lang/go failed with these errors: fatal error: runtime\xc2\xb7lock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count fatal error: runtime\xc2\xb7unlock: lock count [snip] fatal: morestack on g0 SIGTRAP: trace trap PC=0x44ef02 m=1 sigcode=1 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
