Does this bug still happen if you boot back into a supported Precise kernel instead of the upstream kernel?
Does this bug still happen if you boot back into a supported Precise kernel instead of the upstream kernel?