linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Oh <peter.oh@eero.com>
To: Zhi Chen <zhichen@codeaurora.org>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC] Revert "ath10k: fix DMA related firmware crashes on multiple devices"
Date: Tue, 22 Oct 2019 10:16:53 -0700	[thread overview]
Message-ID: <d6cfd945-7bab-a01d-0157-e0e1802f66e3@eero.com> (raw)
In-Reply-To: <1571734629-18028-1-git-send-email-zhichen@codeaurora.org>


On 10/22/19 1:57 AM, Zhi Chen wrote:
> This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
> PCIe hung issue was observed on multiple platforms. The issue was reproduced
> when DUT was configured as AP and associated with 50+ STAs.
>
> With PCIe protocol analyzer, we can see DMA Read crossing 4KB boundary when
> issue happened. It broke PCIe spec and caused PCIe stuck.

How can you say value 0 (I believe it's 64 bytes) DMA burst size causes 
the symptom and 1 fixes it?

Peter


  parent reply	other threads:[~2019-10-22 17:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  8:57 [PATCH RFC] Revert "ath10k: fix DMA related firmware crashes on multiple devices" Zhi Chen
2019-10-22 10:07 ` Tom Psyborg
2019-10-30  2:44   ` zhichen
2019-11-06 10:01     ` Tom Psyborg
2019-11-07  5:35       ` zhichen
2019-10-22 17:16 ` Peter Oh [this message]
2019-10-22 18:24   ` Adrian Chadd
2019-10-30  6:04     ` Peter Oh
2019-10-30  6:28     ` zhichen
2019-10-30  6:16   ` zhichen
2019-10-30 23:01     ` Peter Oh
2019-11-03 15:36     ` Tom Psyborg
2019-11-04 18:41       ` Peter Oh

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=d6cfd945-7bab-a01d-0157-e0e1802f66e3@eero.com \
    --to=peter.oh@eero.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zhichen@codeaurora.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).