From: Pavel Procopiuc <pavel.procopiuc@gmail.com>
To: David Hildenbrand <david@redhat.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org,
ath11k@lists.infradead.org
Subject: Re: Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()"
Date: Fri, 13 Nov 2020 09:17:55 +0100 [thread overview]
Message-ID: <dd24598f-7635-c2e2-9c6d-f320770e3b9e@gmail.com> (raw)
In-Reply-To: <cd8d1b1d-a646-b9b1-ed2a-4aa7070efe00@redhat.com>
Op 12.11.2020 om 11:48 schreef David Hildenbrand:
> Trying to understand the code, it looks like there are always two rounds of reqests. The first one always fails
> ("requesting one big chunk of DMA memory"), the second one (providing multiple chunks of DMA memory) is supposed to work
> - and we do allocate memory.
>
>
> In the *working* cases we have
>
> Respond mem req failed, result: 1, err: 0
> qmi failed to respond fw mem req:-22
> ...
> chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
>
> We don't fail in qmi_txn_wait() - second request w
>
>
> In the *non-working* cases we have
>
> Respond mem req failed, result: 1, err: 0
> qmi failed to respond fw mem req:-22
> ...
> qmi failed memory request, err = -110
> qmi failed to respond fw mem req:-110
>
> We fail in qmi_txn_wait(). We run into a timeout (ETIMEDOUT).
>
> Can we bump up the timeout limit and see if things change? Maybe FW needs more time with other addresses.
I tried increasing ATH11K_QMI_WLANFW_TIMEOUT_MS 20 times to 100000 (i.e. 100 seconds) and it didn't have any positive
effect, the second error (-110) just came 100 seconds later and not 5.
next prev parent reply other threads:[~2020-11-13 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa22cf0f-3bac-add6-8c71-6f6cad5206d8@gmail.com>
[not found] ` <87lffjodu7.fsf@codeaurora.org>
[not found] ` <fa338986-8de4-fde1-6805-d46793c947e4@gmail.com>
[not found] ` <c9cc0ec6-4dda-2608-3575-0e6dfb6d0852@gmail.com>
[not found] ` <87ft5rszcs.fsf@codeaurora.org>
[not found] ` <87ft5qsem9.fsf@codeaurora.org>
[not found] ` <f99862f4-9b3a-03e5-cd26-1de6136f9e46@gmail.com>
[not found] ` <87blgdscxd.fsf@codeaurora.org>
[not found] ` <229c31e7-9aff-18e6-a6db-be7b46331173@gmail.com>
2020-11-05 9:04 ` Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()" Kalle Valo
2020-11-05 9:47 ` Pavel Procopiuc
2020-11-05 10:42 ` Vlastimil Babka
2020-11-05 10:45 ` Pavel Procopiuc
2020-11-05 11:13 ` David Hildenbrand
2020-11-05 12:55 ` Pavel Procopiuc
2020-11-05 20:23 ` David Hildenbrand
2020-11-06 17:32 ` Pavel Procopiuc
2020-11-06 20:41 ` David Hildenbrand
[not found] ` <87eekz4s04.fsf@codeaurora.org>
2020-11-11 20:41 ` Pavel Procopiuc
2020-11-12 10:48 ` David Hildenbrand
2020-11-13 8:17 ` Pavel Procopiuc [this message]
[not found] ` <f1f471905ea99ad9b9c8a8eeae616ff9@codeaurora.org>
2020-11-13 12:52 ` Pavel Procopiuc
2020-11-13 13:36 ` wi nk
2020-11-13 13:56 ` David Hildenbrand
2020-11-13 15:49 ` wi nk
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=dd24598f-7635-c2e2-9c6d-f320770e3b9e@gmail.com \
--to=pavel.procopiuc@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ath11k@lists.infradead.org \
--cc=david@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vbabka@suse.cz \
/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).