Comment 26 for bug 1253155

Just had the same error in Ubuntu 14.04, but noticed that it only occured AFTER I had updated from kernel 3.19.0-30-generic #33 to 3.19.0-30-generic #34 and especially after loading any new module.

Kernel 3.19.0-30-generic #33 and 3.19.0-30-generic #34 has the same path so it makes sense that it's an incompability between loading 3.19.0-30-generic #34 modules into the already running 3.19.0-30-generic #33 kernel.

A simple reboot and no errors.