Comment 59 for bug 950296

Sorry for the sassy comment, but your answer was not much more helpful though. The instructions are not to difficult, but building thousands of kernel commits to pinpoint a specific one do feel like a huge waste of time when someone with knowledge of the subsystem (and the specific driver for my hardware) could check what error I get and see when that part of the code (or parts which might affect it) might have been changed, and what changes were made.
Especially since I would have no idea how well a 2.6.31-kernel would work in an Ubuntu 12.04 system.

However, I do understand that it's quite hard to debug without actually having access to my specific hardware, and I'll gladly help with more information, or testing patches, etc.