From: Marc Zyngier <maz@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: kernelci-results@groups.io,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: next/master bisection: baseline.dmesg.emerg on meson-gxbb-p200
Date: Thu, 19 Nov 2020 11:33:06 +0000 [thread overview]
Message-ID: <48731911dbbe869a6d3bdafd819fa9ff@kernel.org> (raw)
In-Reply-To: <3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com>
On 2020-11-19 10:26, Neil Armstrong wrote:
> On 19/11/2020 11:20, Marc Zyngier wrote:
>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>> Please see the automated bisection report below about some kernel
>>> errors on meson-gxbb-p200.
>>>
>>> Reports aren't automatically sent to the public while we're
>>> trialing new bisection features on kernelci.org, however this one
>>> looks valid.
>>>
>>> The bisection started with next-20201118 but the errors are still
>>> present in next-20201119. Details for this regression:
>>>
>>> https://kernelci.org/test/case/id/5fb6196bfd0127fd68d8d902/
>>>
>>> The first error is:
>>>
>>> [ 14.757489] Internal error: synchronous external abort: 96000210
>>> [#1] PREEMPT SMP
>>
>> Looks like yet another clock ordering setup. I guess different Amlogic
>> platforms have slightly different ordering requirements.
>>
>> Neil, do you have any idea of which platform requires which ordering?
>> The variability in DT and platforms is pretty difficult to follow (and
>> I don't think I have such board around).
>
> The requirements should be the same, here the init was done before
> calling
> dw_hdmi_probe to be sure the clocks and internals resets were
> deasserted.
> But since you boot from u-boot already enabling these, it's already
> active.
The crashing platform also boots with u-boot. What is the difference?
No HDMI support?
> The solution would be to revert and do some check in
> meson_dw_hdmi_init() to
> check if already enabled and do nothing.
It looks more subtle than that, as it also depends on which DT is
provided
(an early meson_dw_hdmi_init() works with the kernel DT, and breaks with
the
u-boot DT). So whatever difference is between the two DTs causes havoc.
u-boot obviously only uses its own DT, so we are looking at a kernel bug
here.
Not having this patch also breaks module reinsertion (HDMI clocks are
disabled
on unbind), so *something* has to be done late.
So here are my questions:
- What breaks in my config when I boot using u-boot's DT?
- How to detect early that the registers are clocked or not?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: kernelci-results@groups.io,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: next/master bisection: baseline.dmesg.emerg on meson-gxbb-p200
Date: Thu, 19 Nov 2020 11:33:06 +0000 [thread overview]
Message-ID: <48731911dbbe869a6d3bdafd819fa9ff@kernel.org> (raw)
In-Reply-To: <3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com>
On 2020-11-19 10:26, Neil Armstrong wrote:
> On 19/11/2020 11:20, Marc Zyngier wrote:
>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>> Please see the automated bisection report below about some kernel
>>> errors on meson-gxbb-p200.
>>>
>>> Reports aren't automatically sent to the public while we're
>>> trialing new bisection features on kernelci.org, however this one
>>> looks valid.
>>>
>>> The bisection started with next-20201118 but the errors are still
>>> present in next-20201119. Details for this regression:
>>>
>>> https://kernelci.org/test/case/id/5fb6196bfd0127fd68d8d902/
>>>
>>> The first error is:
>>>
>>> [ 14.757489] Internal error: synchronous external abort: 96000210
>>> [#1] PREEMPT SMP
>>
>> Looks like yet another clock ordering setup. I guess different Amlogic
>> platforms have slightly different ordering requirements.
>>
>> Neil, do you have any idea of which platform requires which ordering?
>> The variability in DT and platforms is pretty difficult to follow (and
>> I don't think I have such board around).
>
> The requirements should be the same, here the init was done before
> calling
> dw_hdmi_probe to be sure the clocks and internals resets were
> deasserted.
> But since you boot from u-boot already enabling these, it's already
> active.
The crashing platform also boots with u-boot. What is the difference?
No HDMI support?
> The solution would be to revert and do some check in
> meson_dw_hdmi_init() to
> check if already enabled and do nothing.
It looks more subtle than that, as it also depends on which DT is
provided
(an early meson_dw_hdmi_init() works with the kernel DT, and breaks with
the
u-boot DT). So whatever difference is between the two DTs causes havoc.
u-boot obviously only uses its own DT, so we are looking at a kernel bug
here.
Not having this patch also breaks module reinsertion (HDMI clocks are
disabled
on unbind), so *something* has to be done late.
So here are my questions:
- What breaks in my config when I boot using u-boot's DT?
- How to detect early that the registers are clocked or not?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: kernelci-results@groups.io,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>,
Kevin Hilman <khilman@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: next/master bisection: baseline.dmesg.emerg on meson-gxbb-p200
Date: Thu, 19 Nov 2020 11:33:06 +0000 [thread overview]
Message-ID: <48731911dbbe869a6d3bdafd819fa9ff@kernel.org> (raw)
In-Reply-To: <3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com>
On 2020-11-19 10:26, Neil Armstrong wrote:
> On 19/11/2020 11:20, Marc Zyngier wrote:
>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>> Please see the automated bisection report below about some kernel
>>> errors on meson-gxbb-p200.
>>>
>>> Reports aren't automatically sent to the public while we're
>>> trialing new bisection features on kernelci.org, however this one
>>> looks valid.
>>>
>>> The bisection started with next-20201118 but the errors are still
>>> present in next-20201119. Details for this regression:
>>>
>>> https://kernelci.org/test/case/id/5fb6196bfd0127fd68d8d902/
>>>
>>> The first error is:
>>>
>>> [ 14.757489] Internal error: synchronous external abort: 96000210
>>> [#1] PREEMPT SMP
>>
>> Looks like yet another clock ordering setup. I guess different Amlogic
>> platforms have slightly different ordering requirements.
>>
>> Neil, do you have any idea of which platform requires which ordering?
>> The variability in DT and platforms is pretty difficult to follow (and
>> I don't think I have such board around).
>
> The requirements should be the same, here the init was done before
> calling
> dw_hdmi_probe to be sure the clocks and internals resets were
> deasserted.
> But since you boot from u-boot already enabling these, it's already
> active.
The crashing platform also boots with u-boot. What is the difference?
No HDMI support?
> The solution would be to revert and do some check in
> meson_dw_hdmi_init() to
> check if already enabled and do nothing.
It looks more subtle than that, as it also depends on which DT is
provided
(an early meson_dw_hdmi_init() works with the kernel DT, and breaks with
the
u-boot DT). So whatever difference is between the two DTs causes havoc.
u-boot obviously only uses its own DT, so we are looking at a kernel bug
here.
Not having this patch also breaks module reinsertion (HDMI clocks are
disabled
on unbind), so *something* has to be done late.
So here are my questions:
- What breaks in my config when I boot using u-boot's DT?
- How to detect early that the registers are clocked or not?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
kernelci-results@groups.io, Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: next/master bisection: baseline.dmesg.emerg on meson-gxbb-p200
Date: Thu, 19 Nov 2020 11:33:06 +0000 [thread overview]
Message-ID: <48731911dbbe869a6d3bdafd819fa9ff@kernel.org> (raw)
In-Reply-To: <3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com>
On 2020-11-19 10:26, Neil Armstrong wrote:
> On 19/11/2020 11:20, Marc Zyngier wrote:
>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>> Please see the automated bisection report below about some kernel
>>> errors on meson-gxbb-p200.
>>>
>>> Reports aren't automatically sent to the public while we're
>>> trialing new bisection features on kernelci.org, however this one
>>> looks valid.
>>>
>>> The bisection started with next-20201118 but the errors are still
>>> present in next-20201119. Details for this regression:
>>>
>>> https://kernelci.org/test/case/id/5fb6196bfd0127fd68d8d902/
>>>
>>> The first error is:
>>>
>>> [ 14.757489] Internal error: synchronous external abort: 96000210
>>> [#1] PREEMPT SMP
>>
>> Looks like yet another clock ordering setup. I guess different Amlogic
>> platforms have slightly different ordering requirements.
>>
>> Neil, do you have any idea of which platform requires which ordering?
>> The variability in DT and platforms is pretty difficult to follow (and
>> I don't think I have such board around).
>
> The requirements should be the same, here the init was done before
> calling
> dw_hdmi_probe to be sure the clocks and internals resets were
> deasserted.
> But since you boot from u-boot already enabling these, it's already
> active.
The crashing platform also boots with u-boot. What is the difference?
No HDMI support?
> The solution would be to revert and do some check in
> meson_dw_hdmi_init() to
> check if already enabled and do nothing.
It looks more subtle than that, as it also depends on which DT is
provided
(an early meson_dw_hdmi_init() works with the kernel DT, and breaks with
the
u-boot DT). So whatever difference is between the two DTs causes havoc.
u-boot obviously only uses its own DT, so we are looking at a kernel bug
here.
Not having this patch also breaks module reinsertion (HDMI clocks are
disabled
on unbind), so *something* has to be done late.
So here are my questions:
- What breaks in my config when I boot using u-boot's DT?
- How to detect early that the registers are clocked or not?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-11-19 11:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fb5e094.1c69fb81.a2014.2e62@mx.google.com>
2020-11-19 8:50 ` next/master bisection: baseline.dmesg.emerg on meson-gxbb-p200 Guillaume Tucker
2020-11-19 8:50 ` Guillaume Tucker
2020-11-19 8:50 ` Guillaume Tucker
2020-11-19 8:50 ` Guillaume Tucker
2020-11-19 10:20 ` Marc Zyngier
2020-11-19 10:20 ` Marc Zyngier
2020-11-19 10:20 ` Marc Zyngier
2020-11-19 10:20 ` Marc Zyngier
2020-11-19 10:26 ` Neil Armstrong
2020-11-19 10:26 ` Neil Armstrong
2020-11-19 10:26 ` Neil Armstrong
2020-11-19 10:26 ` Neil Armstrong
2020-11-19 11:33 ` Marc Zyngier [this message]
2020-11-19 11:33 ` Marc Zyngier
2020-11-19 11:33 ` Marc Zyngier
2020-11-19 11:33 ` Marc Zyngier
2020-11-19 11:58 ` Marc Zyngier
2020-11-19 11:58 ` Marc Zyngier
2020-11-19 11:58 ` Marc Zyngier
2020-11-19 11:58 ` Marc Zyngier
2020-11-19 18:04 ` Guillaume Tucker
2020-11-19 18:04 ` Guillaume Tucker
2020-11-19 18:04 ` Guillaume Tucker
2020-11-19 18:04 ` Guillaume Tucker
2020-11-19 18:13 ` Jerome Brunet
2020-11-19 18:13 ` Jerome Brunet
2020-11-19 18:13 ` Jerome Brunet
2020-11-19 18:13 ` Jerome Brunet
2020-11-19 18:35 ` Marc Zyngier
2020-11-19 18:35 ` Marc Zyngier
2020-11-19 18:35 ` Marc Zyngier
2020-11-19 18:35 ` Marc Zyngier
2020-11-20 9:26 ` Neil Armstrong
2020-11-20 9:26 ` Neil Armstrong
2020-11-20 9:26 ` Neil Armstrong
2020-11-20 9:26 ` Neil Armstrong
2020-11-20 9:59 ` Marc Zyngier
2020-11-20 9:59 ` Marc Zyngier
2020-11-20 9:59 ` Marc Zyngier
2020-11-20 9:59 ` Marc Zyngier
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=48731911dbbe869a6d3bdafd819fa9ff@kernel.org \
--to=maz@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=guillaume.tucker@collabora.com \
--cc=jbrunet@baylibre.com \
--cc=kernelci-results@groups.io \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.