From: Arjan van de Ven <arjan@infradead.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
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 18:21:44 +0200 [thread overview]
Message-ID: <1155745304.3023.55.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200608161806.10348.mb@bu3sch.de>
On Wed, 2006-08-16 at 18:06 +0200, Michael Buesch wrote:
> On Wednesday 16 August 2006 05:54, Larry Finger wrote:
> > Using vanilla wireless-2.6 from Linville's tree as updated today, I
> > get a warning generated by the statement
> > if (DEBUG_LOCKS_WARN_ON(!irqs_disabled()))
> > in kernel.lockdep.c. This warning only occurs when my wireless
> > interface is inserted and bcm43xx-softmac is activated. For that
> > reason I have included the SoftMAC and bcm43xx messages.
> >
> > kernel: SoftMAC: sent association request!
> > kernel: SoftMAC: associated!
> > kernel: bcm43xx: set security called, .active_key = 0, .level = 2,
> > .enabled = 1, .encrypt = 1
> > kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1
> > kernel: BUG: warning at kernel/lockdep.c:1801/trace_hardirqs_on()
> > kernel: [<c0103da7>] show_trace_log_lvl+0x197/0x1c0
> > kernel: [<c01052db>] show_trace+0x1b/0x20
> > kernel: [<c0105306>] dump_stack+0x26/0x30
> > kernel: [<c013596f>] trace_hardirqs_on+0x17f/0x190
> > kernel: [<c0104a15>] do_general_protection+0xc5/0x230
> > kernel: [<c01034b1>] error_code+0x39/0x40
> > kernel: [<000038c7>] 0x38c7
> > kernel: [<c01052db>] show_trace+0x1b/0x20
> > kernel: [<c0105306>] dump_stack+0x26/0x30
> > kernel: [<c013596f>] trace_hardirqs_on+0x17f/0x190
> > kernel: [<c0104a15>] do_general_protection+0xc5/0x230
> > kernel: [<c01034b1>] error_code+0x39/0x40
> >
> > I'm at a loss here. Can anyone explain how to interpret this dump? I
> > think I see a general protection fault, but what to do from there is a
> > mystery.
>
> Hm, weird bug.
> I can't reproduce this on i386 or PPC.
> Could it be a bug in the lockdep code?
is there anything more in the trace???
next prev parent reply other threads:[~2006-08-16 16:21 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 ` Michael Buesch
2006-08-16 16:21 ` Arjan van de Ven [this message]
2006-08-16 16:47 ` Larry Finger
2006-08-16 16:26 ` Larry Finger
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=1155745304.3023.55.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=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
all inboxes | Powered by JetHome®