ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mitchell Nordine <mail@mitchellnordine.com>
Cc: wi nk <wink@technolu.st>,
	"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Have the QCA6390 patches for XPS 9310 landed yet?
Date: Thu, 26 Aug 2021 17:40:18 +0300	[thread overview]
Message-ID: <87ilzs6zhp.fsf@codeaurora.org> (raw)
In-Reply-To: <UUsN-OH9rM-606TuwUORGzSqrxv4eWc3pX5FYhYcS2eM9gpEG5NrqDgXKkhdkNDwdk_mEaoRoFhBlRahF_Pak_cI0YILecZzkAhEMfH6LZU=@mitchellnordine.com> (Mitchell Nordine's message of "Wed, 04 Aug 2021 13:06:25 +0000")

Mitchell Nordine <mail@mitchellnordine.com> writes:

>> I've been running 5.12 and 5.13 without WIFI issues. Occasionally I
>> still have bluetooth problems and the i915 drivers are causing video
>> artifacts randomly, but the wireless connection seems pretty solid at
>> this point.
>
> Thanks for the udpate!
>
> Recently a collaborator updated the `nixos/nixos-hardware` repo's
> kernel version to `5.12.9` for the xps 9310 as wifi and bluetooth is
> working out-of-the-box for them now. I was excited to update and try
> this myself, however despite having the same kernel version (5.12.9),
> the same qca6390 fw version (fw_version 0x101c06cc fw_build_timestamp
> 2020-06-24 19:50) and almost the same system firmware version (them
> 3.0.3, me 3.0.4) I'm running into an issue where I get some `qmi`
> errors and then the wifi firmware ends up crashing. Here's the
> relevant dmesg output on my system:
>
> $ dmesg | grep -e ath11
> [ 3.937129] ath11k_pci 0000:72:00.0: BAR 0: assigned [mem
> 0xa2500000-0xa25fffff 64bit]
> [    3.937147] ath11k_pci 0000:72:00.0: enabling device (0000 -> 0002)
> [ 4.203596] ath11k_pci 0000:72:00.0: chip_id 0x0 chip_family 0xb
> board_id 0xff soc_id 0xffffffff
> [ 4.207005] ath11k_pci 0000:72:00.0: fw_version 0x101c06cc
> fw_build_timestamp 2020-06-24 19:50 fw_build_id
> [ 9.291281] ath11k_pci 0000:72:00.0: qmi failed set mode request,
> mode: 0, err = -110
> [    9.291293] ath11k_pci 0000:72:00.0: qmi failed to send wlan fw mode:-110
> [    9.291297] ath11k_pci 0000:72:00.0: failed to attach wmi: -110
> [    9.291305] ath11k_pci 0000:72:00.0: failed to start core: -110
> [   20.250729] ath11k_pci 0000:72:00.0: firmware crashed: MHI_CB_SYS_ERROR
>
> My collaborator's system (whose wifi is working) has the same output,
> but without the last 5 lines of errors:
>
> ~ » dmesg | grep -e ath11
> [ 19.872599] ath11k_pci 0000:72:00.0: BAR 0: assigned [mem
> 0xa2500000-0xa25fffff 64bit]
> [   19.872617] ath11k_pci 0000:72:00.0: enabling device (0000 -> 0002)
> [ 20.380168] ath11k_pci 0000:72:00.0: chip_id 0x0 chip_family 0xb
> board_id 0xff soc_id 0xffffffff
> [ 20.380171] ath11k_pci 0000:72:00.0: fw_version 0x101c06cc
> fw_build_timestamp 2020-06-24 19:50 fw_build_id
>
> Here's their PR that removes the patches and updates to the 5.12
> kernel. https://github.com/NixOS/nixos-hardware/pull/298
>
> I checked out the bug report mentioned by justin
> (https://bugzilla.kernel.org/show_bug.cgi?id=212059) however it
> appears to be unrelated... at least I don't see any of the same `qmi`
> errors, and their firmware at least runs long enough that they can
> connect to a 2.4GHz network.
>
> Any ideas what might be going on here?

Did you set the memmap parameter explained in [1]. I strongly recommend
everyone to set the memmap until the firmware is fixed.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=210923

-- 
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

      reply	other threads:[~2021-08-26 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 16:30 Have the QCA6390 patches for XPS 9310 landed yet? Mitchell Nordine
2021-07-30 20:00 ` Kalle Valo
2021-07-30 20:08   ` wi nk
2021-07-30 21:52     ` Justin Mazzola Paluska
2021-07-30 21:57       ` wi nk
2021-07-30 22:11       ` Jens Gecius
2021-08-02  7:20         ` Dominik Förderer
2021-08-02 14:06     ` Kalle Valo
2021-08-04 13:06     ` Mitchell Nordine
2021-08-26 14:40       ` Kalle Valo [this message]

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=87ilzs6zhp.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mail@mitchellnordine.com \
    --cc=wink@technolu.st \
    /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