stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.14.y bisection: baseline.login on meson8b-odroidc1
Date: Mon, 10 Apr 2023 08:06:07 +0200	[thread overview]
Message-ID: <1fcff522-337a-c334-42a7-bc9b4f0daec4@collabora.com> (raw)

Culprit: https://lore.kernel.org/r/20211227180026.4068352-2-martin.blumenstingl@googlemail.com

On lun 27-12-2021 19:00:24, Martin Blumenstingl wrote:
> The dt-bindings for the UART controller only allow the following values
> for Meson6 SoCs:
> - "amlogic,meson6-uart", "amlogic,meson-ao-uart"
> - "amlogic,meson6-uart"
>
> Use the correct fallback compatible string "amlogic,meson-ao-uart" for
> AO UART. Drop the "amlogic,meson-uart" compatible string from the EE
> domain UART controllers.

KernelCI detected that this patch introduced a regression in
stable-rc/linux-4.14.y (4.14.267) on a meson8b-odroidc1.
After this patch was applied the tests running on this platform don't
show any serial output.

This doesn't happen in other stable branches nor in mainline, but 4.14
hasn't still reached EOL and it'd be good to find a fix.

Here's the bisection report:
https://groups.io/g/kernelci-results/message/40147

KernelCI info:
https://linux.kernelci.org/test/case/id/64234f7761021a30b262f776/

Test log:
https://storage.kernelci.org/stable-rc/linux-4.14.y/v4.14.311-43-g88e481d604e9/arm/multi_v7_defconfig/gcc-10/lab-baylibre/baseline-meson8b-odroidc1.html

Thanks,
Ricardo

             reply	other threads:[~2023-04-10  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  6:06 Ricardo Cañuelo [this message]
2023-05-04  9:06 ` stable-rc/linux-4.14.y bisection: baseline.login on meson8b-odroidc1 Linux regression tracking (Thorsten Leemhuis)
2023-05-04 10:22   ` Ricardo Cañuelo
2023-05-04 11:28     ` Thorsten Leemhuis
2023-06-19  9:36       ` Linux regression tracking (Thorsten Leemhuis)
2023-06-19 11:53         ` Ricardo Cañuelo
2023-06-19 17:09           ` Thorsten Leemhuis

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=1fcff522-337a-c334-42a7-bc9b4f0daec4@collabora.com \
    --to=ricardo.canuelo@collabora.com \
    --cc=stable@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).