From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: "Huang, Xiong" <xiong@qca.qualcomm.com>
Cc: Sven Hartge <sven@svenhartge.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Atheros Communications Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) 1.0.0.7 md5/sha1 corrupted using NFS and samba (updated) Version 2
Date: Thu, 28 Mar 2013 04:29:34 +0100 [thread overview]
Message-ID: <20130328032934.GD2176@order.stressinduktion.org> (raw)
In-Reply-To: <157393863283F442885425D2C45428564F201026@nasanexd02f.na.qualcomm.com>
On Thu, Mar 28, 2013 at 03:25:29AM +0000, Huang, Xiong wrote:
> Please don't revise following code:
>
> rx_page->read_offset +=
> (((u32)((prrs->word1 >> RRS_PKT_SIZE_SHIFT) &
> RRS_PKT_SIZE_MASK) +
> sizeof(struct atl1e_recv_ret_status) + 31) &
> 0xFFFFFFE0);
>
> Here 32bytes alignment is no matter with Page alignment.
If I revert this change I get sequence errors:
[ 781.449864] ATL1E 0000:04:00.0: irq 45 for MSI/MSI-X
[ 781.454634] IPv6: ADDRCONF(NETDEV_UP): p33p1: link is not ready
[ 782.893744] ATL1E 0000:04:00.0 p33p1: NIC Link is Up <100 Mbps Full Duplex>
[ 782.893797] IPv6: ADDRCONF(NETDEV_CHANGE): p33p1: link becomes ready
[ 783.194443] ATL1E 0000:04:00.0 p33p1: rx sequence number error (rx=0) (expect=1)
[ 783.204497] ATL1E 0000:04:00.0 p33p1: NIC Link is Up <100 Mbps Full Duplex>
[ 783.225336] ATL1E 0000:04:00.0 p33p1: rx sequence number error (rx=0) (expect=1)
[ 783.236636] ATL1E 0000:04:00.0 p33p1: NIC Link is Up <100 Mbps Full Duplex>
[ 783.462652] ATL1E 0000:04:00.0 p33p1: rx sequence number error (rx=0) (expect=1)
[ 783.472530] ATL1E 0000:04:00.0 p33p1: NIC Link is Up <100 Mbps Full Duplex>
[ 784.038976] ATL1E 0000:04:00.0 p33p1: rx sequence number error (rx=0) (expect=1)
[ 784.047354] ATL1E 0000:04:00.0 p33p1: NIC Link is Up <100 Mbps Full Duplex>
...
next prev parent reply other threads:[~2013-03-28 3:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 23:07 Atheros Communications Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) 1.0.0.7 md5/sha1 corrupted using NFS and samba (updated) Version 2 rebelyouth
2013-03-22 23:54 ` Eric Dumazet
2013-03-23 0:07 ` rebelyouth
2013-03-23 2:10 ` Hannes Frederic Sowa
2013-03-23 4:54 ` rebelyouth
2013-03-23 15:06 ` Hannes Frederic Sowa
2013-03-24 0:36 ` Sven Hartge
2013-03-24 1:26 ` Hannes Frederic Sowa
2013-03-24 1:35 ` Sven Hartge
2013-03-24 1:41 ` Hannes Frederic Sowa
2013-03-24 3:27 ` Huang, Xiong
2013-03-24 3:40 ` Hannes Frederic Sowa
2013-03-24 4:21 ` Huang, Xiong
2013-03-24 4:37 ` Hannes Frederic Sowa
2013-03-24 4:54 ` Huang, Xiong
2013-03-24 5:13 ` Hannes Frederic Sowa
2013-03-24 5:16 ` Huang, Xiong
2013-03-24 5:23 ` Hannes Frederic Sowa
2013-03-24 5:42 ` Huang, Xiong
2013-03-24 17:22 ` Eric Dumazet
2013-03-24 17:38 ` Hannes Frederic Sowa
2013-03-24 17:23 ` Hannes Frederic Sowa
2013-03-25 16:30 ` Hannes Frederic Sowa
2013-03-26 4:27 ` Hannes Frederic Sowa
2013-03-26 4:34 ` Huang, Xiong
2013-03-26 4:40 ` Hannes Frederic Sowa
2013-03-26 4:44 ` Huang, Xiong
2013-03-27 22:02 ` Hannes Frederic Sowa
2013-03-27 22:28 ` Huang, Xiong
2013-03-27 22:34 ` Hannes Frederic Sowa
2013-03-28 0:10 ` Huang, Xiong
2013-03-28 0:40 ` Hannes Frederic Sowa
2013-03-28 1:01 ` Huang, Xiong
2013-03-28 1:16 ` Hannes Frederic Sowa
2013-03-28 1:17 ` Huang, Xiong
2013-03-28 3:19 ` Hannes Frederic Sowa
2013-03-28 3:25 ` Huang, Xiong
2013-03-28 3:29 ` Hannes Frederic Sowa [this message]
2013-03-28 3:39 ` Huang, Xiong
2013-03-29 3:05 ` Hannes Frederic Sowa
2013-03-29 3:39 ` Huang, Xiong
2013-03-28 3:52 ` Huang, Xiong
2013-03-24 6:12 ` Huang, Xiong
2013-03-24 17:24 ` Hannes Frederic Sowa
2013-03-24 1:07 ` Sven Hartge
2013-03-23 0:01 ` Hannes Frederic Sowa
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=20130328032934.GD2176@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=sven@svenhartge.de \
--cc=xiong@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).