From: Guenter Roeck <linux@roeck-us.net>
To: Tony Lindgren <tony@atomide.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
Date: Mon, 15 Feb 2016 17:38:06 -0800 [thread overview]
Message-ID: <56C27D7E.4060603@roeck-us.net> (raw)
In-Reply-To: <20160215213606.GD19432@atomide.com>
On 02/15/2016 01:36 PM, Tony Lindgren wrote:
> * Rafael J. Wysocki <rafael@kernel.org> [160215 12:39]:
>> On Mon, Feb 15, 2016 at 8:58 PM, Tony Lindgren <tony@atomide.com> wrote:
>>> * Guenter Roeck <linux@roeck-us.net> [160215 11:41]:
>>>> On 02/15/2016 11:01 AM, Tony Lindgren wrote:
>>>>>
>>>>> https://kernelci.org/boot/all/job/next/kernel/next-20160215/
>>>>>
>>>>> The SMP ones seem to fail with some regulator issues?
>>>>>
>>>>
>>>> There is another problem, introduced with 6a0712f6f199e ("PM / OPP: Add
>>>> dev_pm_opp_set_rate()"). The kernelci boot log for next-20160212:omap3-overo-tobi
>>>> and others experience that problem.
>>>>
>>>> Essentially, the code now assumes that a CPU clock always has a voltage
>>>> regulator attached to it, which is not correct. I sent out a patch to fix
>>>> that problem a minute ago.
>>>
>>> Yes that fixed it thanks.
>>
>> Can you please also check if this alternative fix from Viresh works:
>>
>> https://patchwork.kernel.org/patch/8316611/
>
> Yes that one too seems to fix the issue on SMP systems for
> me:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
>
Same here.
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2016-02-16 1:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 17:05 Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...' Guenter Roeck
2016-02-15 18:41 ` Rafael J. Wysocki
2016-02-15 18:49 ` Rafael J. Wysocki
2016-02-15 18:49 ` Marc Zyngier
2016-02-15 18:54 ` Rafael J. Wysocki
2016-02-15 19:03 ` Marc Zyngier
2016-02-15 19:12 ` Rafael J. Wysocki
2016-02-15 19:28 ` Rafael J. Wysocki
2016-02-15 19:42 ` Tony Lindgren
2016-02-15 19:46 ` Guenter Roeck
2016-02-15 19:57 ` Tony Lindgren
2016-02-15 19:23 ` Russell King - ARM Linux
2016-02-15 20:41 ` Rafael J. Wysocki
2016-02-15 19:07 ` Russell King - ARM Linux
2016-02-15 19:01 ` Tony Lindgren
2016-02-15 19:40 ` Guenter Roeck
2016-02-15 19:58 ` Tony Lindgren
2016-02-15 20:09 ` Guenter Roeck
2016-02-15 20:38 ` Rafael J. Wysocki
2016-02-15 20:37 ` Rafael J. Wysocki
2016-02-15 21:36 ` Tony Lindgren
2016-02-16 1:38 ` Guenter Roeck [this message]
2016-02-15 19:02 ` Russell King - ARM Linux
2016-02-16 1:13 ` Viresh Kumar
2016-02-16 1:27 ` Rafael J. Wysocki
2016-02-16 1:36 ` Viresh Kumar
2016-02-15 22:29 ` Peter Maydell
2016-02-15 23:19 ` Guenter Roeck
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=56C27D7E.4060603@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=tony@atomide.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox