From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
RENARD Pierre-Francois <pfrenard@gmail.com>,
nsaenzjulienne@suse.de, woojung.huh@microchip.com,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [RPI 3B+ / TSO / lan78xx ]
Date: Tue, 7 Jan 2020 10:06:07 -0800 [thread overview]
Message-ID: <6a8ec9cb-b56d-a788-1460-e9f0d9dd8f5f@gmail.com> (raw)
In-Reply-To: <f7e1f498-d90b-1685-dc02-4c24273957a7@i2se.com>
On 1/7/20 9:30 AM, Stefan Wahren wrote:
> Hi Eric,
>
> Am 07.01.20 um 18:04 schrieb Eric Dumazet:
>>
>>
>> I doubt TSO and SACK have a serious generic bug like that.
>>
>> Most likely the TSO implementation on the driver/NIC has a bug .
>
> Yes, the issue isn't reproducible with the Raspberry Pi 3B and the same
> kernel (without +). The main difference between both boards is the
> different ethernet USB chip:
>
> Raspberry Pi 3B: smsc95xx
> Raspberry Pi 3B+: lan78xx
>
>>
>> Anyway you do not provide a kernel version, I am not sure what you expect from us.
>
> It's Linux 5.4.7 (arm64) as in the provided github link. I asked
> Pierre-Francois to report this issue here, so the issue get addressed
> properly. Currently this very old bug not fixed in mainline and the
> Raspberry Pi vendor tree uses a workaround (disable TSO).
This is puzzling.
Bug seems trivial enough :/
prev parent reply other threads:[~2020-01-07 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5267da21-8f12-2750-c0c5-4ed31b03833b@gmail.com>
2020-01-07 13:32 ` [RPI 3B+ / TSO / lan78xx ] RENARD Pierre-Francois
2020-01-07 17:04 ` Eric Dumazet
2020-01-07 17:21 ` Eric Dumazet
2020-01-07 17:30 ` Stefan Wahren
2020-01-07 18:06 ` Eric Dumazet [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=6a8ec9cb-b56d-a788-1460-e9f0d9dd8f5f@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=pfrenard@gmail.com \
--cc=stefan.wahren@i2se.com \
--cc=woojung.huh@microchip.com \
/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