linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: mac80211 deadlock detection triggering with rt61pci
Date: Sat, 19 Jul 2008 16:47:13 +0200	[thread overview]
Message-ID: <200807191647.13517.IvDoorn@gmail.com> (raw)
In-Reply-To: <200807182120.47252.IvDoorn@gmail.com>

On Friday 18 July 2008, Ivo van Doorn wrote:
> Hi,
> 
> > I'm not sure whether this still happens in current versions or not, but
> > kerneloops is reporting a number of mac80211 warnings due to the TX
> > deadlock detection:
> > http://www.kerneloops.org/searchweek.php?search=ieee80211_master_start_xmit
> > 
> > The rt2x00 mac code seems fine, did it change recently which could
> > explain this warning triggering?
> 
> Interesting, the TX code did change for 2.6.27 recently with the DMA changes
> by GertJan, I think the Fedora kernels which are showing the above panics already
> contain those patches,
> 
> John, Does Fedora kernel 2.6.25.10-86.fc9.x86_64 contain rt2x00 2.1.8?
> 
> I also have some reports about a queue corruption in rt61pci and although I haven't
> figured out how that corruption is caused, I do think the above panics might somehow
> be related.

It might be me, but looking at those traces, aren't they triggered by:

static int ieee80211_tx(struct net_device *dev, struct sk_buff *skb)
{
...
		if (WARN_ON(queue >= ieee80211_num_regular_queues(&local->hw)))
			goto drop;
...
}

Which would suggest that when MAC80211_QOS is disabled, the skb_queue_mapping
still returns something higher then 1.

Ivo

  reply	other threads:[~2008-07-19 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  8:36 mac80211 deadlock detection triggering with rt61pci Johannes Berg
2008-07-18 19:20 ` Ivo van Doorn
2008-07-19 14:47   ` Ivo van Doorn [this message]
2008-07-19 17:42     ` Johannes Berg
2008-07-21 13:05       ` Ivo van Doorn

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=200807191647.13517.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).