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. Regards, Kevin.