From: Gal Pressman <gal@nvidia.com>
To: Matthew Schwartz <matthew.schwartz@linux.dev>,
Dragos Tatulea <dtatulea@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: regressions@lists.linux.dev, netdev@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] aquantia: Sunshine/Moonlight UDP video streaming broken since 5b4015ad833c ("net: aquantia: Remove redundant UDP length adjustment with GSO_PARTIAL")
Date: Mon, 27 Apr 2026 21:09:59 +0300 [thread overview]
Message-ID: <5293b717-6a8e-40b6-bd6b-61043a062451@nvidia.com> (raw)
In-Reply-To: <6c3fb15e-711d-4b8d-b152-e03d9b05293f@linux.dev>
Hello Matthew,
On 27/04/2026 2:20, Matthew Schwartz wrote:
> Hello,
>
> When using a previously working setup of remote streaming from my workstation to another device via Sunshine (the host server) and Moonlight (the client app) on my home network, I no longer receive any video output on the client app after upgrading my host workstation to kernel 7.0. Reverting back to kernel 6.19 on the host restored my setup to a working state.
>
> After bisecting, I landed on 5b4015ad833c ("net: aquantia: Remove redundant UDP length adjustment with GSO_PARTIAL") as the first bad commit. I confirmed this by moving the cable to my second on-board NIC (Intel) on the same workstation, which restored video output without any other kernel changes. My affected on-board NIC is Aquantia AQC113 [1d6a:04c0] (rev 03), atlantic driver, firmware 1.3.34, MTU 1500.
>
> Looking into it a bit further, ethtool -K enp97s0 tx-udp-segmentation off also serves as a workaround on my Aquantia port without changing to my other ethernet port. The working Intel NIC reports tx-udp-segmentation as "off [fixed]", so traffic falls back to software UDP segmentation on there.
>
> Please let me know if there's any additional info I can provide.
>
> Thanks,
> Matt
>
> #regzbot introduced: 5b4015ad833c
Thank you for the report and the bisect!
I will take a look and try to figure out what's wrong (though I don't
have real hardware to test on).
Is the userspace app open source? can I see its code and try to run it
myself?
I will be OOO for the rest of the week, hope to have some meaningful
reply by the end of next week.
next prev parent reply other threads:[~2026-04-27 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 23:20 [REGRESSION] aquantia: Sunshine/Moonlight UDP video streaming broken since 5b4015ad833c ("net: aquantia: Remove redundant UDP length adjustment with GSO_PARTIAL") Matthew Schwartz
2026-04-27 18:09 ` Gal Pressman [this message]
2026-04-27 18:26 ` Matthew Schwartz
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=5293b717-6a8e-40b6-bd6b-61043a062451@nvidia.com \
--to=gal@nvidia.com \
--cc=dtatulea@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.schwartz@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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