After looking at google it seems this might be a kernel bug - I don't really know, but this patch on the kernel mailing list is suggestive.

If this is the case, maybe it could be fixed in a future firmware, but outside of that it's probably not going to work.

It could well be something else though! It might be worth filing a bug report about it all the same.