Comment 11 for bug 884181

Well, for any running into this same issue with the unexplainable kernel spew, I've found a way around it. It seems if a fork sleeps for >= 1 microsecond (0.000001 seconds) immediately after creation, all proceeds normally (this value may vary). Any less, and it vomits. This would appear to have something to do with the EC2 hypervisor's inner workings, at the hardware or kernel level methinks.