That was a linux kernel bug, nothing to do with Go.