From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750707AbWF1SJQ (ORCPT ); Wed, 28 Jun 2006 14:09:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750717AbWF1SJQ (ORCPT ); Wed, 28 Jun 2006 14:09:16 -0400 Received: from py-out-1112.google.com ([64.233.166.182]:56144 "EHLO py-out-1112.google.com") by vger.kernel.org with ESMTP id S1750707AbWF1SJP (ORCPT ); Wed, 28 Jun 2006 14:09:15 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uI71Svk8gL75w289jupX798juX3qEe0oz14nJ2POeiI3Y2wIg3FjYT88V+H0ZuX/kM9bs4mAg5vt6n0EDMVDukHOeIvsi0Fm38thdUv5LrNgOI9S00E/zat+89ngXEWKDiK/mFpl14et7HV7pZpePH4pWBj6I4STyUVBTbVu0Oo= Message-ID: Date: Wed, 28 Jun 2006 11:09:14 -0700 From: "Miles Lane" To: "Ingo Molnar" Subject: Re: 2.6.17-mm3 -- BUG: trying to register non-static key! Cc: "Andrew Morton" , LKML In-Reply-To: <20060628153403.GA32131@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060628153403.GA32131@elte.hu> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org After rebuilding with your patch, the stack trace shows up, but now there is a warning of a possible circular locking dependency: [ INFO: possible circular locking dependency detected ] ------------------------------------------------------- S13gdm/2088 is trying to acquire lock: (&dev->queue_lock){-+..}, at: [] dev_queue_xmit+0x120/0x248 but task is already holding lock: (&dev->_xmit_lock){-+..}, at: [] dev_queue_xmit+0x183/0x248 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&dev->_xmit_lock){-+..}: [] lock_acquire+0x60/0x80 [] _spin_lock_bh+0x28/0x37 [] dev_activate+0xce/0x100 [] linkwatch_run_queue+0x10b/0x138 [] linkwatch_event+0x24/0x2b [] run_workqueue+0x86/0xcb [] worker_thread+0xe1/0x114 [] kthread+0xb0/0xdc [] kernel_thread_helper+0x5/0xb -> #0 (&dev->queue_lock){-+..}: [] lock_acquire+0x60/0x80 [] _spin_lock+0x23/0x32 [] dev_queue_xmit+0x120/0x248 [] hostap_data_start_xmit+0x610/0x61a [hostap] [] dev_hard_start_xmit+0x206/0x212 [] dev_queue_xmit+0x19f/0x248 [] mld_sendpack+0x1a0/0x24d [ipv6] [] mld_ifc_timer_expire+0x1b2/0x1d9 [ipv6] [] run_timer_softirq+0xf2/0x14a [] __do_softirq+0x55/0xb0 [] do_softirq+0x58/0xbd other info that might help us debug this: 1 lock held by S13gdm/2088: #0: (&dev->_xmit_lock){-+..}, at: [] dev_queue_xmit+0x183/0x248 stack backtrace: [] show_trace_log_lvl+0x54/0xfd [] show_trace+0xd/0x10 [] dump_stack+0x19/0x1b [] print_circular_bug_tail+0x59/0x64 [] __lock_acquire+0x7c9/0x95e [] lock_acquire+0x60/0x80 [] _spin_lock+0x23/0x32 [] dev_queue_xmit+0x120/0x248 [] hostap_data_start_xmit+0x610/0x61a [hostap] [] dev_hard_start_xmit+0x206/0x212 [] dev_queue_xmit+0x19f/0x248 [] mld_sendpack+0x1a0/0x24d [ipv6] [] mld_ifc_timer_expire+0x1b2/0x1d9 [ipv6] [] run_timer_softirq+0xf2/0x14a [] __do_softirq+0x55/0xb0 [] do_softirq+0x58/0xbd [] irq_exit+0x3f/0x4b [] do_IRQ+0xa0/0xaf [] common_interrupt+0x25/0x2c [drm] Initialized drm 1.0.1 20051102