Comment 104 for bug 644898

I'm just coming into this discussion so please be kind. It seems from what I've seen that the upstream developers think that this issue should be fixed in the current kernel (possibly earlier but let's ignore that for now). It looks from comment #103 that the problem still exists in the current (Precise) kernel.

Has anyone from this thread / bug tried to engage with the upstream developer(s) to let them know this issue still exists?