Comment 6 for bug 730629

I've run into this problem on a MacBook Pro 8,3 on Oneiric. It looks like this may be fixed upstream in the 3.0.x linux kernel here:

http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.9

I'm not familiar enough with how the Ubuntu kernel handles upstream changes ... maybe someone can explain to me if this will make its way into the next updates or requires some additional input?