From: Pavel Procopiuc <pavel.procopiuc@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
akpm@linux-foundation.org, ath11k@lists.infradead.org,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()"
Date: Fri, 6 Nov 2020 18:32:50 +0100 [thread overview]
Message-ID: <15e33a0a-9a76-0966-125a-5941e2cdfb09@gmail.com> (raw)
In-Reply-To: <C3FD015A-8E51-4752-AD76-6ABE4583E268@redhat.com>
Op 05.11.2020 om 21:23 schreef David Hildenbrand:
>> So just to make sure I understand you correctly, you'd like to see if the problem with ath11k driver on my hardware persists when I boot pristine 5.10-rc2 kernel (without reverting commit 7fef431be9c9ac255838a9578331567b9dba4477) and with page_alloc.shuffle=1, right?
>>
>
> Right, but as lists are randomized then it might take a couple of tries to reproduce. I‘ll have a look at the driver code / failing path on Monday, when back to work.
I have done 5 boots of pristine 5.10-rc2 with page_alloc.shuffle=1. Out of those: 1st, 2nd, 4th and 5th resulted in
working ath11k driver, logs were the same as with the commit 7fef431be9c9ac255838a9578331567b9dba4477 reverted. The 3rd
one failed, but in a different way, I just had no output from the driver after initialization lines:
Nov 06 18:19:41 razor kernel: Linux version 5.10.0-rc2 (root@razor) (gcc (Gentoo 9.3.0-r1 p3) 9.3.0, GNU ld (Gentoo 2.34
p6) 2.34.0) #8 SMP Fri Nov 6 18:14:36 CET 2020
Nov 06 18:19:41 razor kernel: pci 0000:05:00.0: [17cb:1101] type 00 class 0x028000
Nov 06 18:19:41 razor kernel: pci 0000:05:00.0: reg 0x10: [mem 0xd2100000-0xd21fffff 64bit]
Nov 06 18:19:41 razor kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 06 18:19:41 razor kernel: pci 0000:05:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at
0000:00:1c.1 (capable of 7.876 Gb/s with 8.0 GT/s PCIe x1 link)
Nov 06 18:19:41 razor kernel: pci 0000:05:00.0: Adding to iommu group 21
Nov 06 18:19:42 razor kernel: ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
Nov 06 18:19:42 razor kernel: ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
Nov 06 18:19:42 razor kernel: ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
Nov 06 18:19:42 razor kernel: mhi 0000:05:00.0: Requested to power ON
Nov 06 18:19:42 razor kernel: mhi 0000:05:00.0: Power on setup success
I had this before and usually it was fixed after rebooting into Windows and back. This time I just went and rebooted
into Linux again and driver was working on that boot (4th).
After that I removed page_alloc.shuffle=1 and did 2 additional boots, both of them resulted in a non-working driver with
the error messages about not being able to talk to firmware like I had before on the clean 5.10-rc2:
Nov 06 18:24:07 razor kernel: Linux version 5.10.0-rc2 (root@razor) (gcc (Gentoo 9.3.0-r1 p3) 9.3.0, GNU ld (Gentoo 2.34
p6) 2.34.0) #9 SMP Fri Nov 6 18:22:43 CET 2020
Nov 06 18:24:07 razor kernel: pci 0000:05:00.0: [17cb:1101] type 00 class 0x028000
Nov 06 18:24:07 razor kernel: pci 0000:05:00.0: reg 0x10: [mem 0xd2100000-0xd21fffff 64bit]
Nov 06 18:24:07 razor kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 06 18:24:07 razor kernel: pci 0000:05:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at
0000:00:1c.1 (capable of 7.876 Gb/s with 8.0 GT/s PCIe x1 link)
Nov 06 18:24:07 razor kernel: pci 0000:05:00.0: Adding to iommu group 21
Nov 06 18:24:08 razor kernel: ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
Nov 06 18:24:08 razor kernel: ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
Nov 06 18:24:08 razor kernel: ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
Nov 06 18:24:08 razor kernel: mhi 0000:05:00.0: Requested to power ON
Nov 06 18:24:08 razor kernel: mhi 0000:05:00.0: Power on setup success
Nov 06 18:24:08 razor kernel: ath11k_pci 0000:05:00.0: Respond mem req failed, result: 1, err: 0
Nov 06 18:24:08 razor kernel: ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-22
Nov 06 18:24:13 razor kernel: ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
Nov 06 18:24:13 razor kernel: ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
Nov 06 18:25:39 razor kernel: mhi 0000:05:00.0: Device failed to exit MHI Reset state
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-06 17:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 10:32 PROBLEM: unable to get QCA6390 to work Pavel Procopiuc
2020-11-02 17:42 ` Kalle Valo
2020-11-02 18:21 ` Pavel Procopiuc
2020-11-02 21:14 ` Pavel Procopiuc
2020-11-03 6:56 ` Kalle Valo
2020-11-03 13:12 ` Pavel Procopiuc
2020-11-04 9:32 ` Pavel Procopiuc
2020-11-03 14:23 ` Kalle Valo
2020-11-03 21:01 ` Pavel Procopiuc
2020-11-04 9:12 ` Kalle Valo
2020-11-04 22:15 ` Pavel Procopiuc
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 [this message]
2020-11-06 20:41 ` David Hildenbrand
2020-11-11 19:23 ` Kalle Valo
2020-11-11 20:41 ` Pavel Procopiuc
2020-11-12 10:48 ` David Hildenbrand
2020-11-13 8:17 ` Pavel Procopiuc
2020-11-13 11:08 ` Carl Huang
2020-11-13 11:44 ` Carl Huang
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
2020-11-03 8:42 ` PROBLEM: unable to get QCA6390 to work Carl Huang
2020-11-03 14:12 ` Pavel Procopiuc
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=15e33a0a-9a76-0966-125a-5941e2cdfb09@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).