It seems 2.6.35-17.23 has been published.
I believe all the duplicates of this bug were running 2.6.35-16.22
You should upgrade the kernel and check whether this triggers there too.
It seems 2.6.35-17.23 has been published.
I believe all the duplicates of this bug were running 2.6.35-16.22
You should upgrade the kernel and check whether this triggers there too.