From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: kernelci-results@groups.io, bot@kernelci.org,
gtucker@collabora.com, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-serial@vger.kernel.org
Subject: Re: next/pending-fixes bisection: baseline.login on mt8173-elm-hana
Date: Tue, 10 May 2022 10:01:17 +0200 [thread overview]
Message-ID: <9a2b8b38-c4c0-b1a3-832b-74a937d66047@collabora.com> (raw)
In-Reply-To: <YnlaZgJfGASYwO8Y@sirena.org.uk>
Il 09/05/22 20:16, Mark Brown ha scritto:
> On Mon, May 09, 2022 at 05:27:51PM +0100, Mark Brown wrote:
>> On Mon, May 09, 2022 at 09:12:51AM -0700, KernelCI bot wrote:
>>
>> The KernelCI bisection bot found a boot regression on mt8173-elm-hana
>> which bisected to 6f81fdded0d02 ("serial: 8250_mtk: Make sure to select
>> the right FEATURE_SEL"). With the patch the output terminates at:
>
> There was also a similar report on mt8183-kukui-jacuzzi-juniper-sku16.
Strange, we tested it on another Kukui device and it didn't produce any issue...
Doubt is if it's just about the FEATURE_SEL register, as that may be protected
and/or not exist on 8173?
I'm investigating that today.
Cheers,
Angelo
next prev parent reply other threads:[~2022-05-10 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62793d83.1c69fb81.71b96.033e@mx.google.com>
2022-05-09 16:27 ` next/pending-fixes bisection: baseline.login on mt8173-elm-hana Mark Brown
2022-05-09 18:16 ` Mark Brown
2022-05-10 8:01 ` AngeloGioacchino Del Regno [this message]
2022-05-10 8:06 ` Chen-Yu Tsai
2022-06-01 15:07 ` [BUG] mtk serial broken on mt7622 with 5.18.0 Frank Wunderlich
2022-06-01 15:37 ` Ilpo Järvinen
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=9a2b8b38-c4c0-b1a3-832b-74a937d66047@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gtucker@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.bgg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox