Re: cpufreq stops working after a while

[Mark Lord]

Dave Jones wrote:
> boot with cpufreq.debug=7, and capture dmesg output after it fails
> to transition.  This might be another manifestation of the mysterious
> "highest frequency isnt accessable" bug, that seems to come from
> some recent change in acpi.

booting with that option doesn't seem to give me any new messages
in dmesg (or /var/log/messages).  I also tried editing cpufreq.c
and hardcoding debug = 7 on the variable declaration.
Still no new messages.

??
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/