From owner-freebsd-wireless@FreeBSD.ORG  Wed May 21 06:25:41 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9B8E7E87;
 Wed, 21 May 2014 06:25:41 +0000 (UTC)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (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 59FE22F4F;
 Wed, 21 May 2014 06:25:41 +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 293621FE026;
 Wed, 21 May 2014 08:25:39 +0200 (CEST)
Message-ID: <537C4712.908@selasky.org>
Date: Wed, 21 May 2014 08:26:26 +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: Idwer Vollering <vidwer@gmail.com>
Subject: Re: if_rsu hardware causes a kernel panic on removal..
References: <CAPp9Or=6ryhXzLCE07xOKywwQLkJ7FQ-1w8ePru6p0Cfr0FcJQ@mail.gmail.com>	<537AEC79.6080406@selasky.org>	<CAPp9Ork4H=v+udbteJgjOCS9HeGUgMSCFdMOm84x8i0jr4+J=w@mail.gmail.com>	<537B497E.8070701@selasky.org>	<CAPp9Or=yUXU2adQP5qppjwWJDJA3q-Ns+abRi=bRmwKtg9qaHw@mail.gmail.com>	<537B6F44.6070905@selasky.org>	<CAPp9Or=xuKzsa3zydfvfbjNxJh0m48q9RnHdg2YEnXAExQUhTQ@mail.gmail.com>	<537B9D78.3030103@selasky.org>
 <CAPp9Ork1NUxMwZJyPGsN__X9p+MiwM4qxB7YMAZK1WzrTqJ07w@mail.gmail.com>
In-Reply-To: <CAPp9Ork1NUxMwZJyPGsN__X9p+MiwM4qxB7YMAZK1WzrTqJ07w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 May 2014 06:25:41 -0000

On 05/21/14 00:16, Idwer Vollering wrote:
> 2014-05-20 20:22 GMT+02:00 Hans Petter Selasky <hps@selasky.org>:
>>> Hi,
>>>
>>> Certainly, here it is:
>>>
>>> http://ra.openbios.org/~idwer/freebsd/core.txt.9_fbsd_10-stable_rsu-panic-on-insertion
>>>
>>> Idwer
>>>
>>
>> Does the attached patch make any difference?
>>
>> --HPS
>
> Yes, it seems to improve the situation.
> Apparently putting "wlandebug_wlan2=0x40000000" in /etc/rc.conf and
> compiling+booting with rsu_debug=5 triggers the panic.
>
> A verbose boot, so that debug.boothowto=2048 and debug.bootverbose=1,
> doesn't seem to influence behaviour.
>

Hi,

Can you SVN up to:

http://svnweb.freebsd.org/changeset/base/266484

at least, and compile a new kernel and modules without any additional 
patches.

Then send backtrace of any new panics.

--HPS