Comment 13 for bug 984088

@Joseph, I tested the latest 3.2 stable kernel (3.2.39-030239). It did not fix the problem.

However, I discovered a workaround, which does (maybe it introduces another problem I am not aware of?): I blacklisted 'mei'. I added

blacklist mei

to

/etc/modprobe.d/blacklist.conf

Now I do not get these errors anymore, no matter if I use 3.2.38 or 3.2.39.

I found this workaround here:
http://ubuntuforums.org/showthread.php?t=1970325

Does this help to fix the problem for all users of Precise?