All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: wi nk <wink@technolu.st>
Cc: Stephen Liang <stephenliang7@gmail.com>,
	Jeffrey Hugo <jhugo@codeaurora.org>,
	Carl Huang <cjhuang@codeaurora.org>,
	Bhaumik Bhatt <bbhatt@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Hemant Kumar <hemantk@codeaurora.org>,
	ath11k@lists.infradead.org,
	Mitchell Nordine <mail@mitchellnordine.com>
Subject: Re: ath11k: crashes with 1 MSI vector, workaround disable MHI M2 state
Date: Mon, 21 Dec 2020 19:15:52 +0200	[thread overview]
Message-ID: <87zh27nkqf.fsf@codeaurora.org> (raw)
In-Reply-To: <CAHUdJJUmW8LZGGn+982gfYUyejiv8kvW9Ho=jXr=6WTW1W3uww@mail.gmail.com> (wi nk's message of "Sun, 20 Dec 2020 16:39:06 +0100")

wi nk <wink@technolu.st> writes:

> Another interesting note is that the laptop only seems to attempt the
> transition when it's plugged into the charger (see my mp4s for more
> info). If I boot the laptop on battery and bring up the adapter, it
> never attempts the transition beyond m0 either.

This is so weird to me, what could cause it?

If you boot the laptop on battery but after the boot connect it to the
charger, what does it do? I'm wondering f this is some boot state
problem/feature or does the behaviour change runtime.

-- 
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:[~2020-12-21 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16  8:47 ath11k: crashes with 1 MSI vector, workaround disable MHI M2 state Kalle Valo
2020-12-17  8:41 ` Kalle Valo
2020-12-17  9:53 ` Manivannan Sadhasivam
2020-12-17 19:01   ` Stephen Liang
2020-12-19 21:34   ` wi nk
2020-12-20 15:05     ` Manivannan Sadhasivam
2020-12-20 15:39       ` wi nk
2020-12-21 17:15         ` Kalle Valo [this message]
2020-12-21 17:26           ` 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=87zh27nkqf.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=bbhatt@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=cjhuang@codeaurora.org \
    --cc=hemantk@codeaurora.org \
    --cc=jhugo@codeaurora.org \
    --cc=mail@mitchellnordine.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --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.