From: Mark Brown <broonie@kernel.org>
To: khilman@baylibre.com, Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@vger.kernel.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 285 boots: 16 failed, 264 passed with 3 offline, 1 untried/unknown, 1 conflict (next-20190718)
Date: Thu, 18 Jul 2019 17:20:05 +0100 [thread overview]
Message-ID: <20190718162005.GF5761@sirena.org.uk> (raw)
In-Reply-To: <5d3057c8.1c69fb81.c6489.8ad2@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
On Thu, Jul 18, 2019 at 04:28:08AM -0700, kernelci.org bot wrote:
Today's -next started failing to boot defconfig on rk3399-firefly:
> arm64:
> defconfig:
> gcc-8:
> rk3399-firefly: 1 failed lab
It hits a BUG() trying to set up cpufreq:
[ 87.381606] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 200000 KHz
[ 87.393244] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 408000 KHz
[ 87.469777] cpufreq: cpufreq_online: CPU4: Running at unlisted freq: 12000 KHz
[ 87.488595] cpu cpu4: _generic_set_opp_clk_only: failed to set clock rate: -22
[ 87.491881] cpufreq: __target_index: Failed to change cpu frequency: -22
[ 87.495335] ------------[ cut here ]------------
[ 87.496821] kernel BUG at drivers/cpufreq/cpufreq.c:1438!
[ 87.498462] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
I'm struggling to see anything relevant in the diff from yesterday, the
unlisted frequency warnings were there in the logs yesterday but no oops
and I'm not seeing any changes in cpufreq, clk or anything relevant
looking.
Full bootlog and other info can be found here:
https://kernelci.org/boot/id/5d302d8359b51498d049e983/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2019-07-18 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d3057c8.1c69fb81.c6489.8ad2@mx.google.com>
2019-07-18 16:20 ` Mark Brown [this message]
2019-08-12 17:24 ` next/master boot: 285 boots: 16 failed, 264 passed with 3 offline, 1 untried/unknown, 1 conflict (next-20190718) Mark Brown
2019-08-13 17:26 ` Kevin Hilman
[not found] ` <7hmugdynmk.fsf@baylibre.com>
2019-08-14 9:01 ` CPUfreq fail on rk3399-firefly (was: next/master boot: 285 boots: 16 failed, 264 passed with 3 offline, 1 untried/unknown, 1 conflict (next-20190718)) Heiko Stuebner
2019-08-21 18:59 ` Kevin Hilman
[not found] ` <c973d3fa-5f0d-c277-7c83-6227942a671a@rock-chips.com>
2019-08-23 16:52 ` CPUfreq fail on rk3399-firefly Kevin Hilman
2019-08-23 17:03 ` Kevin Hilman
2019-08-26 9:56 ` Kever Yang
2019-08-26 17:09 ` Kevin Hilman
2019-08-27 1:54 ` Kever Yang
2019-08-27 2:14 ` Heiko Stuebner
2019-08-27 9:59 ` Kever Yang
2019-09-26 22:51 ` Kevin Hilman
2019-10-10 9:32 ` Kever Yang
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=20190718162005.GF5761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=kernel-build-reports@lists.linaro.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rockchip@vger.kernel.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).