From owner-freebsd-usb@freebsd.org Tue Aug 30 19:22:10 2016 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66157BC9E15; Tue, 30 Aug 2016 19:22:10 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2863ED8B; Tue, 30 Aug 2016 19:22:08 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id b199so21150450lfe.0; Tue, 30 Aug 2016 12:22:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=IN65yKxXs0nJm7JEwVYD7rNoRto1ArrGQvSZADVyPHk=; b=fiTgsyGLQ4mMu+GbrYdbZkhDFt9yx7SLxq+7WGLcNyASF+v1sW6f9ou2AcXASwyRmh ZuPpVZq/NmliQhi5UslJCQ2ABa08IOLYB+SOhj+ZuFHC54R1sO0HZBffh06kn+Pzbeqz BvUnBAoWrkjCV6TgGW3d3Ddy6lhuLiXoUZNBGBNvAO2PndNJLuG5zUfVNBcEUGNDk53V DFUq5RWTPYlpD8n+wLvjy+9tYmRZgKLlFIgJ/u0DUpF4Aj6SKidLNMSQlhd+gFnZiPzQ Vm8MH26PSQo3+P3aZTib9B1kN7C2b3yq+k4Wugg6qmgFRcU6/9lhq64e6K8qfdtHu94u Pc/g== X-Gm-Message-State: AE9vXwNUg/7Bhz+dtiQ42wHev7aoEx17JtXLlHryigU+pCc15U5f9MpLqEkXD+1ELPrxcw== X-Received: by 10.25.125.4 with SMTP id y4mr1513195lfc.75.1472584920599; Tue, 30 Aug 2016 12:22:00 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id 83sm7787855ljj.14.2016.08.30.12.21.59 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 30 Aug 2016 12:22:00 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-wireless@freebsd.org, =?utf-8?Q?Otac=C3=ADlio?= Subject: Re: urtwn instable on Beaglebone Black References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> Date: Tue, 30 Aug 2016 22:21:44 +0300 Cc: "freebsd-arm@freebsd.org" , freebsd-usb@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 19:22:10 -0000 Tue, 30 Aug 2016 21:33:28 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Otac=C3=ADlio = : I have no ideas here (it works (mostly) fine on x86 and I have no = possibility to check it with ARM). P.S. Other (ARM-specific?) issues: https://lists.freebsd.org/pipermail/freebsd-arm/2016-July/014382.html https://forums.freebsd.org/threads/57396 > Dears > > I'm using a beaglebone black to stream video over UDP. I wrote a = > software and have tested it using a urtwn device + webcam Logitech C92= 0. = > All is connected using a USB hub with external power source. So urtwn = = > and webcam, both are plugged in the same USB hub. When I plug the hub = = > and run my software on a old notebook intel centrino with FreeBSD = > 11.0-RC2 AMD64 all works fine. Last night the system stream video all = = > night. But, when I replace the notebook by beaglebone black running = > FreeBSD 11.0-RC1 with the same USB HUB, the same wrtwn device and same= = > camera, randomly after some time the beaglebone black network shutdown= = > and terminal shows this messages : > > > Network is down > % urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > urtwn0: ieee80211_crypto_encap returns NULL. > > Then, I need to run > > /etc/rc.d/netif stop > > /etc/rc.d/netif start > > To enable network again. So, someone can give me a hit about what can = be = > this and how to fix? > > Thanks a lot > > []'s > > -Otacilio > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org"