We just hit that very same issue on Host running Lenny(inside an VMware
ESX4 Host).
The exact conditions for this to trigger here are:
* exactly ONE cpu/core configured on the host
* exactly 16GB RAM (using 8, 14 or 18GB does not cause the issue to appear)
* bash as the shell
removing one of the above variables cures the issue here so I would
argue that this actually might be a kernel bug
Stefan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
