From: Quentin Perret <qperret@google.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: rjw@rjwysocki.net, rafael@kernel.org, viresh.kumar@linaro.org,
arnd@arndb.de, mpe@ellerman.id.au, benh@kernel.crashing.org,
paulus@samba.org, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, kernel-team@android.com,
tkjos@google.com, adharmap@codeaurora.org, lkp@lists.01.org
Subject: Re: [cpufreq] d83f959b5e: kmsg.cpufreq:cpufreq_online:Failed_to_initialize_policy_for_cpu:#(-#)
Date: Tue, 23 Jun 2020 10:25:36 +0100 [thread overview]
Message-ID: <20200623092536.GA52234@google.com> (raw)
In-Reply-To: <20200622005457.GI5535@shao2-debian>
Hi,
Thanks for the report.
On Monday 22 Jun 2020 at 08:54:57 (+0800), kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: d83f959b5e7a6378a4afbff23de2a2d064d95749 ("[PATCH 2/2] cpufreq: Specify default governor on command line")
> url: https://github.com/0day-ci/linux/commits/Quentin-Perret/cpufreq-Specify-the-default-governor-on-command-line/20200616-005920
> base: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git linux-next
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-x86
> ucode: 0xdc
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
>
>
> [ 8.715369] intel_pstate: Intel P-state driver initializing
> [ 8.721146] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-61)
> [ 8.728900] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-61)
> [ 8.736615] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-61)
> [ 8.744400] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 3 (-61)
> [ 8.752222] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 4 (-61)
> [ 8.760010] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 5 (-61)
> [ 8.768077] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 6 (-61)
> [ 8.775891] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 7 (-61)
That, I think, is because of the issue I reported here:
https://lore.kernel.org/lkml/20200615174141.GA235811@google.com/
The v2 (to be posted shortly) will address this.
Thanks,
Quentin
WARNING: multiple messages have this Message-ID (diff)
From: Quentin Perret <qperret@google.com>
To: lkp@lists.01.org
Subject: Re: [cpufreq] d83f959b5e: kmsg.cpufreq:cpufreq_online:Failed_to_initialize_policy_for_cpu:#(-#)
Date: Tue, 23 Jun 2020 10:25:36 +0100 [thread overview]
Message-ID: <20200623092536.GA52234@google.com> (raw)
In-Reply-To: <20200622005457.GI5535@shao2-debian>
[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]
Hi,
Thanks for the report.
On Monday 22 Jun 2020 at 08:54:57 (+0800), kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: d83f959b5e7a6378a4afbff23de2a2d064d95749 ("[PATCH 2/2] cpufreq: Specify default governor on command line")
> url: https://github.com/0day-ci/linux/commits/Quentin-Perret/cpufreq-Specify-the-default-governor-on-command-line/20200616-005920
> base: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git linux-next
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-x86
> ucode: 0xdc
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
>
>
> [ 8.715369] intel_pstate: Intel P-state driver initializing
> [ 8.721146] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-61)
> [ 8.728900] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-61)
> [ 8.736615] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-61)
> [ 8.744400] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 3 (-61)
> [ 8.752222] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 4 (-61)
> [ 8.760010] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 5 (-61)
> [ 8.768077] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 6 (-61)
> [ 8.775891] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 7 (-61)
That, I think, is because of the issue I reported here:
https://lore.kernel.org/lkml/20200615174141.GA235811(a)google.com/
The v2 (to be posted shortly) will address this.
Thanks,
Quentin
WARNING: multiple messages have this Message-ID (diff)
From: Quentin Perret <qperret@google.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: juri.lelli@redhat.com, kernel-team@android.com,
vincent.guittot@linaro.org, arnd@arndb.de, rafael@kernel.org,
peterz@infradead.org, viresh.kumar@linaro.org,
adharmap@codeaurora.org, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
lkp@lists.01.org, mingo@redhat.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, tkjos@google.com
Subject: Re: [cpufreq] d83f959b5e: kmsg.cpufreq:cpufreq_online:Failed_to_initialize_policy_for_cpu:#(-#)
Date: Tue, 23 Jun 2020 10:25:36 +0100 [thread overview]
Message-ID: <20200623092536.GA52234@google.com> (raw)
In-Reply-To: <20200622005457.GI5535@shao2-debian>
Hi,
Thanks for the report.
On Monday 22 Jun 2020 at 08:54:57 (+0800), kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: d83f959b5e7a6378a4afbff23de2a2d064d95749 ("[PATCH 2/2] cpufreq: Specify default governor on command line")
> url: https://github.com/0day-ci/linux/commits/Quentin-Perret/cpufreq-Specify-the-default-governor-on-command-line/20200616-005920
> base: https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git linux-next
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-x86
> ucode: 0xdc
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
>
>
>
> [ 8.715369] intel_pstate: Intel P-state driver initializing
> [ 8.721146] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-61)
> [ 8.728900] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-61)
> [ 8.736615] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-61)
> [ 8.744400] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 3 (-61)
> [ 8.752222] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 4 (-61)
> [ 8.760010] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 5 (-61)
> [ 8.768077] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 6 (-61)
> [ 8.775891] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 7 (-61)
That, I think, is because of the issue I reported here:
https://lore.kernel.org/lkml/20200615174141.GA235811@google.com/
The v2 (to be posted shortly) will address this.
Thanks,
Quentin
next prev parent reply other threads:[~2020-06-23 9:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 16:55 [PATCH 0/2] cpufreq: Specify the default governor on command line Quentin Perret
2020-06-15 16:55 ` Quentin Perret
2020-06-15 16:55 ` [PATCH 1/2] cpufreq: Register governors at core_initcall Quentin Perret
2020-06-15 16:55 ` Quentin Perret
2020-06-16 4:28 ` Viresh Kumar
2020-06-16 4:28 ` Viresh Kumar
2020-06-16 8:31 ` Quentin Perret
2020-06-16 8:31 ` Quentin Perret
2020-06-15 16:55 ` [PATCH 2/2] cpufreq: Specify default governor on command line Quentin Perret
2020-06-15 16:55 ` Quentin Perret
2020-06-15 17:41 ` Quentin Perret
2020-06-15 17:41 ` Quentin Perret
2020-06-16 4:31 ` Viresh Kumar
2020-06-16 4:31 ` Viresh Kumar
2020-06-16 8:31 ` Quentin Perret
2020-06-16 8:31 ` Quentin Perret
2020-06-16 9:27 ` Viresh Kumar
2020-06-16 9:27 ` Viresh Kumar
2020-06-16 9:48 ` Quentin Perret
2020-06-16 9:48 ` Quentin Perret
2020-06-16 9:54 ` Viresh Kumar
2020-06-16 9:54 ` Viresh Kumar
2020-06-16 9:56 ` Quentin Perret
2020-06-16 9:56 ` Quentin Perret
2020-06-20 14:36 ` [cpufreq] d83f959b5e: aim7.jobs-per-min -30.2% regression kernel test robot
2020-06-20 14:36 ` kernel test robot
2020-06-22 0:54 ` [cpufreq] d83f959b5e: kmsg.cpufreq:cpufreq_online:Failed_to_initialize_policy_for_cpu:#(-#) kernel test robot
2020-06-22 0:54 ` kernel test robot
2020-06-22 0:54 ` kernel test robot
2020-06-23 9:25 ` Quentin Perret [this message]
2020-06-23 9:25 ` Quentin Perret
2020-06-23 9:25 ` Quentin Perret
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200623092536.GA52234@google.com \
--to=qperret@google.com \
--cc=adharmap@codeaurora.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@lists.01.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rong.a.chen@intel.com \
--cc=tkjos@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.