From: Viresh Kumar <viresh.kumar@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Stephan Gerhold <stephan@gerhold.net>,
Rajendra Nayak <rnayak@codeaurora.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
sbhanu@codeaurora.org, Sibi Sankar <sibis@codeaurora.org>,
Matthias Kaehlcke <mka@chromium.org>,
Stephen Boyd <sboyd@kernel.org>,
nm@ti.com
Subject: Re: WARNING: at drivers/opp/core.c:678 dev_pm_opp_set_rate+0x4cc/0x5d4 - on arm x15
Date: Thu, 27 Aug 2020 15:16:51 +0530 [thread overview]
Message-ID: <20200827094651.3grvs6ungv3dh7y3@vireshk-i7> (raw)
In-Reply-To: <CA+G9fYvK5UkERLuBSRH5t2=j5==dbtw45GTMta9MafyJDqFsFA@mail.gmail.com>
On 27-08-20, 15:04, Naresh Kamboju wrote:
> While boot testing arm x15 devices the Kernel warning noticed with linux next
> tag 20200825.
>
> BAD: next-20200825
> GOOD: next-20200824
>
> metadata:
> git branch: master
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git commit: 3a00d3dfd4b68b208ecd5405e676d06c8ad6bb63
> git describe: next-20200825
> make_kernelversion: 5.9.0-rc2
> kernel-config:
> https://builds.tuxbuild.com/LDTu4GFMmvkJspza5LJIjQ/kernel.config
>
> We are working on git bisect and boot testing on x15 and get back to you.
Was this working earlier ? But considering that multiple things
related to OPP broke recently, it may be a OPP core bug as well. Not
sure though.
Can you give me delta between both the next branches for drivers/opp/
path ? I didn't get these tags after fetching linux-next.
--
viresh
next prev parent reply other threads:[~2020-08-27 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:34 WARNING: at drivers/opp/core.c:678 dev_pm_opp_set_rate+0x4cc/0x5d4 - on arm x15 Naresh Kamboju
2020-08-27 9:46 ` Viresh Kumar [this message]
2020-08-27 11:01 ` Naresh Kamboju
2020-08-27 11:18 ` Stephen Rothwell
2020-08-28 4:51 ` Viresh Kumar
2020-08-28 10:12 ` Naresh Kamboju
2020-08-31 4:41 ` Viresh Kumar
2020-08-31 6:00 ` Naresh Kamboju
2020-08-31 6:02 ` Viresh Kumar
2020-10-15 9:56 ` Naresh Kamboju
2020-10-16 5:45 ` Viresh Kumar
2020-10-20 10:36 ` Viresh Kumar
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=20200827094651.3grvs6ungv3dh7y3@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mka@chromium.org \
--cc=naresh.kamboju@linaro.org \
--cc=nm@ti.com \
--cc=rnayak@codeaurora.org \
--cc=sbhanu@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=sibis@codeaurora.org \
--cc=stephan@gerhold.net \
--cc=ulf.hansson@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;
as well as URLs for NNTP newsgroup(s).