Justin Pryzby wrote:
Could you test if this problem exists while running the latest kernel? I think kernel 2.6.18 was ok, and upgrading to linux-image-2.6.24-1-686_2.6.24-5 (from -4) seems to have resolved this for me.
I'm not seeing this on 2.6.25-rc7 anymore, not sure about 2.6.24 now. Cheers, Marcus