All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mitchell Nordine <mail@mitchellnordine.com>
Cc: Stephen Liang <stephenliang7@gmail.com>,
	Carl Huang <cjhuang@codeaurora.org>,
	"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
	wi nk <wink@technolu.st>
Subject: Re: ath11k: QCA6390 on Dell XPS 13 and kernel crashes
Date: Wed, 16 Dec 2020 10:50:28 +0200	[thread overview]
Message-ID: <87lfdyxhgr.fsf@codeaurora.org> (raw)
In-Reply-To: <GEqEHwkxcbfwllceC1TRVJLtj8Dmwp8siybWHHJNuiG4DSh9Ovh293KwSJfMwfykp1ToCm3Jh_hxLlNr-XaNNsMJFvErV3vjVXfOrXgprJw=@mitchellnordine.com> (Mitchell Nordine's message of "Sun, 13 Dec 2020 00:59:48 +0000")

Mitchell Nordine <mail@mitchellnordine.com> writes:

>> > Ok I tried to boot 5.10-rc6 with
>> > 59c6d022df8efb450f82d33dd6a6812935bd022f (single msi) and reverted
>> > 7fef431be9c9. With this kernel, I can't get the wifi adapter to come
>> > up, but no freezing. I receive this consistently:
>> > [ 23.959920] mhi 0000:55:00.0: Requested to power ON
>> > [ 23.960058] mhi 0000:55:00.0: Power on setup success
>> > [ 24.362295] ath11k_pci 0000:55:00.0: Respond mem req failed, result: 1, err:
>> > 0
>> > [ 24.362303] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
>> > [ 24.374433] ath11k_pci 0000:55:00.0: chip_id 0x0 chip_family 0xb board_id 0xf
>> > f soc_id 0xffffffff
>> > [ 24.374438] ath11k_pci 0000:55:00.0: fw_version 0x101c06cc fw_build_timestamp
>> > 2020-06-24 19:50 fw_build_id
>> > [ 25.450139] ath11k_pci 0000:55:00.0: failed to receive control response compl
>> > etion, polling..
>> > [ 26.474154] ath11k_pci 0000:55:00.0: Service connect timeout
>> > [ 26.474163] ath11k_pci 0000:55:00.0: failed to connect to HTT: -110
>> > [ 26.477247] ath11k_pci 0000:55:00.0: failed to start core: -110
>> > With the latest bringup and my patch to disable M2, I'm still booting
>> > and operating reliably.
>>
>> I took my bringup branch and merged 5.10-rc6 into it. It merges fine,
>> and seems to be stable as well.
>
> Nice find wink, I've been running your patch that disables the MHI M2
> state on my XPS 9310 for the past few hours and wifi appears to be
> running smoothly for the first time.
>
> The wifi symbol in the top right menu (GNOME 3 desktop on NixOS) does
> show a question mark for some reason, but otherwise everything appears
> quite stable so far.
>
> Perhaps its worth running git blame on `pm.c` and seeing if the
> original author of the MHI state machine might be able to shed some
> light (if they remember)? Would it be inappropriate to cc them into
> this thread? I'm unsure of mailing list etiquette here.

I started a new thread and included MHI developers, hopefully they have
more insight what could cause this.

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

  parent reply	other threads:[~2020-12-16  8:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 17:38 ath11k: QCA6390 on Dell XPS 13 and kernel crashes Mitchell Nordine
2020-12-06 17:53 ` wi nk
2020-12-06 21:45   ` wi nk
2020-12-07  1:17     ` wi nk
2020-12-07 14:45       ` Mitchell Nordine
2020-12-07 17:01         ` wi nk
2020-12-09  1:52           ` wi nk
2020-12-09  9:43             ` wi nk
2020-12-09 15:28               ` wi nk
2020-12-09 15:35     ` Kalle Valo
2020-12-09 15:39       ` wi nk
2020-12-09 15:50         ` wi nk
2020-12-09 15:50         ` Kalle Valo
2020-12-09 15:55           ` wi nk
2020-12-09 21:46             ` wi nk
2020-12-11 12:28               ` wi nk
2020-12-12  5:37                 ` Kalle Valo
2020-12-12 11:46                   ` wi nk
2020-12-12 23:29                     ` wi nk
2020-12-13  0:03                       ` wi nk
2020-12-13  0:59                         ` Mitchell Nordine
2020-12-13 22:09                           ` Stephen Liang
2020-12-16  8:50                           ` Kalle Valo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-02 23:49 Stephen Liang
2020-12-09 15:09 ` Kalle Valo
2020-12-10  3:07   ` Stephen Liang
2020-12-10  7:37     ` Stephen Liang
2020-11-30 16:55 Kalle Valo
2020-11-30 17:02 ` wi nk
2020-12-01 10:17   ` wi nk
2020-12-05 19:17     ` wi nk
2020-12-06  8:05       ` wi nk

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=87lfdyxhgr.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=cjhuang@codeaurora.org \
    --cc=mail@mitchellnordine.com \
    --cc=stephenliang7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.