Comment 7 for bug 621371

ive got this issue on my system too with 35-16-generic-pae kernel, but what its strange is that even booting on the next kernel 35-17 (which have not this issue) and having 35-16 still installed , produce this error. So ive uninstalled 35-16 from synaptic and now this error is gone.

when we search "scheduling" or "atomic" on launchpad bug , a bunch of report are daily reported and seem to be related to this new D+ service: bug report 617757 617988