> I tried a new kernel with this patch applied, but no changes in > behaviour: can you still reproduce that bug with an uptodate linux image aka at least 2.6.24 or better supported 2.6.25? thanks for feedback. -- maks