From: Kalle Valo <kvalo@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Cool Goose <coolgoose54@yahoo.in>,
Linux ath10k <ath10k@lists.infradead.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: Atheros QCA6174 ath10k_pci fimware crashing
Date: Mon, 25 Sep 2023 13:08:02 +0300 [thread overview]
Message-ID: <87a5taa7lp.fsf@kernel.org> (raw)
In-Reply-To: <ZQ4vQNe3XsArwWQT@debian.me> (Bagas Sanjaya's message of "Sat, 23 Sep 2023 07:20:16 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
>> Sep 19 09:01:11 hostname kernel: ath10k_warn: 149 callbacks suppressed
>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110
>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110
>> Sep 19 09:01:11 hostname kernel: ath10k_pci 0000:03:00.0: failed to wake target for read32 at 0x00036044: -110
>>
>
> Looks like hardware issue, right?
It could be a hardware issue (for example a problem with the PCI bus
communication) but also simply a firmware crash. These kind of reports
come time to time but root cause is unknown.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2023-09-25 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1209906123.2716993.1695416371605.ref@mail.yahoo.com>
2023-09-22 20:59 ` Atheros QCA6174 ath10k_pci fimware crashing Cool Goose
2023-09-23 0:20 ` Bagas Sanjaya
2023-09-25 10:08 ` Kalle Valo [this message]
2023-09-25 10:15 ` Bagas Sanjaya
2023-09-25 10:15 ` Bagas Sanjaya
2023-09-25 16:14 ` Cool Goose
2023-09-25 16:14 ` Cool Goose
2023-10-30 14:38 ` Cool Goose
2023-10-30 14:38 ` Cool Goose
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=87a5taa7lp.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=bagasdotme@gmail.com \
--cc=coolgoose54@yahoo.in \
--cc=quic_jjohnson@quicinc.com \
/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.