From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
regressions@lists.linux.dev,
Max Krummenacher <max.krummenacher@toradex.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Regression, i.MX7 boot failure, Linux v6.1.77
Date: Tue, 13 Feb 2024 12:44:48 +0100 [thread overview]
Message-ID: <2024021300-traverse-anyplace-7910@gregkh> (raw)
In-Reply-To: <20240213112146.GA5874@francesco-nb>
On Tue, Feb 13, 2024 at 12:21:46PM +0100, Francesco Dolcini wrote:
> Hello Sasha,
> kernel v6.1.77 introduces a regression, with a boot failure, on i.MX7,
> with commit db30f469ae8b ("ARM: dts: imx7s: Fix nand-controller #size-cells").
>
> The issue is known [1][2], changing `#size-cells = <0>` is formally
> correct, but do not play well with the firmware that are deployed on
> those embedded devices, leading to a boot failure.
>
> A mitigation was implemented in the Linux kernel,
> commit 84549c816dc3 ("mtd: parsers: ofpart: add workaround for #size-cells 0")
> that was merged into v6.3, the firmware was also fixed, however existing
> device using old firmware will not boot anymore if updating to a newer
> kernel.
>
> I would ask you to drop such a patch from any stable patches queue and
> not backport it to any older kernel.
>
> To fix v6.1.y I see two options:
> - backport 84549c816dc3
> - revert db30f469ae8b
>
> What do you prefer? Should I send myself a patch?
Backport would be best, that way we are in sync with newer releases.
I'll go queue it up now, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
regressions@lists.linux.dev,
Max Krummenacher <max.krummenacher@toradex.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Regression, i.MX7 boot failure, Linux v6.1.77
Date: Tue, 13 Feb 2024 12:44:48 +0100 [thread overview]
Message-ID: <2024021300-traverse-anyplace-7910@gregkh> (raw)
In-Reply-To: <20240213112146.GA5874@francesco-nb>
On Tue, Feb 13, 2024 at 12:21:46PM +0100, Francesco Dolcini wrote:
> Hello Sasha,
> kernel v6.1.77 introduces a regression, with a boot failure, on i.MX7,
> with commit db30f469ae8b ("ARM: dts: imx7s: Fix nand-controller #size-cells").
>
> The issue is known [1][2], changing `#size-cells = <0>` is formally
> correct, but do not play well with the firmware that are deployed on
> those embedded devices, leading to a boot failure.
>
> A mitigation was implemented in the Linux kernel,
> commit 84549c816dc3 ("mtd: parsers: ofpart: add workaround for #size-cells 0")
> that was merged into v6.3, the firmware was also fixed, however existing
> device using old firmware will not boot anymore if updating to a newer
> kernel.
>
> I would ask you to drop such a patch from any stable patches queue and
> not backport it to any older kernel.
>
> To fix v6.1.y I see two options:
> - backport 84549c816dc3
> - revert db30f469ae8b
>
> What do you prefer? Should I send myself a patch?
Backport would be best, that way we are in sync with newer releases.
I'll go queue it up now, thanks.
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-13 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:21 Regression, i.MX7 boot failure, Linux v6.1.77 Francesco Dolcini
2024-02-13 11:21 ` Francesco Dolcini
2024-02-13 11:44 ` Greg Kroah-Hartman [this message]
2024-02-13 11:44 ` Greg Kroah-Hartman
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=2024021300-traverse-anyplace-7910@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=francesco@dolcini.it \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.krummenacher@toradex.com \
--cc=miquel.raynal@bootlin.com \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=shawnguo@kernel.org \
--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 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.