As noted earlier the original bug was confirmed fixed in 2.6.33 upstream. And the only activity here seems to be in kernel 2.6, so I doubt anyone is still running into this issue.
As noted earlier the original bug was confirmed fixed in 2.6.33 upstream. And the only activity here seems to be in kernel 2.6, so I doubt anyone is still running into this issue.