cpufreq: powernv : Decrease the severity of console messages
Bug #1500672 reported by
bugproxy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Tim Gardner | ||
Wily |
Fix Released
|
Undecided
|
Tim Gardner |
Bug Description
"CPU Frequency could be throttled" dmesg is logged with critical log level when the max frequency is clipped. This message should be logged to 'info' if the frequency is throttled between nominal and turbo and not as critical.
Fix for this involves the below two patches:
1)053819e0bf840
tags: | added: architecture-ppc64le bugnameltc-131119 severity-high targetmilestone-inin14044 |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
To post a comment you must log in.
7b3c0b652380893 cdb8139045b093c e4b8e57264 ('UBUNTU: SAUCE: cpufreq: powernv: Handle throttling due to Pmax capping at chip level') has been applied since Ubuntu-4.2.0-6.6.
Applied:
cpufreq : powernv: Report Pmax throttling if capped below nominal frequency
cpufreq: powernv: Increase the verbosity of OCC console messages