Date: Thu, 22 May 2014 20:38:06 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Idwer Vollering <vidwer@gmail.com> Cc: freebsd-wireless@freebsd.org, freebsd-usb@freebsd.org Subject: Re: if_rsu hardware causes a kernel panic on removal.. Message-ID: <537E440E.5010208@selasky.org> In-Reply-To: <CAPp9OrkSHzwmMOhPXDo2Hab0_XgMpa1kQwMzOCimHMSzf8hbdw@mail.gmail.com> References: <CAPp9Or=6ryhXzLCE07xOKywwQLkJ7FQ-1w8ePru6p0Cfr0FcJQ@mail.gmail.com> <537AEC79.6080406@selasky.org> <CAPp9Ork4H=v%2BudbteJgjOCS9HeGUgMSCFdMOm84x8i0jr4%2BJ=w@mail.gmail.com> <537B497E.8070701@selasky.org> <CAPp9Or=yUXU2adQP5qppjwWJDJA3q-Ns%2BabRi=bRmwKtg9qaHw@mail.gmail.com> <537B6F44.6070905@selasky.org> <CAPp9Or=xuKzsa3zydfvfbjNxJh0m48q9RnHdg2YEnXAExQUhTQ@mail.gmail.com> <537B9D78.3030103@selasky.org> <CAPp9Ork1NUxMwZJyPGsN__X9p%2BMiwM4qxB7YMAZK1WzrTqJ07w@mail.gmail.com> <537C4712.908@selasky.org> <CAPp9Orks1MCdDW2J%2B5CWe6GX9qBujvEFzazffstmHZtO9_FA0g@mail.gmail.com> <537CC4CF.9030509@selasky.org> <537CE3C9.7090807@selasky.org> <CAPp9OrnAUU%2Bnm0e_0Uq9V=mPiC8y8zavQCCFsA5AYRCcEed%2BbA@mail.gmail.com> <537D9955.3070001@selasky.org> <CAPp9Orn4AttGuR93V8h-ErWALHpbGN0JzshK24mKYtUdYgYevw@mail.gmail.com> <537DE4DF.1060703@selasky.org> <CAPp9OrkSHzwmMOhPXDo2Hab0_XgMpa1kQwMzOCimHMSzf8hbdw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?537E440E.5010208>