Comment 2 for bug 601226

Through some slow, extensive testing, I have been able to reproduce this bug on Lucid with kernel 2.6.33-502-omap by typing " sudo modprobe parport_pc" in a console. When looking at the differences between 2.6.33 and 2.6.35 kernels, I noticed ppdev was added (probably in 2.6.34) recently. While this module doesn't appear to depend on parport_pc, I have yet to figure out why parport_pc is loaded in the new image.

Adding "blacklist parport_pc" to /etc/modules.d/blacklist.conf seems to eliminate the problem, in that the system no longer tries to load that module. Not sure if this is a proper fix, but it is an easy one. The other solution is a fix from the upstream kernel, and I have not been able to find a bug report upstream yet (connection issues with kerneloops.org).