From: Greg KH <gregkh@linuxfoundation.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: stable@vger.kernel.org,
Brian Silverman <brian.silverman@bluerivertech.com>
Subject: Re: [PATCH] can: m_can: Disable and ignore ELO interrupt
Date: Sun, 12 Dec 2021 14:19:12 +0100 [thread overview]
Message-ID: <YbX20AXH1F0qb4uO@kroah.com> (raw)
In-Reply-To: <20211211213011.813419-1-mkl@pengutronix.de>
On Sat, Dec 11, 2021 at 10:30:11PM +0100, Marc Kleine-Budde wrote:
> From: Brian Silverman <brian.silverman@bluerivertech.com>
>
> Commit f58ac1adc76b5beda43c64ef359056077df4d93a upstream.
>
> With the design of this driver, this condition is often triggered.
> However, the counter that this interrupt indicates an overflow is never
> read either, so overflowing is harmless.
>
> On my system, when a CAN bus starts flapping up and down, this locks up
> the whole system with lots of interrupts and printks.
>
> Specifically, this interrupt indicates the CEL field of ECR has
> overflowed. All reads of ECR mask out CEL.
>
> Fixes: e0d1f4816f2a ("can: m_can: add Bosch M_CAN controller support")
> Link: https://lore.kernel.org/all/20211129222628.7490-1-brian.silverman@bluerivertech.com
> Cc: stable@vger.kernel.org
> Signed-off-by: Brian Silverman <brian.silverman@bluerivertech.com>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
> Hey Greg,
>
> this is
> | f58ac1adc76b ("can: m_can: Disable and ignore ELO interrupt")
> checrry picked onto v5.10. The patch applied without any problems,
> won't know why it didn't work in your side.
This worked, thanks.
Can I get a working backport for 4.4.y and 4.9.y as well?
thanks,
greg k-h
prev parent reply other threads:[~2021-12-12 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 21:30 [PATCH] can: m_can: Disable and ignore ELO interrupt Marc Kleine-Budde
2021-12-12 13:19 ` Greg KH [this message]
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=YbX20AXH1F0qb4uO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brian.silverman@bluerivertech.com \
--cc=mkl@pengutronix.de \
--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