ath11k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jens Gecius <kernel@gecius.de>
To: ath11k@lists.infradead.org
Subject: Re: qca/hci issues with Bluetooth on Dell XPS 13/AX500 (9310)
Date: Tue, 22 Jun 2021 11:50:14 +0200	[thread overview]
Message-ID: <b6670ede-ffbb-02bc-0607-db267329585c@gecius.de> (raw)
In-Reply-To: <d078b4bb-0cd5-ee9f-5d5d-6a95b3fe2ed9@gecius.de>

Am 11.05.21 um 15:02 schrieb Jens Gecius:
> Dear all,
>
> there was an earlier (March 30 "issues with QCA6390 on Dell XPS 13") 
> report of the same/similar problem (just realized today).
>
> As that reporter, I have a Dell XPS 13 dev edition/Ubuntu (working). 
> My 9310 has the AX500 Killer Wifi. Wifi is working fine, but Bluetooth 
> always gives me a crash (I blacklisted BT required modules to later 
> trigger the oops myself or run without). The crash renders the 
> suspend/resume capabilities inoperable, the hci_uart module is not 
> removeable.
>
> I tried to get differences of the Dell supplied Ubuntu-OEM 5.6 kernel 
> to current mainline, but my grey matter is unable to digest that 
> information and supply helpful hints.
> /lib/firmware-files were the same on Ubuntu and Fedora (it recently 
> got updated on my Fedora 34 - crash unchanged).
>
> Full dmesg output of module loading attached.
>
> Intentionally, I did a suspend-resume cycle first for your kind 
> information and then loaded the BT modules. The crash also occurs if I 
> load the hci_uart directly after system startup.
>
> That is unchanged since receiving the notebook in April, even with 
> earlier firmware version. I am on the latest Fedora kernel, now 
> 5.11.18-300.fc34.x86_64. BIOS is latest 2.2.0.
>
> The trace says, that qca_read_soc_version is causing the crash during 
> qca_uart_setup in btqca. Is that correct?
>

Just to report back, that bluetooth works with 5.12.11 (.10 didn't). As 
far as I can see, a change to net/bluetooth/hci_core.c was made. Not 
sure, if this is the relevant change.



> And - maybe I'm on the wrong list here (BT / ath11k) anyway, please 
> let me know if so. :-)
>
> If I can support, please let me know. Thank you very much.
>
> Best
>  Jens
>



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      reply	other threads:[~2021-06-22  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 13:02 qca/hci issues with Bluetooth on Dell XPS 13/AX500 (9310) Jens Gecius
2021-06-22  9:50 ` Jens Gecius [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=b6670ede-ffbb-02bc-0607-db267329585c@gecius.de \
    --to=kernel@gecius.de \
    --cc=ath11k@lists.infradead.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).