From: Pavel Procopiuc <pavel.procopiuc@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Tue, 3 Nov 2020 14:12:10 +0100 [thread overview]
Message-ID: <c25b5029-4f21-c621-1416-3646d90b6a7f@gmail.com> (raw)
In-Reply-To: <87ft5rszcs.fsf@codeaurora.org>
I have another probably interesting finding. I was trying to create a QCA6390-enabled kernel with the latest stable
version 5.9.3. But I only succeeded in making 5.9.1 work, in 5.9.2 loading the driver resulted in a quite weird behavior:
# journalctl -b-1 | grep -iP '05:00|ath11k|Linux version'
Nov 03 10:11:45 razor kernel: Linux version 5.9.2-gentoo-wt-ath (root@razor) (gcc (Gentoo 9.3.0-r1 p3) 9.3.0, GNU ld
(Gentoo 2.34 p6) 2.34.0) #1 SMP Tue Nov 3 09:55:08 CET 2020
Nov 03 10:11:45 razor kernel: pci 0000:05:00.0: [17cb:1101] type 00 class 0x028000
Nov 03 10:11:45 razor kernel: pci 0000:05:00.0: reg 0x10: [mem 0xd2100000-0xd21fffff 64bit]
Nov 03 10:11:45 razor kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 03 10:11:45 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 03 10:11:45 razor kernel: pci 0000:05:00.0: Adding to iommu group 21
Nov 03 10:12:35 razor dbus-daemon[694]: [system] Activating via systemd: service name='net.reactivated.Fprint'
unit='fprintd.service' requested by ':1.73' (uid=0 pid=2258 comm="sudo modprobe ath11k_pci ")
Nov 03 10:12:39 razor sudo[2258]: pro : TTY=pts/1 ; PWD=/home/pro ; USER=root ; COMMAND=/sbin/modprobe ath11k_pci
Nov 03 10:12:39 razor kernel: ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
Nov 03 10:12:39 razor kernel: ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
Nov 03 10:12:39 razor kernel: ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
Nov 03 10:12:39 razor kernel: mhi 0000:05:00.0: Requested to power ON
Nov 03 10:12:39 razor kernel: mhi 0000:05:00.0: Power on setup success
That's it, it didn't go any further, no wifi device appeared. But the patch for 5.9.2 is quite big and there is a number
of non-obvious conflicts so that might be just me resolving them incorrectly.
Also on 5.9.1 with the working driver I'm seeing those lines in the log:
* appears right after loading the kernel module:
Nov 03 09:32:57 razor kernel: ath11k_pci 0000:05:00.0: Unknown eventid: 0x16005
* seems to be related to the disconnection from the access point:
Nov 03 09:33:05 razor kernel: ath11k_pci 0000:05:00.0: Unknown eventid: 0x1d00a
* some boots I see a bunch of those in a row, some boots it's not there at all, seems to be happening after successful
connect the the AP:
Nov 03 09:33:20 razor kernel: ath11k_pci 0000:05:00.0: Unknown eventid: 0x4005
There is not many of those, nothing to worry about, but just wanted to let you know.
Op 03.11.2020 om 07:56 schreef Kalle Valo:
> Interesting, and worrisome. I have not yet tested v5.10-rc releases,
> I'll do that ASAP and try to reproduce your issue. If I see the same
> problem then it should be possible to bisect the issue pretty easily.
>
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-03 13:12 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 [this message]
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
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=c25b5029-4f21-c621-1416-3646d90b6a7f@gmail.com \
--to=pavel.procopiuc@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@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).