From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-mediatek@lists.infradead.org, Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Ryder Lee <ryder.lee@mediatek.com>, Roy Luo <royluo@google.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: mt76x2e hardware restart
Date: Wed, 16 Oct 2019 18:38:42 +0200 [thread overview]
Message-ID: <20191016163842.GA18799@localhost.localdomain> (raw)
In-Reply-To: <96f43a2103a9f2be152c53f867f5805c@natalenko.name>
[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]
> Hello.
>
> On 15.10.2019 18:52, Oleksandr Natalenko wrote:
> > Thanks for the answer and the IRC discussion. As agreed I've applied
> > [1] and [2], and have just swapped the card to try it again. So far,
> > it works fine in 5 GHz band in 802.11ac mode as an AP.
> >
> > I'll give it more load with my phone over evening, and we can discuss
> > what to do next (if needed) tomorrow again. Or feel free to drop me an
> > email today.
> >
> > Thanks for your efforts.
> >
> > [1]
> > https://github.com/LorenzoBianconi/wireless-drivers-next/commit/cf3436c42a297967235a9c9778620c585100529e.patch
> > [2]
> > https://github.com/LorenzoBianconi/wireless-drivers-next/commit/aad256eb62620f9646d39c1aa69234f50c89eed8.patch
>
> As agreed, here are iperf3 results, AP to STA distance is 2 meters.
>
> Client sends, TCP:
>
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.00 sec 70.4 MBytes 59.0 Mbits/sec 3800
> sender
> [ 5] 0.00-10.03 sec 70.0 MBytes 58.6 Mbits/sec
> receiver
>
> Client receives, TCP:
>
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.06 sec 196 MBytes 163 Mbits/sec 3081
> sender
> [ 5] 0.00-10.01 sec 191 MBytes 160 Mbits/sec
> receiver
>
> Client sends, UDP, 128 streams:
>
> [ ID] Interval Transfer Bitrate Jitter Lost/Total
> Datagrams
> [SUM] 0.00-10.00 sec 160 MBytes 134 Mbits/sec 0.000 ms 0/115894
> (0%) sender
> [SUM] 0.00-10.01 sec 160 MBytes 134 Mbits/sec 0.347 ms 0/115892
> (0%) receiver
>
> Client receives, UDP, 128 streams:
>
> [ ID] Interval Transfer Bitrate Jitter Lost/Total
> Datagrams
> [SUM] 0.00-10.01 sec 119 MBytes 99.4 Mbits/sec 0.000 ms 0/85888 (0%)
> sender
> [SUM] 0.00-10.00 sec 119 MBytes 99.5 Mbits/sec 0.877 ms 0/85888 (0%)
> receiver
>
> Given the HW is not the most powerful, the key point here is that nothing
> crashed after doing these tests.
Hi Oleksandr,
thx a lot for testing these 2 patches. Now we need to understand why the chip
hangs if we enable scatter gather dma transfer on x86 while it is working fine
on multiple mips/arm devices (patch 2/2 just disable it for debugging).
Regards,
Lorenzo
>
> --
> Oleksandr Natalenko (post-factum)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-10-16 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 16:24 mt76x2e hardware restart Oleksandr Natalenko
2019-09-19 21:22 ` Oleksandr Natalenko
2019-09-20 6:07 ` Oleksandr Natalenko
2019-10-12 16:50 ` Lorenzo Bianconi
2019-10-13 3:30 ` [PATCH] mt76: mt76x2: disable pcie_aspm by default kbuild test robot
2019-10-15 16:52 ` mt76x2e hardware restart Oleksandr Natalenko
2019-10-16 16:31 ` Oleksandr Natalenko
2019-10-16 16:38 ` Lorenzo Bianconi [this message]
2019-10-23 8:50 ` Lorenzo Bianconi
2019-10-23 16:25 ` Oleksandr Natalenko
2019-10-24 9:43 ` Daniel Golle
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=20191016163842.GA18799@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=royluo@google.com \
--cc=ryder.lee@mediatek.com \
--cc=sgruszka@redhat.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).