From: Ben Greear <greearb@candelatech.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k: wmi service ready event not received
Date: Fri, 10 May 2019 06:54:11 -0700 [thread overview]
Message-ID: <6e530d73-91e9-faaf-31d0-cd5fadc66ffc@candelatech.com> (raw)
In-Reply-To: <CAHk-=wim_asb1MRpis39SDghBNN5SpKDvUvF6cTtwa9w8cS8_Q@mail.gmail.com>
On 05/10/2019 05:28 AM, Linus Torvalds wrote:
> Hmm.
>
> I have a nice new laptop, and it works fine. Except today it lost
> wireless, and I have no idea why.
>
> It's not happened before (but it's fairly new and I'm actually on my
> first trip with it), so I don't know how common this is, but the
> kernel messages seem to say that the cause of it was
>
> ath10k_pci 0000:02:00.0: wmi service ready event not received
> ath10k_pci 0000:02:00.0: could not init core (-110)
> ath10k_pci 0000:02:00.0: could not probe fw (-110)
>
> and then nothing works. -110 is ETIMEDOUT, fwiw.
>
> Rebooting got wireless back. It's possible I could have done something
> less drastic, but I was thinking that it would be the new kernel and
> rebooted into an older version. But then rebooting into the new one
> afterwards (double-checking before starting a bisect) and it all
> worked.
>
> Is there anything I can do to debug this if it happens again?
Please provide 'lspci' or other info on the NIC chipset, for reference.
Sometimes a work-around is:
rmmod ath10k_pci ath10k_core; modprobe ath10k_pci
Sometimes you will get a firmware register dump in this crash case, and then someone
from QCA might can get a backtrace if you post that with the chipset info and
such (or if it is one of the NICs my ath10k-ct firmware supports and you can reproduce
an issue with that firmware, then I can debug it).
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-05-10 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 12:28 ath10k: wmi service ready event not received Linus Torvalds
2019-05-10 12:47 ` Adrian Chadd
2019-05-10 13:54 ` Ben Greear [this message]
2019-05-10 14:25 ` Kalle Valo
2019-05-10 14:44 ` Linus Torvalds
2019-05-14 8:26 ` 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=6e530d73-91e9-faaf-31d0-cd5fadc66ffc@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=torvalds@linux-foundation.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