Ubuntu
linux package

  1. Bug #1763817
  2. Activity log

Activity log for bug #1763817

Date Who What changed Old value New value Message
2018-04-13 19:14:39 Manoj Iyer bug added bug
2018-04-13 19:23:31 Manoj Iyer nominated for series Ubuntu Bionic
2018-04-13 19:23:48 Manoj Iyer linux (Ubuntu): assignee Canonical Kernel Team (canonical-kernel-team)
2018-04-13 19:27:13 Manoj Iyer description [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700 cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 -- after kernel patch -- [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700     cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 -- after kernel patch --
2018-04-13 19:27:55 Manoj Iyer description [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700     cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 -- after kernel patch -- [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700     cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:36 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux -- after kernel patch --
2018-04-13 19:30:05 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2018-04-13 19:30:07 Ubuntu Kernel Bot tags starbuck bionic starbuck
2018-04-13 20:42:16 Manoj Iyer description [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700     cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:36 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux -- after kernel patch -- [Impact] On ARM64 systems enabling cppccontrol=1 in firmware, the dmesg fills with messages like: [ 4083.960332] ACPI CPPC: PCC check channel failed. Status=0 [ 4085.546975] ACPI CPPC: PCC check channel failed. Status=0 [ 4113.939921] ACPI CPPC: PCC check channel failed. Status=0 [ 4115.531777] ACPI CPPC: PCC check channel failed. Status=0 We lose any useful data in dmesg and on the console. [Fix] upstream commit fixes this issue: commit 3d41386d556db9f720e00de3e11e45f39cb5071c Author: George Cherian <george.cherian@cavium.com> Date: Fri Mar 23 03:30:31 2018 -0700     cpufreq: CPPC: Use transition_delay_us depending transition_latency [Testing] -- before kernel patch -- Both console output and dmesg are filled with the message ACPI CPPC: PCC check channel failed. Status=0 [ 85.969952] ACPI CPPC: PCC check channel failed. Status=0 [ 81.888445] cloud-init[4810]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 19:11:57 +0000. Up 80.71 seconds. [ 81.888625] cloud-init[4810]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 19:11:58 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 81.69 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. [ 86.230432] ACPI CPPC: PCC check channel failed. Status=0 [ 86.701943] ACPI CPPC: PCC check channel failed. Status=0 [ 86.773668] ACPI CPPC: PCC check channel failed. Status=0 [ 87.369958] ACPI CPPC: PCC check channel failed. Status=0 [ 87.733361] ACPI CPPC: PCC check channel failed. Status=0 [ 88.207372] ACPI CPPC: PCC check channel failed. Status=0 ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:36 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux -- after kernel patch -- OK ] Started Apply the settings specified in cloud-config. Starting Execute cloud user/final scripts... [ 67.178425] cloud-init[3688]: Cloud-init v. 18.2 running 'modules:final' at Fri, 13 Apr 2018 20:41:15 +0000. Up 65.98 seconds. [ 67.200190] cloud-init[3688]: Cloud-init v. 18.2 finished at Fri, 13 Apr 2018 20:41:15 +0000. Datasource DataSourceMAAS [http://10.228.68.5:5240/MAAS/metadata/]. Up 66.83 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target. Ubuntu Bionic Beaver (development branch) starbuck ttyAMA0 starbuck login: ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-15-generic #16~lp1763817+build.1 SMP Fri Apr 13 19:54:10 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux [Regression Potential] None.
2018-04-13 20:45:10 Manoj Iyer linux (Ubuntu): assignee Canonical Kernel Team (canonical-kernel-team) Manoj Iyer (manjo)
2019-07-24 21:03:20 Brad Figg tags bionic starbuck bionic cscc starbuck