From: Neil Armstrong <narmstrong@baylibre.com>
To: Marc Zyngier <maz@kernel.org>,
Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: kernelci-results@groups.io,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
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:26:43 +0100 [thread overview]
Message-ID: <3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com> (raw)
In-Reply-To: <630e00e83cdd07ee5a0eaba9d3479554@kernel.org>
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 solution would be to revert and do some check in meson_dw_hdmi_init() to
check if already enabled and do nothing.
Neil
>
> Thanks,
>
> M.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-11-19 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fb5e094.1c69fb81.a2014.2e62@mx.google.com>
2020-11-19 8:50 ` Guillaume Tucker
2020-11-19 10:20 ` Marc Zyngier
2020-11-19 10:26 ` Neil Armstrong [this message]
2020-11-19 11:33 ` Marc Zyngier
2020-11-19 11:58 ` Marc Zyngier
2020-11-19 18:04 ` Guillaume Tucker
2020-11-19 18:13 ` Jerome Brunet
2020-11-19 18:35 ` Marc Zyngier
2020-11-20 9:26 ` Neil Armstrong
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=3f54de27-0fef-c5a1-8991-0a0614c90667@baylibre.com \
--to=narmstrong@baylibre.com \
--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=maz@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
all inboxes | Powered by JetHome®