From: Ben Greear <greearb@candelatech.com>
To: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>,
"nbd@openwrt.org" <nbd@openwrt.org>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
Rajkumar Manoharan <rmanohar@codeaurora.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Regression in qca99x0 on x86 platform (kernel: 4.7.0-rc1-wt-ath
Date: Thu, 2 Jun 2016 10:27:22 -0700 [thread overview]
Message-ID: <57506C7A.7070109@candelatech.com> (raw)
In-Reply-To: <f495d218d54a4c4c859849a85f38ab0c@aphydexm01b.ap.qualcomm.com>
On 06/02/2016 10:20 AM, Manoharan, Rajkumar wrote:
> Found a regression in ath.git TOT that system hangs while probing qca99x0 device on x86_64 platform.
> It seems the system hangs while DMA mapping of bigger memory chunks. Below are the list of memory
> chucks requested by target for qca99x0 during service ready event. This issue is seen only on x86 platform.
> No issues are observed on ARM platform (AP148). After reverting below commit able to bring up device on x86.
>
> Jun 2 17:24:37 rmanohar-arch kernel: idx 0 pool_size 689816 num_units 529 unit_len 1304
> Jun 2 17:24:37 rmanohar-arch kernel: idx 1 pool_size 17152 num_units 67 unit_len 256
> Jun 2 17:24:37 rmanohar-arch kernel: idx 2 pool_size 68608 num_units 67 unit_len 1024
> Jun 2 17:24:37 rmanohar-arch kernel: idx 3 pool_size 274432 num_units 67 unit_len 4096
> Jun 2 17:24:37 rmanohar-arch kernel: idx 4 pool_size 107520 num_units 35 unit_len 3072
> Jun 2 17:24:37 rmanohar-arch kernel: idx 5 pool_size 6144 num_units 1 unit_len 6144
> Jun 2 17:24:37 rmanohar-arch kernel: idx 6 pool_size 865444 num_units 529 unit_len 1636
We have seen similar. But, if we enable VT-d in our BIOS, then it works, at least in
our scenarios. I have not tried putting more than one 99x0 NIC in a system to date, so possibly
more than one would cause more issues, and I guess systems without VT-d might
fail too...
Thanks,
Ben
>
> commit b057886524be060021e3cfad0ba8458c850330cd
> Author: Felix Fietkau <nbd@openwrt.org>
> Date: Mon Nov 30 19:32:01 2015 +0100
>
> ath10k: do not use coherent memory for allocated device memory chunks
>
> Coherent memory is more expensive to allocate (and constrained on some
> architectures where it has to be pre-allocated). It is also completely
> unnecessary, since the host has no reason to even access these allocated
> memory spaces
>
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
>
> -Rajkumar
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-02 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 17:20 Regression in qca99x0 on x86 platform (kernel: 4.7.0-rc1-wt-ath Manoharan, Rajkumar
2016-06-02 17:27 ` Ben Greear [this message]
2016-06-02 17:46 ` Rajkumar Manoharan
2016-06-02 17:52 ` Ben Greear
2016-06-14 6:21 ` Rajkumar Manoharan
2016-06-14 13:44 ` Ben Greear
2016-06-15 2:55 ` Rajkumar Manoharan
2016-06-03 16:02 ` Valo, Kalle
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=57506C7A.7070109@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=nbd@openwrt.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.qualcomm.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 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.