A little more work shows that if we do this: xrx node /bin/ENOENT Things don't fail. It's when files start to get pulled over that it blows up.
It does look like huge bits of the kernel data space are getting so completely trashed that the kernel can't even get through printing the oops info. We're trying 2.6.31 now that was known to work in 32 bit mode on a laptop ron
