From: Wen Gong <wgong@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: [RFC] ath10k: change to do napi_enable and napi_disable when insmod and rmmod for sdio
Date: Mon, 24 Aug 2020 12:35:25 +0800 [thread overview]
Message-ID: <6b59e4db2c5ae9deb4959acd52108fb6@codeaurora.org> (raw)
In-Reply-To: <f58ad98479e54a5bbe8b6561563d8cc7@codeaurora.org>
On 2020-08-21 10:45, Wen Gong wrote:
...
> I have 2 cmd, each one can reproduce the hang.
> echo soft >
> /sys/kernel/debug/ieee80211/phy0/ath10k/simulate_fw_crash;sleep
> 0.05;ifconfig wlan0 down
> echo soft >
> /sys/kernel/debug/ieee80211/phy0/ath10k/simulate_fw_crash;rmmod
> ath10k_sdio
> and with the my patch, it fix the hang. Change of my patch is similar
> with your
> patch(https://patchwork.kernel.org/patch/10249365/), so it should also
> fix the hang with your patch.
I have sent v2: https://patchwork.kernel.org/patch/11732165/
next prev parent reply other threads:[~2020-08-24 4:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 3:55 [RFC] ath10k: change to do napi_enable and napi_disable when insmod and rmmod for sdio Wen Gong
2020-08-20 8:32 ` Kalle Valo
2020-08-20 9:19 ` Krishna Chaitanya
2020-08-20 9:26 ` Krishna Chaitanya
2020-08-20 10:20 ` Wen Gong
2020-08-20 10:14 ` Wen Gong
2020-08-20 10:52 ` Krishna Chaitanya
2020-08-20 14:37 ` Wen Gong
2020-08-20 16:08 ` Krishna Chaitanya
2020-08-20 16:32 ` Ben Greear
2020-08-20 17:00 ` Krishna Chaitanya
2020-08-20 17:07 ` Ben Greear
2020-08-20 17:41 ` Krishna Chaitanya
2020-08-20 17:42 ` Krishna Chaitanya
2020-08-20 17:53 ` Ben Greear
2020-08-20 20:15 ` Krishna Chaitanya
2020-08-20 20:59 ` Ben Greear
2020-08-21 2:45 ` Wen Gong
2020-08-24 4:35 ` Wen Gong [this message]
2020-09-07 16:07 ` Kalle Valo
2020-09-07 17:18 ` Ben Greear
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=6b59e4db2c5ae9deb4959acd52108fb6@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--cc=greearb@candelatech.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.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).