From: Guenter Roeck <linux@roeck-us.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-next@vger.kernel.org,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
linux-pm@vger.kernel.org
Subject: Re: Crashes in arm qemu emulations due to 'cpufreq: governor: Replace timers with utilization ...'
Date: Mon, 15 Feb 2016 15:19:57 -0800 [thread overview]
Message-ID: <56C25D1D.5080409@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA9Xy2L+edFAdUCpZFiO5NLGyrQPTQ6DgmuScbwEty-nzg@mail.gmail.com>
On 02/15/2016 02:29 PM, Peter Maydell wrote:
> On 15 February 2016 at 17:05, Guenter Roeck <linux@roeck-us.net> wrote:
>> I see crashes in various arm qemu tests due to 'cpufreq: governor: Replace
>> timers with utilization update callbacks' with next-20160215. An example
>> crash log and bisect results are attached below.
>>
>> Please let me know if there is anything I can do to help tracking down
>> the problem.
>>
>> Thanks,
>> Guenter
>>
>> ---
>>
>> Building arm:beagle:multi_v7_defconfig:omap3-beagle ... running ..... failed (crashed)
>> ------------
>> qemu log:
>
> You're using the QEMU beagle board emulation? Can I ask which
> QEMU you're using (qemu-linaro?). If the OMAP3 emulation is still
> actively useful to people I might have another stab at getting
> it into upstream QEMU some day...
>
Yes, I use qemu-linaro for those tests.
Is it useful ? Obviously for me, yes. It lets me test images in qemu,
and I don't need real hardware to run those tests. That means that
I don't depend on the hardware really working, and I am not hosed
if the hardware breaks down and I don't have a replacement. Plus,
of course, I don't need a lab with 90+ pieces of hardware.
Guenter
prev parent reply other threads:[~2016-02-15 23:20 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
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 [this message]
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=56C25D1D.5080409@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=peter.maydell@linaro.org \
--cc=rafael.j.wysocki@intel.com \
/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