Running kernel 2.6.37 rc 2 on Maverick the issue no longer exists. Seems that the upstream has decided what to do. Could this now be pulled to the 2.6.35 kernel of Maverick?
Running kernel 2.6.37 rc 2 on Maverick the issue no longer exists. Seems that the upstream has decided what to do. Could this now be pulled to the 2.6.35 kernel of Maverick?