Hi Jonathan, Current kernels don't reproduce this problem. The bug can be closed since 2.6.33 is no longer used. Jos v.W.