All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhadram Varka <vbhadram@nvidia.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: STMMAC driver with TSO enabled issue
Date: Fri, 25 May 2018 19:55:09 +0530	[thread overview]
Message-ID: <94cda7c4-127c-cae1-e51e-8853224065e2@nvidia.com> (raw)
In-Reply-To: <78914761-0375-5929-ed88-5225e0e260b9@synopsys.com>

Hi Jose,

On 5/25/2018 7:35 PM, Jose Abreu wrote:
> Hi Bhadram,
> 
> On 25-05-2018 05:41, Bhadram Varka wrote:
>> Hi Jose,
>>
>> On 5/24/2018 3:01 PM, Jose Abreu wrote:
>>> Hi Bhadram,
>>>
>>> On 24-05-2018 06:58, Bhadram Varka wrote:
>>>>
>>>> After some time if check Tx descriptor status - then I see only
>>>> below
>>>>
>>>> [..]
>>>> [85788.286730] 027 [0x827951b0]: 0xf854f000 0x0 0x16d8
>>>> 0x90000000
>>>>
>>>> index 025 and 026 descriptors processed but not index 027.
>>>>
>>>> At this stage Tx DMA is always in below state -
>>>>
>>>> ■ 3'b011: Running (Reading Data from system memory
>>>> buffer and queuing it to the Tx buffer (Tx FIFO))
>>>
>>> Thats strange, I think the descriptors look okay though. I will
>>> need the registers values (before the lock) and, if possible, the
>>> git bisect output.
>>
>> Attaching the register dump file after the issue observed.
>> Please check once.
>>
> 
> ----->8-----
> 0x112c = 0x0000003F
> 0x11ac = 0x0000003F
> 0x122c = 0x0000003F
> 0x12ac = 0x0000003F
> 
> 0x1130 = 0x0000003F
> 0x11b0 = 0x0000003F
> 0x1230 = 0x0000003F
> 0x12b0 = 0x0000003F
> ----->8-----
> 
> This can't be right, it should be DMA_{RX/TX}_SIZE - 1 = 511. Did
> you change these values in the code?
> 

Yes. I have changed the descriptor length to 64 - so that searching for 
the current descriptor status would be easy.

-- 
Thanks,
Bhadram.

  reply	other threads:[~2018-05-25 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fcb38ad0-a6e4-ce65-ead0-eb98ff0913a5@nvidia.com>
     [not found] ` <be22393f-bdea-0171-ea2d-04f8e9b9555f@synopsys.com>
     [not found]   ` <89c0a735-9e34-89c6-7692-579e48dadaa6@nvidia.com>
2018-05-10  8:55     ` STMMAC driver with TSO enabled issue Jose Abreu
2018-05-10 14:29       ` Jose Abreu
2018-05-10 15:08         ` Bhadram Varka
2018-05-10 15:45           ` Jose Abreu
2018-05-15  6:44             ` Bhadram Varka
2018-05-17 14:13               ` Jose Abreu
2018-05-24  5:58                 ` Bhadram Varka
2018-05-24  9:31                   ` Jose Abreu
2018-05-25  4:41                     ` Bhadram Varka
2018-05-25 14:05                       ` Jose Abreu
2018-05-25 14:25                         ` Bhadram Varka [this message]
2018-05-25 14:32                           ` Jose Abreu
2018-05-28  9:15                             ` Bhadram Varka
2018-05-28 10:56                               ` Jose Abreu
2018-05-29 15:43                                 ` Bhadram Varka

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=94cda7c4-127c-cae1-e51e-8853224065e2@nvidia.com \
    --to=vbhadram@nvidia.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Jose.Abreu@synopsys.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.