From owner-freebsd-usb@FreeBSD.ORG Thu May 22 18:37:30 2014 Return-Path: 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 BFE56A40; Thu, 22 May 2014 18:37:30 +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 742992E88; Thu, 22 May 2014 18:37:30 +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 C28B41FE026; Thu, 22 May 2014 20:37:22 +0200 (CEST) Message-ID: <537E440E.5010208@selasky.org> Date: Thu, 22 May 2014 20:38:06 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Idwer Vollering Subject: Re: if_rsu hardware causes a kernel panic on removal.. References: <537AEC79.6080406@selasky.org> <537B497E.8070701@selasky.org> <537B6F44.6070905@selasky.org> <537B9D78.3030103@selasky.org> <537C4712.908@selasky.org> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <537D9955.3070001@selasky.org> <537DE4DF.1060703@selasky.org> In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2014 18:37:30 -0000 On 05/22/14 20:34, Idwer Vollering wrote: > Hi, > > This patch again improves its stability, but the interface keeps flapping: > > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=20, > val=0, arg_len=7]: Device not configured > May 22 20:29:03 machete last message repeated 3 times > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=25, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, > val=208, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=95, > val=208, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=17, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=26, > val=0, arg_len=0]: Device not configured > May 22 20:29:03 machete wpa_supplicant[2211]: ioctl[SIOCS80211, op=16, > val=1, arg_len=0]: Device not configured > > May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument > wlan2: link state changed to UP > wlan2: link state changed to DOWN > wlan2: link state changed to UP > wlan2: link state changed to DOWN > May 22 20:30:27 machete dhclient[2734]: send_packet: Invalid argument > wlan2: link state changed to UP > May 22 20:30:36 machete dhclient[2734]: send_packet: No buffer space available > wlan2: link state changed to DOWN > wlan2: link state changed to UP > May 22 20:31:03 machete dhclient[2734]: send_packet: No buffer space available > Hi, I guess you need to enable rsu debugging to figure out why the hardware reports link loss. --HPS