Comment 10 for bug 903558

I am really confused now... it looks like the kernel config file itself is the cause of my woes.

I was given a slimmed down copy of the kernel config optimized for a Thinkpad L520 to use when building the kernel to make it quicker, which I started using after my previous comment on this ticket when I went through the 'git bisect' process. I went through the whole thing without any errors - it reported the broken commit being the one creating the tag!

So I tested that config file generating on the latest/master from the git repo, and it worked.

This was weird, since I'd tested these builds before with no success. So I went back and used the config file for the stock kernel installed on ubuntu (/boot/config-3.2.0-14-generic), and now any build I try is broken.

I can only assume that there is something in the config file I was provided which enables something my laptop needs?
Being a configuration parameter it would explain why some builds worked and others didn't, it would depend on whatever kernel config I was booted into at the time (I was using 'cp /boot/config-`uname -r` .config' before to generate it for each compile).

So, how do I go about debugging the config file? I wouldn't know where to start!