And try to use following code to replace atl1c_configure_dma

static inline void atl1e_configure_dma(struct atl1e_adapter *adapter)
{
	struct atl1e_hw *hw = &adapter->hw;
	u32 dma_ctrl_data;

	dma_ctrl_data = DMA_CTRL_RXCMB_EN | 0x400000;
	dma_ctrl_data |= (((u32)hw->dmar_block) & DMA_CTRL_DMAR_BURST_LEN_MASK)
		<< DMA_CTRL_DMAR_BURST_LEN_SHIFT;
	dma_ctrl_data |= (((u32)hw->dmaw_block) & DMA_CTRL_DMAW_BURST_LEN_MASK)
		<< DMA_CTRL_DMAW_BURST_LEN_SHIFT;
	dma_ctrl_data |= DMA_CTRL_DMAR_REQ_PRI | DMA_CTRL_DMAR_OUT_ORDER;
	dma_ctrl_data |= (((u32)hw->dmar_dly_cnt) & DMA_CTRL_DMAR_DLY_CNT_MASK)
		<< DMA_CTRL_DMAR_DLY_CNT_SHIFT;
	dma_ctrl_data |= (((u32)hw->dmaw_dly_cnt) & DMA_CTRL_DMAW_DLY_CNT_MASK)
		<< DMA_CTRL_DMAW_DLY_CNT_SHIFT;

	AT_WRITE_REG(hw, REG_DMA_CTRL, dma_ctrl_data);
	return;
}


Thanks
Xiong

-----Original Message-----
From: Huang, Xiong
Sent: Sunday, March 24, 2013 1:43 PM
To: 'Hannes Frederic Sowa'
Cc: Sven Hartge; 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

quoted

quoted

quoted

The caputered packets show that a 16 byte segment overwrites later
data in the same packet, sometimes even multiple contiguous 16
byte

segments.

quoted

quoted

The corrupted packets look like this:

...ABC....DBBEF..

Each character represents a 16 byte region, the dots are dont-care
placeholders. The BB-region is overwritten by the data of the
first B-

region.

quoted

quoted

It looks like a DMA issue. Not checksum related. :(

Yes, I think so, too. Until this is resolved I would propose to not
set CHECKSUM_UNNECESSARY because it could corrupt data (like for the
original poster).

Do you have any idea where how these errors could be resolved? I e.g.
could not reproduce it with FreeBSD and the driver seems to be related
to the linux driver.

1.  pages cross 4GB bouandary ?  or overlap with each other ?
2. try to set hw->dmaw_block = atl1e_dma_req_128 3. can you print reg15C0
content when the NIC is in normal tx/rx status ?
4. other possible may be related the diff register configuration, but it's very
difficult to compare with Windows driver :(

Thanks
Xiong