| 2018-01-30 07:10:56 |
bugproxy |
bug |
|
|
added bug |
| 2018-01-30 07:10:58 |
bugproxy |
tags |
|
architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- |
|
| 2018-01-30 07:10:59 |
bugproxy |
ubuntu: assignee |
|
Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
|
| 2018-01-30 07:11:03 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2018-01-30 07:23:14 |
Frank Heimes |
bug task added |
|
ubuntu-power-systems |
|
| 2018-01-30 07:23:19 |
Frank Heimes |
ubuntu-power-systems: importance |
Undecided |
High |
|
| 2018-01-30 07:23:30 |
Frank Heimes |
ubuntu-power-systems: assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
| 2018-01-30 07:23:41 |
Frank Heimes |
tags |
architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- |
architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- triage-g |
|
| 2018-01-30 20:38:43 |
Joseph Salisbury |
linux (Ubuntu): status |
New |
In Progress |
|
| 2018-01-30 20:38:47 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2018-01-30 20:38:50 |
Joseph Salisbury |
linux (Ubuntu): assignee |
Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
Joseph Salisbury (jsalisbury) |
|
| 2018-01-30 20:43:03 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-01-30 20:43:03 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2018-01-30 20:43:03 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Artful |
|
| 2018-01-30 20:43:03 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2018-01-30 20:43:09 |
Joseph Salisbury |
linux (Ubuntu Artful): status |
New |
In Progress |
|
| 2018-01-30 20:43:12 |
Joseph Salisbury |
linux (Ubuntu Artful): importance |
Undecided |
High |
|
| 2018-01-30 20:43:15 |
Joseph Salisbury |
linux (Ubuntu Artful): assignee |
|
Joseph Salisbury (jsalisbury) |
|
| 2018-01-30 21:09:34 |
Frank Heimes |
ubuntu-power-systems: status |
New |
In Progress |
|
| 2018-02-12 15:17:46 |
Manoj Iyer |
ubuntu-power-systems: status |
In Progress |
Incomplete |
|
| 2018-02-16 16:30:22 |
Joseph Salisbury |
description |
== 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
3fa4680b860bf48b437d6a2c039789c4abe202ae
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_pstate_info.min' variable and result in erroneous CPU
frequency reporting. This patch fixes this problem.
Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <wangat@tw.ibm.com>
Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Cc: 4.8+ <stable@vger.kernel.org> # 4.8+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae |
== 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 3fa4680b860bf48b437d6a2c039789c4abe202ae
Author: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
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
3fa4680b860bf48b437d6a2c039789c4abe202ae
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_pstate_info.min' variable and result in erroneous CPU
frequency reporting. This patch fixes this problem.
Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <wangat@tw.ibm.com>
Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Cc: 4.8+ <stable@vger.kernel.org> # 4.8+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae |
|
| 2018-03-01 12:20:20 |
Thadeu Lima de Souza Cascardo |
tags |
architecture-ppc64le bugnameltc-163614 severity-high targetmilestone-inin--- triage-g |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin--- triage-g |
|
| 2018-03-01 12:22:07 |
Thadeu Lima de Souza Cascardo |
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 3fa4680b860bf48b437d6a2c039789c4abe202ae
Author: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
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
3fa4680b860bf48b437d6a2c039789c4abe202ae
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_pstate_info.min' variable and result in erroneous CPU
frequency reporting. This patch fixes this problem.
Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <wangat@tw.ibm.com>
Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Cc: 4.8+ <stable@vger.kernel.org> # 4.8+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae |
== 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 3fa4680b860bf48b437d6a2c039789c4abe202ae
Author: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
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
3fa4680b860bf48b437d6a2c039789c4abe202ae
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_pstate_info.min' variable and result in erroneous CPU
frequency reporting. This patch fixes this problem.
Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <wangat@tw.ibm.com>
Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Cc: 4.8+ <stable@vger.kernel.org> # 4.8+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae
break-fix: - cf0de9a0d52ff64bcb6b20b6fa4b5d3eb4637719
break-fix: - 3fa4680b860bf48b437d6a2c039789c4abe202ae |
|
| 2018-03-01 12:22:24 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-03-01 13:41:30 |
Kleber Sacilotto de Souza |
linux (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2018-03-05 14:54:40 |
Manoj Iyer |
ubuntu-power-systems: status |
Incomplete |
Fix Committed |
|
| 2018-03-19 10:58:38 |
Stefan Bader |
tags |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin--- triage-g |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin--- triage-g verification-needed-artful |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
linux (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-0861 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-1000407 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-15129 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-16994 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17448 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17450 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17741 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17805 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17806 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2017-17807 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-1000026 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5332 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5333 |
|
| 2018-04-03 14:10:10 |
Launchpad Janitor |
cve linked |
|
2018-5344 |
|
| 2018-04-16 15:04:47 |
Manoj Iyer |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-04-16 15:04:54 |
Manoj Iyer |
ubuntu-power-systems: status |
Fix Committed |
Fix Released |
|
| 2018-10-11 08:59:45 |
bugproxy |
tags |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin--- triage-g verification-needed-artful |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin1804 triage-g verification-needed-artful |
|
| 2019-07-24 20:21:37 |
Brad Figg |
tags |
architecture-ppc64le bugnameltc-163614 kernel-bug-break-fix severity-high targetmilestone-inin1804 triage-g verification-needed-artful |
architecture-ppc64le bugnameltc-163614 cscc kernel-bug-break-fix severity-high targetmilestone-inin1804 triage-g verification-needed-artful |
|
