Upstream is already aware of the issue, see
http://www.spinics.net/lists/kernel/msg1418335.html
So the only thing that needs to be determined, is which quantal patch to the 3.5 mainline has introduced the bug.
Upstream is already aware of the issue, see
http:// www.spinics. net/lists/ kernel/ msg1418335. html
So the only thing that needs to be determined, is which quantal patch to the 3.5 mainline has introduced the bug.