From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: DEBUG_LOCKS_WARN_ON triggered by bcm43xx-SoftMAC
Date: Wed, 16 Aug 2006 11:26:42 -0500 [thread overview]
Message-ID: <44E34742.80302@lwfinger.net> (raw)
In-Reply-To: <200608161806.10348.mb@bu3sch.de>
Michael Buesch wrote:
>
> Hm, weird bug.
> I can't reproduce this on i386 or PPC.
> Could it be a bug in the lockdep code?
>
It could be. I'll send it on to LKML. Perhaps one of the experts
there can tell us. It doesn't seem to cause any trouble, but I get
one of these when bcm43xx starts.
Are you running WPA? The message seems to occur just after
wpa_supplicant finishes the connection and sets the security flags.
Larry
next prev parent reply other threads:[~2006-08-16 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44E296DD.3040803@lwfinger.net>
2006-08-16 16:06 ` DEBUG_LOCKS_WARN_ON triggered by bcm43xx-SoftMAC Michael Buesch
2006-08-16 16:21 ` Arjan van de Ven
2006-08-16 16:47 ` Larry Finger
2006-08-16 16:26 ` Larry Finger [this message]
2006-08-16 16:29 Larry Finger
2006-08-16 16:38 ` Arjan van de Ven
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=44E34742.80302@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox