From: Jakub Kicinski <kuba@kernel.org>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [regression] dpaa2: TSO offload on lx2160a causes fatal exception in interrupt
Date: Wed, 18 May 2022 22:12:26 -0700 [thread overview]
Message-ID: <20220518221226.3712626c@kernel.org> (raw)
In-Reply-To: <20220512094323.3a89915f@kernel.org>
On Thu, 12 May 2022 09:43:23 -0700 Jakub Kicinski wrote:
> On Wed, 4 May 2022 08:06:47 +0000 Ioana Ciornei wrote:
> > > > Mitigation:
> > > > ethtool -K ethX tso off
> > > >
> > > > [reply] [−] Comment 1 kernelbugs@63bit.net 2022-05-02 01:37:06 UTC
> > > >
> > > > I believe this is related to commit 3dc709e0cd47c602a8d1a6747f1a91e9737eeed3
> > > >
> > >
> > > That commit is "dpaa2-eth: add support for software TSO".
> > >
> > > Could somebody take a look into this? Or was this discussed somewhere
> > > else already? Or even fixed?
> >
> > I will take a look at it, it wasn't discussed already.
>
> Hi! Any progress on this one? AFAICT this is a new bug in 5.18, would
> be great if we can close it in the next week or so, otherwise perhaps
> consider disabling TSO by default. maybe?
ping?
next prev parent reply other threads:[~2022-05-19 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:46 [regression] dpaa2: TSO offload on lx2160a causes fatal exception in interrupt Thorsten Leemhuis
2022-05-04 8:06 ` Ioana Ciornei
2022-05-12 16:43 ` Jakub Kicinski
2022-05-19 5:12 ` Jakub Kicinski [this message]
2022-05-19 6:07 ` Thorsten Leemhuis
2022-05-19 16:03 ` Jakub Kicinski
2022-05-19 16:23 ` Ioana Ciornei
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=20220518221226.3712626c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=ioana.ciornei@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@leemhuis.info \
/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).