From: Michal Pecio <michal.pecio@gmail.com>
To: Dane Linssen <linssendane@gmail.com>
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: r8152: RX stops until rebind after -EPROTO on the bulk-in endpoint
Date: Fri, 2 Oct 2026 10:43:55 +0200 [thread overview]
Message-ID: <20261002104355.698eaf00.michal.pecio@gmail.com> (raw)
In-Reply-To: <CAM6_QD-CbYSsmic5LhpMi-aMXuC_VaniELBzaBeWO8SWm4UONA@mail.gmail.com>
On Mon, 28 Sep 2026 14:48:05 +0200, Dane Linssen wrote:
> Andrew:
> As far as I can tell it isn't a regression. The adapter is new
> (2026-09-17) and has only run 7.2.5 and 7.2.6, which don't differ in
> r8152 or xhci. e765ab012f73 ("usb: xhci: Improve Soft Retries after
> short transfers", v7.1) should make it rarer, not more common.
IDK if it's a regression or not, but the symptoms seem consistent
with a know problem which exists since forever.
> Michal:
> > Out of curiosity, what's your xHCI chip?
>
> Intel Sunrise Point-LP, 8086:9d2f (i5-8250U), so not ASMedia. The
> other host with the same adapter, which hasn't stalled, has an Intel
> Comet Lake-LP, 8086:02ed.
OK, thanks.
> > As a bandaid, you could try increasing MAX_SOFT_RETRY or this:
> > https://lore.kernel.org/linux-usb/20260905101837.4b7849c5.michal.pecio@gmail.com/
>
> Thank you. Would you like me to try this to gather more data? If not,
> I already have a userspace watchdog that rebinds r8152 when the LAN is
> unreachable and the bulk-in endpoint shows virt_state 0x40.
You could try it. We may consider increasing retries in mainline if
this turns out to solve real world problems. Though so far, in the only
reported case of 3 retries not working, 10 retries over a span of 100ms
weren't helping either...
> I only enabled it after the two stalls I reported. In the 19 hours
> since, including 71 minutes above 5k rx packets/s (peak about 29k),
> there hasn't been a single "Transfer error" message, and no stall. So
> nothing random so far. The next stall will show whether it's a burst.
Any results yet?
Regards,
Michal
next prev parent reply other threads:[~2026-10-02 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM6_QD_PoTdwdM7DvzzgHRs-G5EvQu-c5oNGve=GuKV4wFYAvQ@mail.gmail.com>
2026-09-27 22:01 ` Dane Linssen
2026-09-28 10:03 ` Michal Pecio
2026-09-28 12:48 ` Dane Linssen
2026-10-02 8:43 ` Michal Pecio [this message]
2026-09-28 1:33 ` Andrew Lunn
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=20261002104355.698eaf00.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linssendane@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®