Comment 19 for bug 156066

Revision history for this message
Stefan Bader (smb) wrote :

It might be related to the fact that acpi-cpufreq is built in now and the second choice. The expectation would be that if acpi does not find support, it should pass on to the next driver in the stack. I did not find any objects that acpi-cpufreq is needing, so that should be the case. However not much can be seen in the usual log. To enable dbugging for acpi and cpufreq I had to create a special kernel. It can be found at http://people.ubuntu.com/~smb/bug156066/. With that installed, you can use the option: "cpufreq.debug=7" on the grub commandline and we should get more output. Can you attach the dmesg of that, please?