From: Ferry Toth <fntoth@gmail.com>
To: Iryna Semenovych <iryna.semenovych@chargex.de>, netdev@vger.kernel.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com,
Steve Glendinning <steve.glendinning@shawell.net>,
UNGLinuxDriver@microchip.com,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
stable@kernel.org
Subject: Re: smsc95xx driver
Date: Tue, 16 Aug 2022 16:22:27 +0200 [thread overview]
Message-ID: <98c22ea0-ce1d-ab7e-5d87-da85660ab8ec@gmail.com> (raw)
In-Reply-To: <CAJU7JFAscYncnRLSNGrs4n22EzkxZBTWW6hQuk2WRGcUPwoXNw@mail.gmail.com>
Hi,
On 16-08-2022 11:44, Iryna Semenovych wrote:
> Hi folks!
>
> Recently I found the discussion in the archive about smsc95xx driver
> patch that introduces some other issues:
> https://lore.kernel.org/netdev/93d3bb50040dd4519a65187d3412973831d2d797.camel@collabora.com/
>
> I am struggling with the similar/the same issue that is described in
> detail here:
> https://github.com/raspberrypi/linux/issues/5116
>
I believe that a number patches have just been backported for usbnet:
smsc95xx for 5.15 and 5.18 that might resolve your issue.
I did find another crash:
DMA-API: xhci-hcd xhci-hcd.1.auto: cacheline tracking EEXIST, > > >
overlapping mappings aren't supported But it appears happens in the hub
code as other hubs then smsc95xx also have that error. This one has not
yet been resolved.
> Does anybody know if this issue is even related to smsc95xx driver
> changes or how it can be fixed?
> I would really appreciate any help.
>
> Thanks in advance!
>
> --
> *Best regards, *
> *Iryna Semenovych*
> Software Engineer
>
> T: +49 157 31090173
> M: iryna.semenovych@chargex.de
> W: www.chargex.de <http://www.chargex.de>
>
> ChargeX GmbH
> Landsberger Str. 318a, 80687 München
parent reply other threads:[~2022-08-16 14:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAJU7JFAscYncnRLSNGrs4n22EzkxZBTWW6hQuk2WRGcUPwoXNw@mail.gmail.com>]
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=98c22ea0-ce1d-ab7e-5d87-da85660ab8ec@gmail.com \
--to=fntoth@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=iryna.semenovych@chargex.de \
--cc=kernel@collabora.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
--cc=steve.glendinning@shawell.net \
/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