From owner-freebsd-current@FreeBSD.ORG  Sun May 18 20:51:21 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C0620501;
 Sun, 18 May 2014 20:51:21 +0000 (UTC)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7FC7D2A81;
 Sun, 18 May 2014 20:51:21 +0000 (UTC)
Received: from laptop015.home.selasky.org
 (cm-176.74.213.204.customer.telag.net [176.74.213.204])
 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id BC9B51FE029;
 Sun, 18 May 2014 22:51:19 +0200 (CEST)
Message-ID: <53791D78.3070305@selasky.org>
Date: Sun, 18 May 2014 22:52:08 +0200
From: Hans Petter Selasky <hps@selasky.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: John Baldwin <jhb@FreeBSD.org>, 
 freebsd-current <freebsd-current@freebsd.org>
Subject: Re: panic: resource_list_add: resource entry is busy
References: <53763B0F.4040003@selasky.org> <5377529C.3000508@FreeBSD.org>
In-Reply-To: <5377529C.3000508@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 May 2014 20:51:21 -0000

On 05/17/14 14:14, John Baldwin wrote:
> On 5/16/14, 12:21 PM, Hans Petter Selasky wrote:
>> Hi,
>>
>> I see the following panic:
>>
>> panic: resource_list_add: resource entry is busy
>>
>> When trying to kldload an older pccard driver. The call comes from the
>> driver_added bus method somewhere down the tree. Loading the module
>> before the kernel boots fixes the problem temporarily.
>>
>> Any bells ringing or patch suggestions?
>>
>> Seeing this on 9-stable, also believed that the same issue exists with
>> 10-current.
>
> Something is doing a duplicate resource_list_add() for the same RID.
> The trace will tell you where the second resource_list_add() is
> occurring.  Some tracing should let you see where the first one occurs.
>

Hi,

Here is the backtrace. Is this information sufficient to debug further:

KDB: stack backtrace:
#0 0xffffffff8089e5d6 at kdb_backtrace+0x66
#1 0xffffffff808960f7 at resource_list_add+0x57
#2 0xffffffff805ea939 at pccard_function_init+0x279
#3 0xffffffff805ebede at pccard_probe_and_attach_child+0x7e
#4 0xffffffff805ec6ce at pccard_driver_added+0x5e
#5 0xffffffff808951b5 at devclass_driver_added+0x75
#6 0xffffffff80895cf3 at devclass_add_driver+0x103
#7 0xffffffff8084f1e8 at module_register_init+0xa8
#8 0xffffffff80846cde at linker_load_module+0x85e
#9 0xffffffff808473f4 at kern_kldload+0xb4
#10 0xffffffff80847504 at sys_kldload+0x84
#11 0xffffffff80c4a48a at amd64_syscall+0x5ea
#12 0xffffffff80c34b27 at Xfast_syscall+0xf7

--HPS