While booting stable-rc 4.14 branch kernel this warning was noticed on
Qualcomm APQ 8016 SBC (DT) Dragonboard 410c device.
[8.459580] clk: failed to reparent byte0_clk_src to dsi0pllbyte: -22
[8.459724] clk: failed to reparent pclk0_clk_src to dsi0pll: -22
[8.466474] msm
On Sun, 12 Apr 2020 at 15:08, Naresh Kamboju wrote:
>
> While booting stable-rc 4.14 branch kernel this warning was noticed on
> Qualcomm APQ 8016 SBC (DT) Dragonboard 410c device.
>
> [8.459580] clk: failed to reparent byte0_clk_src to dsi0pllbyte: -22
> [8.4
We still notice kernel warnings while booting stable rc 4.14.177-rc1 kernel
on qualcomm dragonboard 410c development board.
[7.760140] msm_dsi_host_set_src_pll: can't set parent to
byte_clk_src. ret=-22
[7.763963] msm_dsi_manager_register: failed to register mipi dsi
host for DSI 0
[
On Tue, 15 Sep 2020 at 19:50, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.66 release.
> There are 132 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Mon, 20 Jul 2020 at 21:27, Rob Clark wrote:
>
> On Mon, Jul 20, 2020 at 4:28 AM Robin Murphy wrote:
> >
> > On 2020-07-20 08:17, Arnd Bergmann wrote:
> > > On Mon, Jul 20, 2020 at 8:36 AM Naresh Kamboju
> > > wrote:
<>
> > >> [5.44
On Wed, 12 Aug 2020 at 23:14, Stephen Boyd wrote:
>
> Quoting Stephen Boyd (2020-07-23 03:26:02)
> > Quoting Naresh Kamboju (2020-07-23 03:10:37)
> > > On Thu, 23 Jul 2020 at 13:36, Stephen Boyd wrote:
> > > >
> > > > It sounds like maybe you need t
On Thu, 23 Jul 2020 at 13:36, Stephen Boyd wrote:
>
> Quoting Arnd Bergmann (2020-07-21 02:51:32)
> > __clk_set_parent_before(orphan, parent);
> >
> > None of the above have changed in stable kernels.
> >
> > > [5.633668] pll_28nm_register+0xa4/0x340 [msm]
> > > [
Kernel Internal oops while booting stable-rc 4.14 kernel on qcom db410c device
this problem happened only once on this specific platform.
and rcu_preempt detected stalls on CPUs/tasks detected after this and
board hung.
metadata:
git branch: linux-4.14.y
git repo:
Hi Rob,
On Sun, 20 Feb 2022 at 00:02, Rob Clark wrote:
>
> From: Rob Clark
>
> Avoid going down devfreq paths on devices where devfreq is not
> initialized.
>
> Reported-by: Linux Kernel Functional Testing
> Reported-by: Anders Roxell
> Signed-off-by: Rob Clark
I have tested this patch and
Hi Rob and Linus,
On Mon, 7 Mar 2022 at 14:07, Naresh Kamboju wrote:
>
> Hi Rob,
>
> On Sun, 20 Feb 2022 at 00:02, Rob Clark wrote:
> >
> > From: Rob Clark
> >
> > Avoid going down devfreq paths on devices where devfreq is not
> > initialized.
&g
[Please ignore this email if it is already reported]
Linux next-20220302 running on Qcom db410c the following kernel crash
reported [1].
metadata:
git_ref: master
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: adaedcf826dccf01b69d9a1f1997c9446c6b2c54
11 matches
Mail list logo
