------- Comment From shriy...@in.ibm.com 2018-02-26 06:09 EDT------- Hi , Can you please let us know in which build the fix is available ?
I am able to see issue on : root@ltc-boston27:~# dmesg | grep freq [ 0.000000] time_init: decrementer frequency = 512.000000 MHz [ 0.000000] time_init: processor frequency = 2134.000000 MHz [ 2.159457] powernv-cpufreq: cpufreq pstate min 98 nominal 98 max 0 [ 2.159459] powernv-cpufreq: Workload Optimized Frequency is enabled in the platform [ 2.164178] powernv-cpufreq: pstate 97 is out of bound ubuntu@ltc-boston27:~$ uname -a Linux ltc-boston27 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746174 Title: Error in CPU frequency reporting when nominal and min pstates are same (cpufreq) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress 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 3fa4680b860bf48b437d6a2c039789c4abe202ae Author: Shilpasri G Bhat <shilpa.b...@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 <wan...@tw.ibm.com> Signed-off-by: Shilpasri G Bhat <shilpa.b...@linux.vnet.ibm.com> Acked-by: Viresh Kumar <viresh.ku...@linaro.org> Cc: 4.8+ <sta...@vger.kernel.org> # 4.8+ Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
