I noticed you added the kernel-fixed-upstream tag in comment #45. However, it sounds like this bug still exists in v3.5? If so, would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.
If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.
@Jeff,
I noticed you added the kernel- fixed-upstream tag in comment #45. However, it sounds like this bug still exists in v3.5? If so, would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.
If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.
[1] https:/ /wiki.ubuntu. com/Bugs/ Upstream/ kernel