From: Guenter Roeck <linux@roeck-us.net>
To: Nathan Rossi <nathan@nathanrossi.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [Qemu-devel] [PATCH v2] hw/misc/zynq_slcr: Change CPU clock rate for Linux boots
Date: Mon, 14 Sep 2015 07:05:17 -0700 [thread overview]
Message-ID: <55F6D41D.9090000@roeck-us.net> (raw)
In-Reply-To: <CA+aJhH3My015EZ8F6gQX9rX2AKxFUp=861-0ExR2fkiZ+k+FyA@mail.gmail.com>
On 09/14/2015 06:17 AM, Nathan Rossi wrote:
> On Mon, Sep 14, 2015 at 10:07 PM, Peter Maydell
> <peter.maydell@linaro.org> wrote:
>> On 13 September 2015 at 23:42, Peter Crosthwaite
>> <crosthwaitepeter@gmail.com> wrote:
>>> On Sun, Sep 13, 2015 at 1:47 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>>> On 13 September 2015 at 21:22, Peter Crosthwaite
>>>> <crosthwaitepeter@gmail.com> wrote:
>>>>> There may be more changes worth making on is_linux. I don't have the
>>>>> patch with the full list of FSBL-related SLCR changes handy and can't
>>>>> seem to find it in any modern Yocto trees. Wondering if Yocto still
>>>>> supports booting Zynq without FSBL (Nathan/Alistair may know more)?
>
> I have been running QEMU without any patches for zynq in Yocto for
> some time now. I have not experienced the bug mentioned, at least not
> with the kernels I have been testing with. Is this something that is
> more apparent in a 4.2 or newer kernel?
>
With mainline kernel v4.3-rc1 and qemu v2.4.0-417-g30c38c9, using multi_v7_defconfig,
I get
[ 0.478288] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 216666 KHz
[ 0.479378] cpu cpu0: failed to set clock rate: -16
[ 0.479515] cpufreq: __target_index: Failed to change cpu frequency: -16
[ 0.480107] ------------[ cut here ]------------
[ 0.480222] kernel BUG at drivers/cpufreq/cpufreq.c:1287!
with all the upstream devicetree files I am testing with. The crash happens all
the way back to 3.18, so it isn't new either.
Also, with kernel 3.18+, the same version of qemu, and the clock patch applied,
the kernel hangs because it expects the ADC to be supported by the hardware.
Effectively this suggests that you are using a different kernel configuration,
a different devicetree file, and/or an older kernel. I can not do this since the
required configuration and devicetree files change from kernel version to kernel
version, and I test a large range of kernel versions (currently 3.18, 4.1, 4.2,
and mainline, for this platform).
Thanks,
Guenter
next prev parent reply other threads:[~2015-09-14 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 21:06 [Qemu-devel] [PATCH v2] hw/misc/zynq_slcr: Change CPU clock rate for Linux boots Guenter Roeck
2015-09-13 20:22 ` Peter Crosthwaite
2015-09-13 20:37 ` Guenter Roeck
2015-09-13 20:47 ` Peter Maydell
2015-09-13 21:51 ` Guenter Roeck
2015-09-13 22:42 ` Peter Crosthwaite
2015-09-14 12:07 ` Peter Maydell
2015-09-14 13:17 ` Nathan Rossi
2015-09-14 14:05 ` Guenter Roeck [this message]
2015-09-27 5:44 ` Peter Crosthwaite
2015-09-27 5:50 ` Peter Crosthwaite
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=55F6D41D.9090000@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=nathan@nathanrossi.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).