ntb.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Marc Smith <msmith626@gmail.com>
Cc: ntb@lists.linux.dev, Kelvin Cao <kelvin.cao@microchip.com>,
	kelvincao@outlook.com
Subject: Re: ntb_netdev Communication Failure Issue
Date: Wed, 9 Mar 2022 09:52:32 -0700	[thread overview]
Message-ID: <0c3b408a-80b2-992d-0a75-f76977dcb4e9@deltatee.com> (raw)
In-Reply-To: <CAH6h+hd7o7fWFVmPSn86SrgnHC5X_jfdRtn1=dAF=8w8knJK1g@mail.gmail.com>



On 2022-03-09 07:35, Marc Smith wrote:
> No difference between the two above, and actually, comparing the
> entire 4 MiB of GAS dump taken while working/functional versus broken
> state shows no differences:
> # cmp switchtec0_gas_dump_after_ifup_working.1 switchtec0_gas_dump_broken.1

Well I'm stumped. It looks like the receive side is getting the
doorbell, but when it reads the memory window the done flag is not set,
so it doesn't process any packets. The transmit side then fills up the
memory window and breaks.

So it sounds like the read side is not reading the correct data from the
memory window. Like it's cache or something (which it shouldn't be). But
I have no idea what could cause that.

Logan

  reply	other threads:[~2022-03-09 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:16 ntb_netdev Communication Failure Issue Marc Smith
2022-02-16 17:14 ` Logan Gunthorpe
2022-02-17 15:22   ` Marc Smith
2022-02-17 16:31     ` Eric Pilmore
2022-02-17 16:49     ` Logan Gunthorpe
2022-03-09 14:35       ` Marc Smith
2022-03-09 16:52         ` Logan Gunthorpe [this message]
2022-03-09 18:26           ` Marc Smith
2022-03-09 18:31             ` Logan Gunthorpe

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=0c3b408a-80b2-992d-0a75-f76977dcb4e9@deltatee.com \
    --to=logang@deltatee.com \
    --cc=kelvin.cao@microchip.com \
    --cc=kelvincao@outlook.com \
    --cc=msmith626@gmail.com \
    --cc=ntb@lists.linux.dev \
    /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).