From: Luca Coelho <luca@coelho.fi>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: ilw@linux.intel.com, linux-wireless@vger.kernel.org
Subject: Re: iwlwifi micorcode errors and hardware resets problems
Date: Sat, 24 Aug 2013 14:52:57 +0300 [thread overview]
Message-ID: <1377345177.5589.3.camel@porter.coelho.fi> (raw)
In-Reply-To: <20130823090821.GB2632@redhat.com>
On Fri, 2013-08-23 at 11:08 +0200, Stanislaw Gruszka wrote:
> We have those bug reports on RH bugzilla, and various other iwlwifi
> problems, but those have some common scenario:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=979873
> https://bugzilla.redhat.com/show_bug.cgi?id=990536
> https://bugzilla.redhat.com/show_bug.cgi?id=994322
> https://bugzilla.redhat.com/show_bug.cgi?id=996502
> https://bugzilla.redhat.com/show_bug.cgi?id=969610
> https://bugzilla.redhat.com/show_bug.cgi?id=999053
>
> First there is Microcode error or other firmware problem, what make we
> do iwl_trans_stop_device() which set trans->state to IWL_TRANS_NO_FW.
> If mac80211 has some pending works/timers i.e. ieee80211_sta_work(),
> it calls drv and we trigger on of those warnings
>
> WARN_ONCE(trans->state != IWL_TRANS_FW_ALIVE,
> "%s bad state = %d", __func__, trans->state);
>
> on some trans operation.
>
> I think this can be fixed by first do quiesce on mac80211 (for example
> by ieee80211_sta_quiesce() procedure, which I removed but can be added
> back) and then do iwlagn_prepare_restart() & ieee80211_restart_hw().
>
> Though I'm not sure if it's worth to do this since those warnings are
> indicator for malfunctioning iwlwifi firmware (or driver not correctly
> communicating with firmware), which will be unnoticed if not reported
> automatically by tool like ABRT. But perhaps we could add WARN_ONCE on
> Microcode error condition ?
I think that, if the quiesce really helps with this, we should do it.
This WARN is a side-effect of the problem and not the problem itself.
If you want to catch the FW problem, there should be a WARN elsewhere.
I'm not saying that this WARN should be removed and I also think it's a
good idea to change it to WARN_ON_ONCE(). I just think that, if there's
anything the driver can do to keep things running nicely, we should do
it.
In any case, I'll leave this for Johannes, Emmanuel or some of the other
guys with more experience in iwlwifi to comment. ;)
--
Cheers,
Luca.
next prev parent reply other threads:[~2013-08-24 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 9:08 iwlwifi micorcode errors and hardware resets problems Stanislaw Gruszka
2013-08-24 11:52 ` Luca Coelho [this message]
2013-08-25 8:21 ` [Ilw] " Grumbach, Emmanuel
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=1377345177.5589.3.camel@porter.coelho.fi \
--to=luca@coelho.fi \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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