From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Subject: Re: DEBUG_LOCKS_WARN_ON triggered by bcm43xx-SoftMAC
Date: Wed, 16 Aug 2006 18:06:10 +0200
Message-ID: <200608161806.10348.mb@bu3sch.de>
References: <44E296DD.3040803@lwfinger.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Return-path: <bcm43xx-dev-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>
To: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
In-Reply-To: <44E296DD.3040803-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Content-Disposition: inline
List-Unsubscribe: <https://lists.berlios.de/mailman/listinfo/bcm43xx-dev>,
	<mailto:bcm43xx-dev-request-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org?subject=unsubscribe>
List-Archive: <https://lists.berlios.de/pipermail/bcm43xx-dev>
List-Post: <mailto:bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>
List-Help: <mailto:bcm43xx-dev-request-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org?subject=help>
List-Subscribe: <https://lists.berlios.de/mailman/listinfo/bcm43xx-dev>,
	<mailto:bcm43xx-dev-request-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org?subject=subscribe>
Sender: bcm43xx-dev-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Errors-To: bcm43xx-dev-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
List-Id: netdev.vger.kernel.org

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?

-- 
Greetings Michael.