Will this also be fixed in the linux-image-3.2.0-4-486 kernel?  It seems to
be affecting that one too.

Reply via email to