From owner-freebsd-usb@FreeBSD.ORG  Thu May 22 11:51:17 2014
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@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 8DC0155C;
 Thu, 22 May 2014 11:51:17 +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 4398E2993;
 Thu, 22 May 2014 11:51:16 +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 307D51FE026;
 Thu, 22 May 2014 13:51:16 +0200 (CEST)
Message-ID: <537DE4DF.1060703@selasky.org>
Date: Thu, 22 May 2014 13:51:59 +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>	<537C4712.908@selasky.org>	<CAPp9Orks1MCdDW2J+5CWe6GX9qBujvEFzazffstmHZtO9_FA0g@mail.gmail.com>	<537CC4CF.9030509@selasky.org>	<537CE3C9.7090807@selasky.org>	<CAPp9OrnAUU+nm0e_0Uq9V=mPiC8y8zavQCCFsA5AYRCcEed+bA@mail.gmail.com>	<537D9955.3070001@selasky.org>
 <CAPp9Orn4AttGuR93V8h-ErWALHpbGN0JzshK24mKYtUdYgYevw@mail.gmail.com>
In-Reply-To: <CAPp9Orn4AttGuR93V8h-ErWALHpbGN0JzshK24mKYtUdYgYevw@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-usb@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 11:51:17 -0000

On 05/22/14 13:22, Idwer Vollering wrote:
> rsu0: timeout waiting for EMEM transfer

Does this patch make any difference:

=== ./if_rsu.c
==================================================================
--- ./if_rsu.c	(revision 266539)
+++ ./if_rsu.c	(local)
@@ -2220,13 +2220,13 @@
  		goto fail;
  	}
  	/* Wait for load to complete. */
-	for (ntries = 0; ntries != 10; ntries++) {
+	for (ntries = 0; ntries != 50; ntries++) {
  		usb_pause_mtx(&sc->sc_mtx, hz / 100);
  		reg = rsu_read_2(sc, R92S_TCR);
  		if (reg & R92S_TCR_EMEM_CODE_DONE)
  			break;
  	}
-	if (ntries == 10) {
+	if (ntries == 50) {
  		device_printf(sc->sc_dev, "timeout waiting for EMEM transfer\n");
  		error = ETIMEDOUT;
  		goto fail;