Comment 33 for bug 925350

wild_oscar: Was that with a "working" kernel or the broken one? It looks like I wasn't very clear, sorry about that. If possible what I'd really like to know is the value in the broken kernel. I realize that can be challenging though. Would it be possible for you to ssh into the machine to read the value, or perhaps to connect it to an external monitor?

As for the modprobe.d files, it could in theory be any of them. Try running 'grep i915 /etc/modprobe.d/*' and see if anything turns up. Also paste the output of 'cat /proc/cmdline'. But you're right that the configuration for grub isn't specifying a value.

The thing is, if you are not supplying a value for the parameter then it doesn't make sense that this commit would be identified as the first bad one in the bisection. The only functional change it has is to how the lvds_use_ssc parameter is interpreted. If you are not supplying the value, the functionality for that commit should be identical to the prior commit. So if you aren't supplying a value then I have to suspect that something went wrong with the bisection.