From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] iwlwifi: jiffies based tx queues watchdog
Date: Thu, 2 Dec 2010 17:31:17 +0100 [thread overview]
Message-ID: <20101202163116.GA11331@redhat.com> (raw)
In-Reply-To: <1288192267.12056.75.camel@wwguy-huron>
Hi Wey
On Wed, Oct 27, 2010 at 08:11:07AM -0700, Guy, Wey-Yi wrote:
> > This patch replace monitor/recover timer by watchdog based on time
> > stamp. New code allow to discover hangs more precisely.
> >
> > Timeout values are currently doubled monitoring period values of
> > previous timer. This have to be tuned based of firmware timing
> > capabilities.
> >
> > Code was not widely tested jet.
>
> > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > ---
>
> Thanks for the RFC, I will have people here test this patch with the
> latest devices still under development. At the meantime, could you also
> do some testing on your side with the devices you have since we can not
> cover all the older devices already out there.
I finally get some time to test this patch. I found two issues.
First problem is oops on 3945, when I set wd_timeout to 10 ms.
Frequent resets show a bug when ieee80211_reconfig do call to
iwl_send_add_sta, and in parallel, restart code do
iwl3945_down()->iwl3945_hw_txq_ctx_stop() and free txq that
iwl_send_add_sta() want to use. This need some better fix
and careful review, but adding
/* initialize force reset */
priv->force_reset[IWL_RF_RESET].reset_duration =
IWL_DELAY_NEXT_FORCE_RF_RESET;
priv->force_reset[IWL_FW_RESET].reset_duration =
IWL_DELAY_NEXT_FORCE_FW_RELOAD;
to iwl3945_init_drv to prevent too frequent reset make bug gone.
Second problem I saw, was also when watchdag want to do frequent
resets. When reset was not actually performed, because of above
reset duration limit, watchdog stays disabled. Keep watchdog
running when iwl_force_reset() return error fix that problem.
In general watchdog do the job. I will official patch shortly.
Stanislaw
next prev parent reply other threads:[~2010-12-02 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 14:55 [RFC] iwlwifi: jiffies based tx queues watchdog Stanislaw Gruszka
2010-10-27 15:11 ` Guy, Wey-Yi
2010-12-02 16:31 ` Stanislaw Gruszka [this message]
2010-12-02 16:31 ` Guy, Wey-Yi
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=20101202163116.GA11331@redhat.com \
--to=sgruszka@redhat.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.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 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).