linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: yuweizheng@139.com
Cc: linux-kernel@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
	linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
	linux@rempel-privat.de, netdev@vger.kernel.org,
	Yuwei Zheng <zhengyuwei@360.cn>
Subject: Re: [PATCH] Repair soft lockup with monitor mode of ath9k_htc card
Date: Fri, 30 Jan 2015 12:44:52 +0200	[thread overview]
Message-ID: <87d25wzgwr.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1422486872-16308-1-git-send-email-yuweizheng@139.com> (yuweizheng@139.com's message of "Thu, 29 Jan 2015 07:14:32 +0800")

yuweizheng@139.com writes:

> From: Yuwei Zheng <yuweizheng@139.com>
>
> In the environment with heavy wifi traffic, set the ar9271 into
> monitor mode, will trigger a deadloop panic.
>  
> The ath9k_hif_usb_rx_cb function excute on  the interrupt context, and ath9k_rx_tasklet excute
> on the soft irq context. In other words, the ath9k_hif_usb_rx_cb have more chance to excute than
> ath9k_rx_tasklet.  So in the worst condition,  the rx.rxbuf receive list is always full,
> and the do {}while(true) loop will not be break. The kernel get a soft lockup panic. 

Word wrapping is too long and please prefix the title with "ath9k_htc: ".

-- 
Kalle Valo

  reply	other threads:[~2015-01-30 10:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 23:14 [PATCH] Repair soft lockup with monitor mode of ath9k_htc card yuweizheng
2015-01-30 10:44 ` Kalle Valo [this message]
2015-01-30 10:55 ` Oleksij Rempel
2015-01-29  0:18   ` Yuwei Zheng
2015-01-29  4:09 zhengyuwei

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=87d25wzgwr.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=netdev@vger.kernel.org \
    --cc=yuweizheng@139.com \
    --cc=zhengyuwei@360.cn \
    /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).