Indeed. This is a Linux bug that affects only 64-bit kernels. It was
introduced in July 2008
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=6c5d0512a091480c9f981162227fdb1c9d70e555
and only fixed in May 2009
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=2b79bc4f7ebbd5af3c8b867968f9f15602d5f802
I'm applying this supposed workaround
I'm undecided whether it's better to talk about dates, or rather say
"2.6.27 to 2.6.29"; it's less precise, but will give a simpler hint
about whether your kernel is broken.
Paolo
