On Fri, Sep 19, 2008 at 09:40:39AM +0930, Kevin Shanahan wrote:
> No idea what I can do to help resolve this, but thought I may as well
> just confirm that this same issue is present in the latest
> linux-image-2.6.26-1-686, version 2.6.26-5.
Could you try the 2.6.30 kernel from backports.org to test, whether
this fixed by upstream kernel changes in the mean time?
Cheers,
Moritz