From: Aaro Koskinen <aaro.koskinen@iki.fi>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: netdev@vger.kernel.org, linux-mips@vger.kernel.org
Subject: r8169: regression on MIPS/Loongson
Date: Fri, 23 Aug 2019 01:25:50 +0300 [thread overview]
Message-ID: <20190822222549.GF30291@darkstar.musicnaut.iki.fi> (raw)
Hi,
After upgrading from v5.2 to v5.3-rc5 on MIPS/Loongson board, copying
large files from network with scp started to fail with "Integrity error".
Bisected to:
f072218cca5b076dd99f3dfa3aaafedfd0023a51 is the first bad commit
commit f072218cca5b076dd99f3dfa3aaafedfd0023a51
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Thu Jun 27 23:19:09 2019 +0200
r8169: remove not needed call to dma_sync_single_for_device
Any idea what goes wrong? Should this change be reverted?
A.
next reply other threads:[~2019-08-22 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 22:25 Aaro Koskinen [this message]
2019-08-22 22:52 ` r8169: regression on MIPS/Loongson Heiner Kallweit
2019-08-22 23:00 ` David Miller
2019-08-22 23:38 ` Aaro Koskinen
2019-08-23 18:08 ` Heiner Kallweit
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=20190822222549.GF30291@darkstar.musicnaut.iki.fi \
--to=aaro.koskinen@iki.fi \
--cc=hkallweit1@gmail.com \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).