From owner-freebsd-wireless@freebsd.org Sun Aug 28 10:26:46 2016 Return-Path: Delivered-To: freebsd-wireless@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 EAF4EB78008 for ; Sun, 28 Aug 2016 10:26:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DAA32D25 for ; Sun, 28 Aug 2016 10:26:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7SAQkb2094526 for ; Sun, 28 Aug 2016 10:26:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 211885] if_iwm firmware crashes and recovers Date: Sun, 28 Aug 2016 10:26:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ish@amail.plala.or.jp X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 10:26:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211885 --- Comment #6 from Masachika ISHIZUKA --- Created attachment 174153 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D174153&action= =3Dedit /var/log/messages It remains panic. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Aug 28 21:00:35 2016 Return-Path: Delivered-To: freebsd-wireless@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 672E5BC1955 for ; Sun, 28 Aug 2016 21:00:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 599F8182 for ; Sun, 28 Aug 2016 21:00:35 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7SL01MK005972 for ; Sun, 28 Aug 2016 21:00:35 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201608282100.u7SL01MK005972@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 28 Aug 2016 21:00:35 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 21:00:35 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. 7 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Mon Aug 29 05:08:00 2016 Return-Path: Delivered-To: freebsd-wireless@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 55BE6BC5339 for ; Mon, 29 Aug 2016 05:08:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 318ABE9B for ; Mon, 29 Aug 2016 05:08:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x231.google.com with SMTP id e63so85355342ith.1 for ; Sun, 28 Aug 2016 22:08:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=ZRdaV0Hy6eMLuUU3XGexevWNfXSdH0T1aFN/Mrzn6Sg=; b=nTPwpwAMpkSMczJy76vwdbhpcw5k9aQxP7mtYwrU8JmURk/AATRNfzfF1p7JW3GARG JEg9LLr6s6coxVyI93sp2OXCsk37xgfI78LehrDSI8Jy88IJnnaY/IkgPMPXM/rSKLur oGr5dYa05Cp/q4/0Y6TX0rNJuxHSUEUG+SYvgZzrpQKVBlsiTUBGJ+HzWJNn5eqlVUgO 6j7aP2SLMUfCGmk2nL/DC3UT4fIpthoWSwYou/uYkYUy0aoyy8URwGwsZ02AUk+0CiPK CeJNuHPQeyry76U0I0rSBU1CHqcybotkUV9j+LLSud00yzoCvRXFAjLqT/zb3jkCkgrO oeRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=ZRdaV0Hy6eMLuUU3XGexevWNfXSdH0T1aFN/Mrzn6Sg=; b=e0gvA36xD6bAM5LO7jwHdBcPyRuvj91OHCqgd9IksuCKyM87t1WsqAIMQsFTEaG+hi QIJLAI72uUyxMsAmS3OFFdun9LmhS0mkT/fxvLN1+5vkfLIPY/kaqp1goQxrFicKDnZa 45Ib6bwxx8yGNPfS9Nw3LJKHOg16QKjqYRX2zVIVHnB+MOhCdDn0hRCCYErfCmw3pPui W8iVigUw6v/e3kSR7oXQNQAvP+e/AI+BKjNwSa/RpkUGhoxr4IWnOCIBepES2IsR6cIQ VqKd4SN7DQQn5xdi6+YsPg/210Cnt7pL3LQuFtyTdaENxmXLkAkX5Hlw8k/MnH23xqc1 EAtA== X-Gm-Message-State: AE9vXwPW7H2Qesnn/KA3t0l/gq5z4LHp4c6qiFtJS2/R+z0Ad8kKs4F39l0zEbuvt03eZ0U3PmGJs693iPxteQ== X-Received: by 10.36.73.195 with SMTP id e64mr12092185itd.80.1472447279405; Sun, 28 Aug 2016 22:07:59 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.141.129 with HTTP; Sun, 28 Aug 2016 22:07:58 -0700 (PDT) From: Adrian Chadd Date: Sun, 28 Aug 2016 22:07:58 -0700 X-Google-Sender-Auth: 565Y1-ltVq-RHkg8QZdy8Xcxklo Message-ID: Subject: WDS/DWDS experiments - an update To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2016 05:08:00 -0000 hiya, I've started digging into what FreeBSD WDS is at. Yes, it's because I now need it at home. :-) * there's two kinds of WDS - static and dynamic * I'm playing with dynamic WDS for now * with dynamic WDS, the STA/AP has a normal association with (ifconfig wlanX dwds) and then the AP side creates a VAP for each seen DWDS source * .. ie, a MAC address behind the STA. * Then, 'wlanwds' is supposed to watch the AP parent interface, and then plumb up the WDS VAP, insert it into the bridge, etc, when it comes up. So, a bunch of stuff doesn't work out of the box anymore! * firstly, there's no longer a parent interface - but we still have to provide it (eg 'ath0'.) It should be okay, but I need to dig into it some more. * I can somehow make the ath driver run out of RX buffers when DWDS is enabled - I'll dig into what's going on. * It is correctly receiving DWDS frames on the WDS VAP, and sending them back out, but it's not making it through to the parent interface and out to the station again. * And, there's no 'node' plumbed up in ifconfig wlan0 or ifconfig wlanX (WDS VAP) list sta. I need to go see what's going on there - the rate control code needs it at least; other state like A-MPDU will need it too. Next, I'll try the static WDS (wdslegacy) and see if I can at least plumb things up with that. Maybe I'll get lucky. -adrian From owner-freebsd-wireless@freebsd.org Tue Aug 30 18:33:41 2016 Return-Path: Delivered-To: freebsd-wireless@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 E639FBC9406 for ; Tue, 30 Aug 2016 18:33:41 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 A1CBEEE for ; Tue, 30 Aug 2016 18:33:41 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x233.google.com with SMTP id t7so27836550qkh.1 for ; Tue, 30 Aug 2016 11:33:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=ZCtRSySsUt86p0UR+D5K5zQU8cW4f2WIj0err1djUeA=; b=HkbZaxb3+XTI3rjFdsvOuCSvGr7TGuq372Fy0hDoXcCEoySAqzeCk8MdLM8Rs/+8P3 JjyYIU0cZUQFilYr15VeFv2JIto6ZV8dmoTOeqMULQbCrW3dT0Z0I39M/uFwP8WhMjPl 1DhMMbYSdYICB7mTjMJPrtjvougwZYBRPT3Ag= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=ZCtRSySsUt86p0UR+D5K5zQU8cW4f2WIj0err1djUeA=; b=FM6UGXYYgAcx3bsBH28oNoEZftWezVBnMTpkS2b75xmLa63okAY+61Oje1G8qd6Amn G40/BMvMKLsWOpJ7/Fs5OYmFLz5Dc3fQmiZ6UDkeTxosbr2GEBi+XnIBFnXfEZU9rOiF t7y3v68M7cshncnk2iyNyUrNNIaObNfQ+gJP+wsSn6JIRqsOvQNJi5y1c5yi4qLI1iNr +oUt6Eu7C7WyVSxi+dTDJyTob54QKCHgWYTBoy3C7zseImumrCqAajoKOh0npaUfv15O QgB75NyrxoCpotRMfHhft5e6XpBH8n0oSesChVraArZLjtaRQs4nKNx+L3wT6p4QucXG hBRQ== X-Gm-Message-State: AE9vXwNYlfxsXrtM4IyqY395qivXuOpNnOcNi66Q7to6w1CoY6OMnMkzwP8BYYw9EwLkbg== X-Received: by 10.55.94.66 with SMTP id s63mr6325279qkb.31.1472582019671; Tue, 30 Aug 2016 11:33:39 -0700 (PDT) Received: from [192.168.43.219] (191-247-227-7.3g.claro.net.br. [191.247.227.7]) by smtp.googlemail.com with ESMTPSA id m4sm22405956qkf.29.2016.08.30.11.33.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Aug 2016 11:33:38 -0700 (PDT) To: freebsd-wireless@freebsd.org From: =?UTF-8?B?T3RhY8OtbGlv?= Subject: urtwn instable on Beaglebone Black Message-ID: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> Date: Tue, 30 Aug 2016 15:33:28 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 18:33:42 -0000 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 C920. 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 From owner-freebsd-wireless@freebsd.org Tue Aug 30 19:22:10 2016 Return-Path: Delivered-To: freebsd-wireless@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-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." 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" From owner-freebsd-wireless@freebsd.org Tue Aug 30 23:32:54 2016 Return-Path: Delivered-To: freebsd-wireless@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 B33E8BC9C41; Tue, 30 Aug 2016 23:32:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 7D953869; Tue, 30 Aug 2016 23:32:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id l203so48304604oib.1; Tue, 30 Aug 2016 16:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dk0YSShG+hmpEv+wM2EeCELou4faoqef4eV2FPToa4U=; b=h5auOXtq7OCOYaO6HTJICxCALAC3oFsrGllLkafn57g4PE0Oljf8vpxMRq/DvM763u d+AOWtybEgyi8X7LmZ8lkHKXkDWjaa00kVoLbtvTgctEEoFu4pICv8XWkinujY1JSdMV b8R2ztsxFwE5TPLISfPDTxdV8MGmIpDM4tQHWIH8UbABzqdhoIxph9g09HIuECGyEpE0 ZP/2gQZC6QT3luFJHqFOLltdDVV1Ud8VyUHy4TspldzduSY+D4a7M+kBZun4jGgRZ5lz gURL7iXeUgD3bfw0NTiT/zQEzYDEzszwexKLW4oOOiruukciASKsnIXwv+AmLeJv2SJU GLbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dk0YSShG+hmpEv+wM2EeCELou4faoqef4eV2FPToa4U=; b=VP1Q6jV+e12j4+wNY5q2Shgbr1zyhzwnoNjMs+/T+DpzdBYm/OzzPB/14+U1ty0GUP RH58E3xysQWAWgH7Bk+GX281e5cXdwClGNPt3+ub78yLIFViWEwxaMDFyczpOEZJ0nqx XUT6qooukomjpVPVVCT/r4R4xAQZX1kwo08+P0MmB5YS8pzLOpudJ43vaYY20F80WUph vSYhcSZI4DvYmRtWwqjYSn2tx9WhzZcUOKlcLMghdNdfIWN4F+QA4RHom44n+j3VJbzG nhC5b+tBre2awDnvjMsLFbEqAgAFOTYEw5chl3t2v99OduQMVrTgyHNsCUtrTvHZ4V31 JVXg== X-Gm-Message-State: AE9vXwP3rqfhpAu6ON2iJI1HZA1hJQ27MyqJbqiXV+NVray+npCRGqRjfVHv6felkzWOheX25DuMCLkj8hCiHQ== X-Received: by 10.157.35.85 with SMTP id k21mr7249385otd.41.1472599973668; Tue, 30 Aug 2016 16:32:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Tue, 30 Aug 2016 16:32:50 -0700 (PDT) In-Reply-To: References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> From: Adrian Chadd Date: Tue, 30 Aug 2016 16:32:50 -0700 Message-ID: Subject: Re: urtwn instable on Beaglebone Black To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" , "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 23:32:54 -0000 hi, What's the signal level? (ifconfig -v wlan0 list sta) -a On 30 August 2016 at 12:21, Andriy Voskoboinyk wrote: > 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 softwar= e >> and have tested it using a urtwn device + webcam Logitech C920. All is >> connected using a USB hub with external power source. So urtwn and webca= m, >> 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 al= l >> 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 t= he >> same USB HUB, the same wrtwn device and same camera, randomly after some >> time the beaglebone black network shutdown and terminal shows this messa= ges >> : >> >> >> 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" > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@freebsd.org Tue Aug 30 23:33:38 2016 Return-Path: Delivered-To: freebsd-wireless@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 64B17BC9D01; Tue, 30 Aug 2016 23:33:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 2CE8893C; Tue, 30 Aug 2016 23:33:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id e124so12806768ith.0; Tue, 30 Aug 2016 16:33:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bmHAv4CY1J62OaJVtLYitGhOluWfK4ilgDOgEa+9vlY=; b=CsBO0tE8JLd8l2h7eBnPBg3C/UfEq0ZLfj6/wFkzqoUbez9PQnFv9bMLWSL8RPQrv9 lBdzGGd+rKX47kYIVavCOHpGGATZDqieZ78aY6qkuOJEAPbhWvnYLj6Mzil0z9MkNv4K uXo3OftyEj9DWYm8MfgSibCNSFestqfS/tbgjxNCCi3SGEOF6nj/0cMHnGvdC8HgPAKM bB0QFGZeoTOx9ANgv+iG4K55uOZA1Rof9k1oYfNzwvuW3ETjahNGNagrQO78X3c67o20 /4YpianQE41/wezfgtgBQ1P2AcAjnDxSipEAmZnAUhuo0r5pR2vIhvCATaU/ewyvmmWk UjEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bmHAv4CY1J62OaJVtLYitGhOluWfK4ilgDOgEa+9vlY=; b=P/QgHr8G1qIEk080pgW3pAu4HHE45y+Gwykfvr7KKO32QWRIZkBSZDeBsLUOAxFsPn BmyhpUd9zePmzAOsQN6wOpW2DF7W4O17+I79v53U312kkNOEmscm+nYMpl2diU+r+KUM w1M4o/Vl0X/M+Ef2wpc5NAsK2SvtR+K10YLnMt6FB2ICr6F2V9ZZRObO8UmjgDI2d9iQ pMQ2gTie9NikF4IWuNchgGJHzgaBtaYvElWm1XQgwzIytXKbdFbMqrIdMRm4l10tUwPq 6slC2kEHPs9D6cALchTT1d1XXWBTgBu/XjQU7kEbXkawgyyEFS8JoxdwK82hpouI5CEi 53wA== X-Gm-Message-State: AE9vXwOmlr5rKal4Ix1bgqfB1tQiulJqlcajj/hsxZZHZm/BThEjc6U+WvXJlns5to2aYWIV2yu1v9ZfSIdUAw== X-Received: by 10.36.150.70 with SMTP id z67mr25915253itd.80.1472600017558; Tue, 30 Aug 2016 16:33:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Tue, 30 Aug 2016 16:33:36 -0700 (PDT) In-Reply-To: References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> From: Adrian Chadd Date: Tue, 30 Aug 2016 16:33:36 -0700 Message-ID: Subject: Re: urtwn instable on Beaglebone Black To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" , =?UTF-8?B?T3RhY8OtbGlv?= , "freebsd-arm@freebsd.org" , "freebsd-usb@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 23:33:38 -0000 .. and which chipset? (dmesg | grep urtwn) -a On 30 August 2016 at 16:32, Adrian Chadd wrote: > hi, > > What's the signal level? (ifconfig -v wlan0 list sta) > > > > -a > > > On 30 August 2016 at 12:21, Andriy Voskoboinyk wrote: >> 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 softwa= re >>> and have tested it using a urtwn device + webcam Logitech C920. All is >>> connected using a USB hub with external power source. So urtwn and webc= am, >>> 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 a= ll >>> 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 som= e >>> time the beaglebone black network shutdown and terminal shows this mess= ages >>> : >>> >>> >>> 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 b= e >>> 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" >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.o= rg" From owner-freebsd-wireless@freebsd.org Thu Sep 1 03:35:03 2016 Return-Path: Delivered-To: freebsd-wireless@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 C5C35BC7DD5 for ; Thu, 1 Sep 2016 03:35:03 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 7C6D7E4F for ; Thu, 1 Sep 2016 03:35:03 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x22c.google.com with SMTP id t7so72606238qkh.1 for ; Wed, 31 Aug 2016 20:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=JUEwmO3fB+64AbDESZSIfvaCTMxjANcp9IMIQv0vnG4=; b=LiO8TZT3EMTEYrma9typoLsOloa5JOIq7t22Dobm3yYmUc8jRM9oCA36+QITTK97a4 zAfamNQfdgQtNIO1ajvvTfguRQqblq0Ll62lNyMUl2dfc3ghCSUfKpy4z6M6h+kGrM1/ ZX8XcgmHKCnbB3xWmo3ZN49kk4Ql/u95d7G9k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=JUEwmO3fB+64AbDESZSIfvaCTMxjANcp9IMIQv0vnG4=; b=MoN9LDZ3p+YbCZQa7p2VkB82b32N6IkCElg0BeP/7FPUvbjvKOs8kmv0DtJWNvDnvJ p6UzqM7lJ0d750JBBQtmqqO9uTLFIAlpHzmEzgdnP+eS0QFiL3cgRSTdwI48aW6MAO2D 7QJRztYqwfbvvfoEVCyejNCAWNFSdJ01zEyqvtKr5dMe3hcOrj0CGWUvPUSE6mWy6n5B 69CGeRXAYWy4x9KOUK3jCsN42X4/9LHb1wXyun+4ax3NvM1x8SbmwC5S2g4pFehnS7Pr J3NYo2NXBqhghLGNXqzjaK9ePZvw/k+0dAJkK4EnVw0RXxM+6MoTwjTdSFrmZwnxg4Li ytSg== X-Gm-Message-State: AE9vXwPbjs4ngIiYrYsq1ei522sMFx22EmoxkiHeWzxeYm3HWHY2wiSvkVFAepsLW2YHuQ== X-Received: by 10.55.16.86 with SMTP id a83mr15476144qkh.212.1472700902454; Wed, 31 Aug 2016 20:35:02 -0700 (PDT) Received: from [192.168.0.11] ([187.60.94.34]) by smtp.googlemail.com with ESMTPSA id q68sm1748549qka.1.2016.08.31.20.34.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Aug 2016 20:35:00 -0700 (PDT) Subject: Re: urtwn instable on Beaglebone Black To: Adrian Chadd , Andriy Voskoboinyk References: <0a35e401-47ba-dddb-3769-1b64353c3202@bsd.com.br> Cc: "freebsd-wireless@freebsd.org" , "freebsd-arm@freebsd.org" , Hans Petter Selasky From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: <9dc9d2b8-848e-a1c0-4dd5-2841003df189@bsd.com.br> Date: Thu, 1 Sep 2016 00:34:46 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 03:35:03 -0000 wifi and webcam C920 connected using a USB host connected to beaglebone black I tested with two chipsets: chipset 1 % dmesg | grep urtwn urtwn0: on usbus1 urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R urtwn0: enabling 11n signal level: % ifconfig -v wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 58:23:8c:c6:e1:aa 3 1 54M 12.0 0 14 16752 EP AQE SSID RATES DSPARMS<1> ERP<0x4> ???<2f0104> RSN XRATES<12,18,24,96> HTCAP HTINFO WPS VEN WPA WME After open a MJPEG stream near immediately I got: Network is down % urtwn0: ieee80211_crypto_encap returns NULL. urtwn0: ieee80211_crypto_encap returns NULL. urtwn0: ieee80211_crypto_encap returns NULL. So I unplugged the device and then plug another, after some time I got: Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=25, val=0, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone dhclient[783]: ioctl(SIOCGIFFLAGS) on wlan0: Operation not permitted Aug 31 23:51:38 beaglebone dhclient[783]: Interface wlan0 no longer appears valid. Aug 31 23:51:38 beaglebone dhclient[783]: No live interfaces to poll on - exiting. Aug 31 23:51:38 beaglebone dhclient[783]: exiting. Aug 31 23:51:38 beaglebone dhclient[607]: connection closed Aug 31 23:51:38 beaglebone dhclient[607]: exiting. Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCGIFFLAGS]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=95, val=208, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=17, val=0, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Device not configured Aug 31 23:51:38 beaglebone wpa_supplicant[412]: ioctl[SIOCS80211, op=16, val=1, arg_len=0]: Device not configured ugen1.3: at usbus1 urtwn0: on usbus1 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R urtwn0: enabling 11n wlan0: Ethernet address: 80:3f:5d:11:28:e6 chipset 2: % dmesg | grep urtwn urtwn0: on usbus1 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R urtwn0: enabling 11n signal level: % ifconfig -v wlan0 list sta ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 58:23:8c:c6:e1:aa 3 1 54M 16.0 0 18 27216 EP AQE SSID RATES DSPARMS<1> ERP<0x4> ???<2f0104> RSN XRATES<12,18,24,96> HTCAP HTINFO WPS VEN WPA WME Network is down urtwn0: ieee80211_crypto_encap returns NULL. % urtwn0: ieee80211_crypto_encap returns NULL. urtwn0: ieee80211_crypto_encap returns NULL. So, I remove the camera from HUB, plug it on my notebook. the urtwn stay in HUB+Beaglebone. Now, I transmit from my notebook to beaglebone and back to notebook. Throughput of rx | tx --------------------------------------+------------------ bytes 66,43 MiB | 860,85 MiB --------------------------------------+------------------ max 4,36 Mbit/s | 24,80 Mbit/s average 1,66 Mbit/s | 21,57 Mbit/s min 6 kbit/s | 18,35 Mbit/s --------------------------------------+------------------ packets 51283 | 667960 --------------------------------------+------------------ max 412 p/s | 2342 p/s average 156 p/s | 2042 p/s min 0 p/s | 1740 p/s --------------------------------------+------------------ time 5,45 minutes And no problems. I think that the bug occurs when the webcam and wifi dongle are in the same USB HUB. Maybe a electric problem? I'm using a external power source to USB HUB. []'s -Otacílio Em 30/08/2016 20:33, Adrian Chadd escreveu: > .. and which chipset? (dmesg | grep urtwn) > > > > -a > > > On 30 August 2016 at 16:32, Adrian Chadd wrote: >> hi, >> >> What's the signal level? (ifconfig -v wlan0 list sta) >> >> >> >> -a >> >> >> On 30 August 2016 at 12:21, Andriy Voskoboinyk wrote: >>> Tue, 30 Aug 2016 21:33:28 +0300 було написано Otacílio >>> : >>> >>> 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 C920. 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" >>> _______________________________________________ >>> 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" From owner-freebsd-wireless@freebsd.org Thu Sep 1 07:44:05 2016 Return-Path: Delivered-To: freebsd-wireless@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 872C6BCB93B for ; Thu, 1 Sep 2016 07:44:05 +0000 (UTC) (envelope-from bawig1@gmail.com) Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 56189F8E for ; Thu, 1 Sep 2016 07:44:05 +0000 (UTC) (envelope-from bawig1@gmail.com) Received: by mail-pf0-x243.google.com with SMTP id a143so722710pfa.3 for ; Thu, 01 Sep 2016 00:44:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version; bh=9KK+WF3WTjKVU/0MsWEGdKwEunEtdkH2aFFZoCdzp38=; b=Casd+/RwKuoePkhqwpJl+Uoaa8cTiTnxEzXjDk3P5cE2/zcFZBpypAffCLqns9IoMT IRi3ceXpOC8kOXWyIwbk2A+A+Q9R1jDzI806bWUZffuQQXM6NG5qRkSD/XofJiM6EaqQ cjN3LjCVu7BAuIHVvVCN8dL9NX8qKpdHXrb4N4d70S1rzCfb+6DoXEnFxm50q0YgJsw5 8IuEUaT04zcuQ55IDrnVOygsy1+f2I4wtPnzlUdL2ldkIvHX1J+vWHGkCJWl8Y3FkfTM 8MnPPuqQjYzT6E6bj1ibfJUfP+I2N4fKUv2zz84yOs9s9d9NSUMOCk8hpUPP5Z+ENesb DLow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=9KK+WF3WTjKVU/0MsWEGdKwEunEtdkH2aFFZoCdzp38=; b=GoeJrQ72zbrribNv9ntv93Y4S1Poi3wreGuJccXC6sUw1+xVMVJrb0jRY4r97uxV2L bbhN0Ln40gFLvGAl1nQrpOxON4ITYmeuxF2BiS6c8/AODg3rSwAxyQ00IVg/OwYsYnCi 6gRoL1teXR7IK5SKn3ufOu/dNdVM9YVr8As0agmPU1/NDD2WM8SoSlKhQJLar9FB9OAn EeCGODQd5UmSDRFCOFVmgOc0N2PM35TprelLzCUkO2Gvrpf7o4DhfFI+Kqs8Pi5MOYdg P8b51kc1G/9Vkcfyi9GKPuHr08szA2mpDbsi0KD0uj0+48/3jhT70l9Qc8/rvynIgEhO eaPw== X-Gm-Message-State: AE9vXwPuGaxzp9pNBulziFr3lHAIakczVRCid4VPL+iHmhEfubtxw1lt+5FoRhi40wGa9w== X-Received: by 10.98.67.193 with SMTP id l62mr24456212pfi.16.1472715844743; Thu, 01 Sep 2016 00:44:04 -0700 (PDT) Received: from [192.168.43.12] (pa49-199-84-84.pa.vic.optusnet.com.au. [49.199.84.84]) by smtp.gmail.com with ESMTPSA id b90sm4926152pfc.29.2016.09.01.00.43.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Sep 2016 00:44:04 -0700 (PDT) To: freebsd-wireless@freebsd.org From: Brett Wiggins Subject: RE: Updating bwn to support newer chipsets Message-ID: <338149a3-d576-06a0-ba87-64f6e55f7c6c@gmail.com> Date: Thu, 1 Sep 2016 17:43:34 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 07:44:05 -0000 Hi everyone, I'm replying to a message from April 07 2015 which was calling for people to help get the bwn driver to support BCM4331 adapters. The message is provided below. I am happy to help with code or testing. I'm dual booting a Macbook Pro 10,1 with OS X and Freebsd 10.3-RELEASE, my wireless adapter is a BCM4331. If anyone know of progress on this or needs help please let me know. Brett. Updating bwn to support newer chipsets *Felix Friedlander* felixphew0 at gmail.com /Tue Apr 7 06:35:13 UTC 2015/ * Previous message (by thread): hostapd with wpa * Next message (by thread): Updating bwn to support newer chipsets * *Messages sorted by:* [ date ] [ thread ] [ subject ] [ author ] ------------------------------------------------------------------------ Hello all, I am trying to expand the bwn driver to support some newer-model Broadcom chips, like the BCM4331 in my machine. These chips require newer firmware, and so I have modified bwn-firmware-kmod to use a newer firmware. However, I do not have a device with one of the chips currently supported, so I cannot be sure that this change won't break things. Do any of you have a device that you are willing to try with the new firmware? The changes are quite simple: --- Makefile.orig 2014-01-27 08:52:12.000000000 +1100 +++ Makefile 2015-04-07 08:31:46.000000000 +1000 @@ -2,7 +2,7 @@ # $FreeBSD: head/net/bwn-firmware-kmod/Makefile 341294 2014-01-26 21:52:12Z bapt $ PORTNAME= bwn-firmware -PORTVERSION= 0.1.0 +PORTVERSION= 0.2.0 CATEGORIES= net MASTER_SITES= http://downloads.openwrt.org/sources/ \ http://mirror2.openwrt.org/sources/ @@ -36,11 +36,11 @@ WRKSRC= ${WRKDIR} FWNAME= bwn_v4 FWFILE= broadcom-wl-${FWVERSION}.tar.bz2 -FWVERSION= 4.150.10.5 +FWVERSION= 5.100.138 KMODNAME= ${FWNAME}_ucode FWNAME_LP= bwn_v4_lp FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2 -FWVERSION_LP= 4.178.10.4 +FWVERSION_LP= 5.100.138 KMODNAME_LP= ${FWNAME_LP}_ucode PLIST_SUB= KMODNAME="${KMODNAME}" \ KMODNAME_LP="${KMODNAME_LP}" @@ -54,7 +54,7 @@ tar xjf ${DISTDIR}/${FWFILE} mkdir -p ${WRKSRC}/bg b43-fwcutter -w ${WRKSRC}/bg \ - ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o + ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o ${TOUCH} ${WRKSRC}/bg/v4/ucode.fw @${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile --- distinfo.orig 2014-01-23 02:30:13.000000000 +1100 +++ distinfo 2015-04-07 08:37:10.000000000 +1000 @@ -2,3 +2,5 @@ SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794 SHA256 (broadcom-wl-4.178.10.4.tar.bz2) = 32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780 +SHA256 (broadcom-wl-5.100.138.tar.bz2) = f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f Any help would be much appreciated. -- Felix Friedlander > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: ------------------------------------------------------------------------ * Previous message (by thread): hostapd with wpa * Next message (by thread): Updating bwn to support newer chipsets * *Messages sorted by:* [ date ] [ thread ] [ subject ] [ author ] ------------------------------------------------------------------------ More information about the freebsd-wireless mailing list From owner-freebsd-wireless@freebsd.org Thu Sep 1 08:33:43 2016 Return-Path: Delivered-To: freebsd-wireless@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 1F189BC849B for ; Thu, 1 Sep 2016 08:33:43 +0000 (UTC) (envelope-from felixphew0@gmail.com) Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (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 CF79F6C1 for ; Thu, 1 Sep 2016 08:33:42 +0000 (UTC) (envelope-from felixphew0@gmail.com) Received: by mail-qk0-x243.google.com with SMTP id r128so5317264qkc.1 for ; Thu, 01 Sep 2016 01:33:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RZdbzPQ+aortU4uQ2FFP2i2ekhVoDfv3dc8Kr0dK2Xw=; b=Tazq/BjW/jTM+2LqQ+VGCwAEjLG0xeR2PnjQArv9sMDoZ//r3OII+A01GdejDVovRo 4OO3dC4Tk9iQsXPGXj9uD3uWvbRvaeoRCF8N/TbP5Gglc3yr8/Np/rEpWooalywjkc0f 9g1htdY2J9969i1oHEwZk+UydhE77jZrGPppBMT1QALT+JuhSYEYKATc6M+xdf1RhDYG pEjirRd75qSlTvTi/VNQuYb+zp4nU+wDtb0sxDa1L17CQld55bM84Li/NWwl7/+FDEFx oaJ4BRxhlEEDnHsow6+ZKz6YA1WEHx3laVAPMrdYwUpFiNMdv8hCSVkGVyafY0qB79tE x0Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RZdbzPQ+aortU4uQ2FFP2i2ekhVoDfv3dc8Kr0dK2Xw=; b=KK8AxJ9EoVQO1WNu8zpDvP7Ajsm4QM7kRiUbcbz00fGwvbPn37v7Lg4OO8lnpZiYM/ bngcm8JXsAFACAWnjnZbYvx9gufmsjIuTBTVpSwVid28xsPhhZvvYZhXS1NTz8f17zAu 6/BzpjeHmZi2JgwKSMe6tmYmD32JkOP2uPihEArK0t8bGx1h7klkCixDYaTwON6nSGmQ 4NRv7awh2Y0FXJ60WrrBrPh6NVJmwmLK1nFbi2M0XEs7BO5ER1ad2/or3quSG0VSUr65 FGJ8Gk6GI8pV2QYioPBMeAXj5rtZ7xFDfoCHAHkOFfQwXJ/bKmnHn3ITIkChQzpaxTjx M8RQ== X-Gm-Message-State: AE9vXwON8KSqi0RT1wwRD1ErG3UGUIXlBmwE21FWTK0VW9NPBBwGvPj8CYEDIc0m9WWxvewIrKTHKVMWZCTVaQ== X-Received: by 10.55.5.65 with SMTP id 62mr15940194qkf.279.1472718821926; Thu, 01 Sep 2016 01:33:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.25.148 with HTTP; Thu, 1 Sep 2016 01:33:41 -0700 (PDT) In-Reply-To: <338149a3-d576-06a0-ba87-64f6e55f7c6c@gmail.com> References: <338149a3-d576-06a0-ba87-64f6e55f7c6c@gmail.com> From: Felix Friedlander Date: Thu, 1 Sep 2016 18:33:41 +1000 Message-ID: Subject: Re: Updating bwn to support newer chipsets To: Brett Wiggins Cc: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 08:33:43 -0000 Hi Brett, It turns out I actually have no idea how to write wireless drivers, but progress is being made by adrian and others. I don't think there's a working build to test - yet - but if you want to help code, then by all means, just talk to someone more competent than me. For the record, I'm also dual-booting several MacBooks, both BCM4331 (apparently not *that* far off) and the newer BCM4360 (which is miles away, being an 11ac chip). - Felix On 1 September 2016 at 17:43, Brett Wiggins wrote: > Hi everyone, > > I'm replying to a message from April 07 2015 which was calling for people to > help get the bwn driver to support BCM4331 adapters. The message is provided > below. I am happy to help with code or testing. I'm dual booting a Macbook > Pro 10,1 with OS X and Freebsd 10.3-RELEASE, my wireless adapter is a > BCM4331. > > If anyone know of progress on this or needs help please let me know. > > Brett. > > > Updating bwn to support newer chipsets > > *Felix Friedlander* felixphew0 at gmail.com > > /Tue Apr 7 06:35:13 UTC 2015/ > > * Previous message (by thread): hostapd with wpa > > > * Next message (by thread): Updating bwn to support newer chipsets > > > * *Messages sorted by:* [ date ] > > > [ thread ] > > > [ subject ] > > > [ author ] > > > > > ------------------------------------------------------------------------ > > Hello all, > I am trying to expand the bwn driver to support some newer-model Broadcom > chips, like the BCM4331 in my machine. These chips require newer firmware, > and so I have modified bwn-firmware-kmod to use a newer firmware. However, I > do not have a device with one of the chips currently supported, so I cannot > be sure that this change won't break things. Do any of you have a device > that you are willing to try with the new firmware? > > The changes are quite simple: > > --- Makefile.orig 2014-01-27 08:52:12.000000000 +1100 > +++ Makefile 2015-04-07 08:31:46.000000000 +1000 > @@ -2,7 +2,7 @@ > # $FreeBSD: head/net/bwn-firmware-kmod/Makefile 341294 2014-01-26 21:52:12Z > bapt $ > PORTNAME= bwn-firmware > -PORTVERSION= 0.1.0 > +PORTVERSION= 0.2.0 > CATEGORIES= net > MASTER_SITES= http://downloads.openwrt.org/sources/ \ > http://mirror2.openwrt.org/sources/ > @@ -36,11 +36,11 @@ > WRKSRC= ${WRKDIR} > FWNAME= bwn_v4 > FWFILE= broadcom-wl-${FWVERSION}.tar.bz2 > -FWVERSION= 4.150.10.5 > +FWVERSION= 5.100.138 > KMODNAME= ${FWNAME}_ucode > FWNAME_LP= bwn_v4_lp > FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2 > -FWVERSION_LP= 4.178.10.4 > +FWVERSION_LP= 5.100.138 > KMODNAME_LP= ${FWNAME_LP}_ucode > PLIST_SUB= KMODNAME="${KMODNAME}" \ > KMODNAME_LP="${KMODNAME_LP}" > @@ -54,7 +54,7 @@ > tar xjf ${DISTDIR}/${FWFILE} > mkdir -p ${WRKSRC}/bg > b43-fwcutter -w ${WRKSRC}/bg \ > - ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o > + ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o > ${TOUCH} ${WRKSRC}/bg/v4/ucode.fw > @${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile > --- distinfo.orig 2014-01-23 02:30:13.000000000 +1100 > +++ distinfo 2015-04-07 08:37:10.000000000 +1000 > @@ -2,3 +2,5 @@ > SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794 > SHA256 (broadcom-wl-4.178.10.4.tar.bz2) = > 32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f > SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780 > +SHA256 (broadcom-wl-5.100.138.tar.bz2) = > f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f > > Any help would be much appreciated. > -- > Felix Friedlander > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 819 bytes > Desc: not available > URL: > > > ------------------------------------------------------------------------ > > * Previous message (by thread): hostapd with wpa > > > * Next message (by thread): Updating bwn to support newer chipsets > > > * *Messages sorted by:* [ date ] > > > [ thread ] > > > [ subject ] > > > [ author ] > > > > > ------------------------------------------------------------------------ > More information about the freebsd-wireless mailing list > > _______________________________________________ > 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" From owner-freebsd-wireless@freebsd.org Thu Sep 1 17:35:25 2016 Return-Path: Delivered-To: freebsd-wireless@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 82BD2BCBFD7; Thu, 1 Sep 2016 17:35:25 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 3B1E697C; Thu, 1 Sep 2016 17:35:25 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id g62so66026327lfe.3; Thu, 01 Sep 2016 10:35:24 -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:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=2AeNHwMZGQjB/bsXcOHQUr+lMe5QJGNa4R60CxCdCqk=; b=JFFxYD5xwjo0vgR8I8Fn9yNIVlpjpDQZNhHXTSPC2O00bYAtYEZCDiPP+mP6PRPBpZ m/9+fEPc3ajJWgrtUEFpS6FuGFblTnzCCNSr5QHh0epwQyPVnJ76W6SXuM4eqJfzrjsZ AFkGZmbxcnMo3EcN7mn7PsUb3pYwUUlD51YyZkiz4Lcy6QSE+qOjFYObJUTupJYb3LWp XwRQeKPTBMEjVxlO/7mNb/Ipkc6oW8VorV9otCAX4wBw+nb9OCX/3WnuiPHDBdAkgGN/ d4jBKLFRHOo45TZIJE+pY3W/TgmSokMPn6hcpkieGHgCVNEPnXbeZOvG5S0KT1KUurWC kpdg== X-Gm-Message-State: AE9vXwM96TLFDDi63OVDJKq44IYrV+2I5JRTo+Zj2FRglrplH4cX4zy1Ss/8E3CUMoGg7Q== X-Received: by 10.46.32.131 with SMTP id g3mr5102108lji.46.1472747359829; Thu, 01 Sep 2016 09:29:19 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id k63sm1041861lfe.48.2016.09.01.09.29.18 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 01 Sep 2016 09:29:19 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" Subject: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver) References: Date: Thu, 01 Sep 2016 19:29:03 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 17:35:25 -0000 Hi everyone, rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged into a single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is available on https://github.com/s3erios/rtwn repository. Among bugfixes / code deduplication, there some new features too: 1) multi-vap support (one any wireless interface + one STA interface + any number of monitor mode interfaces). 2) few new sysctls: * dev.rtwn.#.crypto - controls how to use hardware crypto acceleration * dev.rtwn.#.ratectl_selected * dev.rtwn.#.ratectl - selects current 'rate control' algorithm (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). 3) (incomplete) power management support for RTL8188EU (requires firmware). 4) Short Guard Interval support. It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; however, it was never tested with RTL8192CE or RTL8812AU. How-to-build: 1) download / checkout the repository. 2) apply 'patch-usbdevs.diff' against '/usr/src' 3) build and install rtwn module: cd $repository/sys/modules/rtwn && make && make install 4) build and install rtwn_usb/rtwn_pci: cd ../rtwn_usb && make && make install cd ../rtwn_pci && make && make install 5) unload previous && load current drivers: kldunload if_urtwn if_rtwn kldload /boot/modules/if_rtwn.ko /boot/modules/if_rtwn_usb.ko /boot/modules/if_rtwn_pci.ko 6) Use. From owner-freebsd-wireless@freebsd.org Fri Sep 2 17:54:38 2016 Return-Path: Delivered-To: freebsd-wireless@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 79AC5BCDC6A for ; Fri, 2 Sep 2016 17:54:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6905EACD for ; Fri, 2 Sep 2016 17:54:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u82Hsbt9034620 for ; Fri, 2 Sep 2016 17:54:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises Date: Fri, 02 Sep 2016 17:54:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 17:54:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206112 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #4 from Andriy Voskoboinyk --- Should be fixed in r302035. --=20 You are receiving this mail because: You are the assignee for the bug.=