From: Kalle Valo <kvalo@adurom.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH] iwlwifi: pcie: don't panic on host commands in iwldvm
Date: Thu, 23 Jan 2014 17:46:26 +0200 [thread overview]
Message-ID: <87fvoen1kd.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1390214977-29202-1-git-send-email-egrumbach@gmail.com> (Emmanuel Grumbach's message of "Mon, 20 Jan 2014 12:49:36 +0200")
Emmanuel Grumbach <egrumbach@gmail.com> writes:
> From: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
>
> None of the devices supported by iwldvm have support for
> shadow registers. This means that we wake the NIC
> when we increment the write pointer on Tx ring.
> This happened even before my bad commit mentionned below.
> Since my commit below, we wake up the NIC when we put a
> host command on the ring regardless of shadow register
> support. This means that in iwldvm (when the NIC doesn't
> support shadow register), we wake up the NIC twice:
>
> pcie_enqueue_hcmd:
> wake up the NIC
> iwl_pcie_txq_inc_wr_ptr:
> wake up the NIC - no shadow reg support
>
> Since waking up the NIC means that we need to acquire a
> spinlock, this obviously leads to a recursive spinlock
> and hence a freeze.
>
> Fixes: b9439491055a ("iwlwifi: pcie: keep the NIC awake when commands are in flight")
> Reported-by: Janusz Dziedzic <janusz.dziedzic@gmail.com>
> Reviewed-by: Johannes Berg <johannes.berg@intel.com>
> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Ah, this is why my laptop was hanging during boot with latest
wireless-testing? Thanks for fixing this.
FWIW:
Tested-by: Kalle Valo <kvalo@adurom.com>
--
Kalle Valo
next prev parent reply other threads:[~2014-01-23 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 10:46 pull request: iwlwifi-next 2014-1-20 Emmanuel Grumbach
2014-01-20 10:49 ` [PATCH] iwlwifi: pcie: don't panic on host commands in iwldvm Emmanuel Grumbach
2014-01-23 15:46 ` Kalle Valo [this message]
2014-01-23 19:01 ` pull request: iwlwifi-next 2014-1-20 John W. Linville
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=87fvoen1kd.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=egrumbach@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--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 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.