I can confirm this bug on an Asus L3T running the last feisty. It appear when usion kernel 2.6.20; with 2.6.17 this error doesn't appear
I can confirm this bug on an Asus L3T running the last feisty.
It appear when usion kernel 2.6.20; with 2.6.17 this error doesn't appear