Error in CPU frequency reporting when nominal and min pstates are same (cpufreq)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
High
|
Canonical Kernel Team | ||
linux (Ubuntu) |
Fix Released
|
High
|
Joseph Salisbury | ||
Artful |
Fix Released
|
High
|
Joseph Salisbury | ||
Bionic |
Fix Released
|
High
|
Joseph Salisbury |
Bug Description
== SRU Justification ==
Commit 09ca4c9b5958 introduced a bug in v4.8-rc2. The bug is that
an error happens in CPU frequency reporting when nominal and min pstates
are the same (cpufreq). Commit 3fa4680b8 fixes this issue.
Commit 3fa4680b8 is in mailine as of v4.16-rc1 and has been cc'd to upstream stable.
== Fix ==
commit 3fa4680b860bf48
Author: Shilpasri G Bhat <email address hidden>
Date: Fri Jan 12 12:43:53 2018 +0530
cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
== Regression Potential ==
Low. This commit been cc'd to upstream stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Shilpasri G. Bhat
+++ This bug was initially created as a clone of Bug #163527 +++
---Problem Description---
Error in CPU frequency reporting when nominal and min pstates are same
The patch for this issue is accepted to linux-next as
3fa4680b860bf48
cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin
Some OpenPOWER boxes can have same pstate values for nominal and
pmin pstates. In these boxes the current code will not initialize
'powernv_
frequency reporting. This patch fixes this problem.
Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <email address hidden>
Signed-off-by: Shilpasri G Bhat <email address hidden>
Acked-by: Viresh Kumar <email address hidden>
Cc: 4.8+ <email address hidden> # 4.8+
Signed-off-by: Rafael J. Wysocki <email address hidden>
break-fix: - cf0de9a0d52ff64
break-fix: - 3fa4680b860bf48
tags: | added: architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
tags: | added: triage-g |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Artful): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in ubuntu-power-systems: | |
status: | New → In Progress |
Changed in ubuntu-power-systems: | |
status: | In Progress → Incomplete |
tags: | added: kernel-bug-break-fix |
description: | updated |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Artful): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | Incomplete → Fix Committed |
tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin--- |
tags: | added: cscc |
I built a test kernel with commit 3fa4680b860bf48 b437d6a2c039789 c4abe202ae. The test kernel can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1746174
http://
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages.
Thanks in advance!