Brice Goglin wrote: > You just don't have the same bug. Perhaps, mighty coincidence though. BTW, the problem persists for me even with 2.6.31-rc3 kernel. Tomas