From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1751089AbWHPQHW@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751089AbWHPQHW (ORCPT <rfc822;willy@w.ods.org>);
	Wed, 16 Aug 2006 12:07:22 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751016AbWHPQHW
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 16 Aug 2006 12:07:22 -0400
Received: from static-ip-62-75-166-246.inaddr.intergenia.de ([62.75.166.246]:3716
	"EHLO bu3sch.de") by vger.kernel.org with ESMTP id S1750975AbWHPQHV
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 16 Aug 2006 12:07:21 -0400
From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: DEBUG_LOCKS_WARN_ON triggered by bcm43xx-SoftMAC
Date: Wed, 16 Aug 2006 18:06:10 +0200
User-Agent: KMail/1.9.1
References: <44E296DD.3040803@lwfinger.net>
In-Reply-To: <44E296DD.3040803@lwfinger.net>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
       linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608161806.10348.mb@bu3sch.de>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@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.