[Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram

bugzilla-daemon
2013-03-19T08:27:03Z

--- Comment #12 from Viresh Kumar <viresh.kumar@linaro.org> 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.