From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Will Dyson <will.dyson@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] Please pull 'upstream' branch of rt2x00
Date: Tue, 5 Aug 2008 20:44:34 +0200 [thread overview]
Message-ID: <200808052044.34747.IvDoorn@gmail.com> (raw)
In-Reply-To: <1217959883.3603.50.camel@johannes.berg>
On Tuesday 05 August 2008, Johannes Berg wrote:
> On Tue, 2008-08-05 at 20:30 +0200, Ivo van Doorn wrote:
>
> > > > =============================================
> > > > [ INFO: possible recursive locking detected ]
> > > > 2.6.27-rc1-rt2-wl #1
> > > > ---------------------------------------------
> > > > rt61pci/4405 is trying to acquire lock:
> > > > (_xmit_IEEE80211#2){-...}, at: [<ffffffffa014cc52>]
> > > > ieee80211_scan_completed+0x172/0x320 [mac80211]
> > > >
> > > > but task is already holding lock:
> > > > (_xmit_IEEE80211#2){-...}, at: [<ffffffffa014cc52>]
> > > > ieee80211_scan_completed+0x172/0x320 [mac80211]
> > > >
> > >
> > > I get that same lockdep warning when using the mainline kernel with b43. It
> > > doesn't seem to cause any problems.
> >
> > Sounds like a mac80211 bug then, can't find something obvious at first glance,
> > but perhaps Johannes has an idea?
>
> I ignore everything with the TX lock in it because those have been
> wrongly annotated in a bunch of versions, including -rc1 afaik.
Heh ok. :)
Ivo
next prev parent reply other threads:[~2008-08-05 18:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 14:36 Please pull 'upstream' branch of rt2x00 Ivo van Doorn
2008-08-04 14:37 ` [PATCH 1/5] rt2x00: Implement HW encryption Ivo van Doorn
2008-08-04 14:38 ` [PATCH 2/5] rt2x00: Implement HW encryption (rt61pci) Ivo van Doorn
2008-08-04 14:38 ` [PATCH 3/5] rt2x00: Implement HW encryption (rt73usb) Ivo van Doorn
2008-08-04 14:38 ` [PATCH 4/5] rt2x00: Gather channel information in structure Ivo van Doorn
2008-08-04 14:39 ` [PATCH 5/5] rt2x00: Release rt2x00 2.2.0 Ivo van Doorn
2008-08-04 17:22 ` [PATCH 3/5] rt2x00: Implement HW encryption (rt73usb) Stefanik Gábor
2008-08-04 17:57 ` Ivo van Doorn
2008-08-05 1:21 ` [Rt2400-devel] Please pull 'upstream' branch of rt2x00 Will Dyson
2008-08-05 1:43 ` Larry Finger
2008-08-05 18:30 ` Ivo van Doorn
2008-08-05 18:11 ` Johannes Berg
2008-08-05 18:44 ` Ivo van Doorn [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-06 22:37 Ivo van Doorn
2008-01-10 11:52 ` [Rt2400-devel] " Will Dyson
2008-01-10 15:46 ` John W. Linville
2008-01-10 17:29 ` Ivo van Doorn
2008-01-15 0:44 ` Will Dyson
2008-01-10 17:29 ` Ivo van Doorn
2008-01-10 20:32 ` Stefan Lippers-Hollmann
2007-10-27 11:34 Ivo van Doorn
2007-10-27 12:47 ` [Rt2400-devel] " John W. Linville
2007-10-27 14:45 ` Ivo van Doorn
2007-10-27 16:19 ` Ivo van Doorn
2007-08-19 18:18 Ivo van Doorn
2007-08-23 20:55 ` [Rt2400-devel] " John W. Linville
2007-07-25 20:49 Ivo van Doorn
2007-07-26 2:19 ` [Rt2400-devel] " John W. Linville
2007-07-26 21:22 ` 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=200808052044.34747.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
--cc=will.dyson@gmail.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).