All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org,
	Intel Linux Wireless <ilw@linux.intel.com>
Subject: Lots of trans->state != IWL_TRANS_FW_ALIVE warnings
Date: Mon, 15 Oct 2012 16:47:24 +0200	[thread overview]
Message-ID: <20121015144722.GA12560@redhat.com> (raw)

On Fedora (3.5 and 3.6 kernels) we are currently overwhelmed by
tons of iwlwifi warnings at iwlagn_mac_flush() and iwl_dvm_send_cmd()
reports.

iwlagn_mac_flush warning is triggered at:

static inline int iwl_trans_wait_tx_queue_empty(struct iwl_trans *trans)
{
        WARN_ONCE(trans->state != IWL_TRANS_FW_ALIVE,
                  "%s bad state = %d", __func__, trans->state);

        return trans->ops->wait_tx_queue_empty(trans);
}

We have 2 instances of this issue:

- started at ieee80211_scan()
https://bugzilla.redhat.com/show_bug.cgi?id=866013
- started at ieee80211_sta_monitor_work()
https://bugzilla.redhat.com/show_bug.cgi?id=861753

iwl_dvm_send_cmd is triggered at:

static inline int iwl_trans_send_cmd(struct iwl_trans *trans,
                                struct iwl_host_cmd *cmd)
{
        WARN_ONCE(trans->state != IWL_TRANS_FW_ALIVE,
                  "%s bad state = %d", __func__, trans->state);

        return trans->ops->send_cmd(trans, cmd);
}

And have 3 instances:

- started at ieee80211_set_disassoc()
https://bugzilla.redhat.com/show_bug.cgi?id=861599
- started at ieee80211_restart_work()
https://bugzilla.redhat.com/show_bug.cgi?id=865072
- started at ieee80211_auth()
https://bugzilla.redhat.com/show_bug.cgi?id=866015

Can those be fixed in some reasonable time ?

I'm not sure if they are related with some user visible problem like
disconnects.

I'll probably revert f0d120af8f55649571c681f49c920b0822050fa5
on Fedora, just to stop getting those warnings ...

Stanislaw


             reply	other threads:[~2012-10-15 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 14:47 Stanislaw Gruszka [this message]
2012-10-15 14:56 ` Lots of trans->state != IWL_TRANS_FW_ALIVE warnings Grumbach, Emmanuel
2012-10-15 15:14 ` Grumbach, Emmanuel
2012-10-15 15:23   ` Stanislaw Gruszka
2012-10-15 15:37     ` Stanislaw Gruszka
2012-10-15 18:53       ` Grumbach, Emmanuel
2012-10-17  6:58         ` Stanislaw Gruszka
2012-10-17  7:48           ` 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=20121015144722.GA12560@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --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.