linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Greg Dietsche <Gregory.Dietsche@cuw.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: iwl4965: "MAC is in deep sleep!" freezes
Date: Fri, 2 Sep 2011 18:38:06 -0500	[thread overview]
Message-ID: <20110902233806.GA22157@elie> (raw)
In-Reply-To: <bbdbd01d4965ae789384bc1f9d0a2426@imap.dd24.net>

Hi,

Christoph Anton Mitterer wrote[1]:

> When I bring the WLAN interface up, after some time (usually just
> minutes) I get the following error (during which the system
> completely freezes for some 10-20s)
[...]
> kernel: [  951.087153] iwl4965 0000:14:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
> wpa_supplicant[13032]: Failed to initiate AP scan.
> kernel: [  952.089208] ------------[ cut here ]------------
> kernel: [  952.090089] WARNING: at drivers/net/wireless/iwlegacy/iwl-tx.c:483 iwl_legacy_enqueue_hcmd+0x3c7/0x3f0()

The warning is from v3.0-rc2~7^2~16^2~216 (iwlegacy: fix enqueue hcmd
race conditions, 2011-04-28):

| -	spin_lock_irqsave(&priv->hcmd_lock, flags);
| -
| -	/* If this is a huge cmd, mark the huge flag also on the meta.flags
| -	 * of the _original_ cmd. This is used for DMA mapping clean up.
| -	 */
| -	if (cmd->flags & CMD_SIZE_HUGE) {
| -		idx = iwl_legacy_get_cmd_index(q, q->write_ptr, 0);
| -		txq->meta[idx].flags = CMD_SIZE_HUGE;
| -	}
| -
| 	idx = iwl_legacy_get_cmd_index(q, q->write_ptr, cmd->flags & CMD_SIZE_HUGE);
| 	out_cmd = txq->cmd[idx];
| 	out_meta = &txq->meta[idx];
|  
| +	if (WARN_ON(out_meta->flags & CMD_MAPPED)) {
| +		spin_unlock_irqrestore(&priv->hcmd_lock, flags);
| +		return -ENOSPC;
| +	}
| +

More details are at [1].  Stanislav, thoughts?  Is this a bug, and if
so, any ideas for tracking it down?

Thanks,
Jonathan

[1] http://bugs.debian.org/636355

       reply	other threads:[~2011-09-02 23:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bbdbd01d4965ae789384bc1f9d0a2426@imap.dd24.net>
2011-09-02 23:38 ` Jonathan Nieder [this message]
2011-09-03 12:45   ` iwl4965: "MAC is in deep sleep!" freezes Christoph Anton Mitterer
2011-09-05  9:24     ` Stanislaw Gruszka
2011-09-05  9:19   ` Stanislaw Gruszka
2011-09-05  9:42     ` Christoph Anton Mitterer
2011-09-08  8:49       ` Stanislaw Gruszka
2011-09-08 16:19         ` Stanislaw Gruszka
2011-09-24 16:50           ` Stanislaw Gruszka
2011-11-14  0:02         ` Christoph Anton Mitterer
2011-11-14  1:46           ` Jonathan Nieder
2011-11-16 18:08             ` Christoph Anton Mitterer
2011-11-18  7:45               ` Stanislaw Gruszka
2011-12-29 15:17                 ` Christoph Anton Mitterer
2011-12-29 20:11                   ` Jonathan Nieder
2012-01-03 10:51                     ` Stanislaw Gruszka
2012-01-04  1:22                       ` Christoph Anton Mitterer
2012-01-05 10:14                         ` Stanislaw Gruszka
2012-01-16 22:08                           ` Christoph Anton Mitterer

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=20110902233806.GA22157@elie \
    --to=jrnieder@gmail.com \
    --cc=Gregory.Dietsche@cuw.edu \
    --cc=calestyo@scientia.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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;
as well as URLs for NNTP newsgroup(s).