https://bugzilla.kernel.org/show_bug.cgi?id=55411 --- Comment #12 from Viresh Kumar <viresh.kumar@xxxxxxxxxx> 2013-03-19 08:27:02 --- (In reply to comment #11) > (In reply to comment #6) > > > BTW, it will be good if you can provide me suspend/resume log with all debug > > prints enabled. > > I take it that shouldn't be necessary with the new reproducer? But a debug log > from the offline/online cycle would be useful? > > You meant dmesg, correct? I take it the originally attached dmesg didn't have > the kernel config debug options enabled that you need? Which specific options > enabled, anything I need to echo into an appropriate sysfs file, etc? There's > a LOT of kernel debug options to choose from but I guess most of them wouldn't > be particularly helpful here, so I think you didn't really mean *ALL* of them. > =;^) I don't need any logs now. I wanted the logs with following added to the top of drivers/cpufreq/Makefile: ccflags-y := -DDEBUG -DVERBOSE_DEBUG But not required now. > (In reply to comment #10) > > > I believe you are using acpi-cpufreq driver, right? > > Yes, the acpi p-states driver, X86_ACPI_CPUFREQ. AFAIK it was previously the > k8 powernow driver, X86_POWERNOW_K8, but a kernel or two ago I noticed > complaints in the kernel log saying to switch to the acpi driver, so I disabled > the powernow driver (acpi p-states was already enabled, monolithic kernel as I > mentioned above) and rebooted, and cpufreq continued to work, so I stayed with > the acpi driver. I think i know the issue now, but don't have sufficient knowledge to give a fix. I will circulate a mail to people who can do this. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
