From: Kalle Valo <kvalo@codeaurora.org>
To: Mitchell Nordine <mitchell.nordine@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: Fwd: XPS 9310 MSI vectors patch for ath11k
Date: Sun, 15 Nov 2020 21:35:41 +0200 [thread overview]
Message-ID: <87zh3i1khe.fsf@codeaurora.org> (raw)
In-Reply-To: <CAJxb_Eq1NemrYh+DzrOiRfagZpcF5E4de=JPuU1EhspFF2nCWA@mail.gmail.com> (Mitchell Nordine's message of "Sun, 15 Nov 2020 16:16:25 +0100")
Mitchell Nordine <mitchell.nordine@gmail.com> writes:
> With Kalle's help I have managed to get wi-fi working on my XPS 13
> 9310 (with the QCA6390) working on NixOS.
>
> To do this, I switched to 5.10-rc2 and applied Kalle's patch for the
> XPS 9310 here[1] and installed the latest version of the firmware
> following the instructions outlined here[2].
>
> However, despite wi-fi working, with these changes my system has
> become incredibly unstable, often crashing resulting in a frozen
> desktop with nothing responding and no ability to switch to the other
> ttys.
>
> Occasionally however, the system will not crash, and instead the
> internet will simply drop out (though with GNOME still showing the
> wi-fi as "connected") with the following errors reported in
> journalctl:
To pinpoint the problem can you try Carl's suggestion adding
"memmap=12M\$20M" to kernel parameters:
http://lists.infradead.org/pipermail/ath11k/2020-November/000686.html
Let me know how it goes.
> I've also noticed that on each boot, there appear to be some errors
> during ath11k_pci initialisation related to a memory request and qmi.
>>From dmesg:
>
> [ 4.738943] ath11k_pci 0000:56:00.0: Respond mem req failed,
> result: 1, err: 0
> [ 4.738945] ath11k_pci 0000:56:00.0: qmi failed to respond fw mem
> req:-22
There's a fix coming for this error.
> [ 4.739070] ath11k_pci 0000:56:00.0: req mem_seg[0] 0x5a100000
> 524288 1
> [ 4.739071] ath11k_pci 0000:56:00.0: req mem_seg[1] 0x5a180000
> 524288 1
> [ 4.739072] ath11k_pci 0000:56:00.0: req mem_seg[2] 0x5a200000
> 524288 1
> [ 4.739072] ath11k_pci 0000:56:00.0: req mem_seg[3] 0x5a280000
> 294912 1
> [ 4.739073] ath11k_pci 0000:56:00.0: req
> mem_seg[4] 0x5a300000 524288 1
> [ 4.739073] ath11k_pci 0000:56:00.0: req mem_seg[5] 0x5a380000
> 524288 1
> [ 4.739074] ath11k_pci 0000:56:00.0: req mem_seg[6] 0x59c00000
> 458752 1
> [ 4.739074] ath11k_pci 0000:56:00.0: req mem_seg[7] 0x5a5c0000
> 131072 1
> [ 4.739075] ath11k_pci 0000:56:00.0: req
> mem_seg[8] 0x59c80000 524288 4
> [ 4.739075] ath11k_pci 0000:56:00.0: req mem_seg[9] 0x59d00000
> 360448 4
> [ 4.739076] ath11k_pci 0000:56:00.0: req
> mem_seg[10] 0x5a5a4000 16384 1
These are just debug messages to help diagnose the instability issues,
they will be removed in the final patch.
> For the record, bluetooth still does not appear to be working, though
> I'm not sure if this is expected or not at this point.
I don't know the status with bluetooth.
> I'm on NixOS, and unfortunately I haven't yet worked out how to enable
> the ath11k debugging options via `make menuconfig` in a declarative
> manner for my nix configuration. That said, if there are any other
> patches you would like me to test just let me know.
>
> Btw, I tried subscribing to the ath11k mailing list today and
> yesterday, but haven't received any ack or response, but maybe this is
> normal over the weekend.
Yes, weekends are normally pretty quiet here.
> In case anyone is interested in following along, I have a draft PR
> open at the nixos/nixos-hardware repo[3] for the Dell XPS 9310 which
> includes these WIP patches. This includes a nix module for installing
> the QCA6390 firmware and Kalle's patch mentioned above.
>
> [1]:
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> [2]: http://lists.infradead.org/pipermail/ath11k/2020-November/000537.html
> [3]: https://github.com/NixOS/nixos-hardware/pull/207
Nice, but do note that these patches are not finalised yet. So there
will be new versions coming.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-15 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJxb_EpOy-CqJhodHMcBDuOgeQoZrtims9stB4uGxz7kCz_Y7Q@mail.gmail.com>
[not found] ` <877dqn3m3t.fsf@codeaurora.org>
[not found] ` <CAJxb_EoTvUV3Bwq4O7DMS1AgvWD3VLq9e5Z_Y8FeGbSFxmvzbg@mail.gmail.com>
2020-11-15 15:16 ` Fwd: XPS 9310 MSI vectors patch for ath11k Mitchell Nordine
2020-11-15 19:35 ` Kalle Valo [this message]
[not found] ` <CAJxb_ErL6NhWNxp_yxFmTqB9v1q3VL399+V+yL4n3L1aBWuocQ@mail.gmail.com>
2020-11-16 9:30 ` Kalle Valo
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=87zh3i1khe.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=mitchell.nordine@gmail.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