I experienced the same bug after an upgrade from raring to saucy with the same model. I just tested the upstream kernel, but the same bug seems to exist there. I added the corresponding tag.
I can work around the issue by booting into the raring kernel (3.8.0-31), which was still installed after the upgrade.
I experienced the same bug after an upgrade from raring to saucy with the same model. I just tested the upstream kernel, but the same bug seems to exist there. I added the corresponding tag.
I can work around the issue by booting into the raring kernel (3.8.0-31), which was still installed after the upgrade.