I can confirm that the problem also occurs with kernel 2.6.35-7. I see that the bug is still unassigned, is somebody looking at it?
I can confirm that the problem also occurs with kernel 2.6.35-7. I see that the bug is still unassigned, is somebody looking at it?