Looks like the patches noted in the upstream bug report should resolve this issue. They appear to be making their way into the upstream 2.6.35.y stable kernel. They'll automatically get pulled into the Maverick kernel as a SRU (stable release update) when we sync up with the upstream stable version which contains the patches.
Looks like the patches noted in the upstream bug report should resolve this issue. They appear to be making their way into the upstream 2.6.35.y stable kernel. They'll automatically get pulled into the Maverick kernel as a SRU (stable release update) when we sync up with the upstream stable version which contains the patches.