this is still present in 2.6.22. all discussion, and its appearance in all distros suggests that this is a kernel bug that has not been fixed yet
this is still present in 2.6.22. all discussion, and its appearance in all distros suggests that this is a kernel bug that has not been fixed yet