Thx, but in which 2.6.35 kernel the bug is fixed? In 2.6.35.3-10.fc14.x86_64 i had already this error.
Thx, 3-10.fc14. x86_64 i had already this error.
but in which 2.6.35 kernel the bug is fixed?
In 2.6.35.