From owner-freebsd-wireless@freebsd.org Sun Nov 22 04:56:45 2015 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 41129A35079 for ; Sun, 22 Nov 2015 04:56:45 +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 2CEC41B8F for ; Sun, 22 Nov 2015 04:56:45 +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 tAM4uj75036526 for ; Sun, 22 Nov 2015 04:56:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203271] Wi-Fi no longer driven on some hardware with 11.0-CURRENT Date: Sun, 22 Nov 2015 04:56:43 +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: 11.0-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: grahamperrin@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 22 Nov 2015 04:56:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203271 --- Comment #11 from Graham Perrin --- https://github.com/pcbsd/pcbsd/commit/9dc6aa26de2508b50dec6054edeee2d67998ad73 (2015-11-16) > When we boot PC-BSD desktop, check for new wireless devices which are missing /etc/rc.conf wlans_ entries. > > This fixes a problem where the GUI tools don't see any wireless devices anymore on -CURRENT -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Tue Nov 24 02:39:01 2015 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 10687A369F8 for ; Tue, 24 Nov 2015 02:39:01 +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 F0BC41481 for ; Tue, 24 Nov 2015 02:39:00 +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 tAO2d0TV028685 for ; Tue, 24 Nov 2015 02:39:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Date: Tue, 24 Nov 2015 02:39:00 +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: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tony@git-pull.com X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 24 Nov 2015 02:39:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #24 from Tony Narlock --- (In reply to Hans Petter Selasky from comment #23) Sorry for the late response. I tried 40, 160, 253 and 500. Unfortunately, same results. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Nov 25 20:34:04 2015 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 957EBA373D8 for ; Wed, 25 Nov 2015 20:34:04 +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 81B1F12F1 for ; Wed, 25 Nov 2015 20:34:04 +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 tAPKY4Z5036761 for ; Wed, 25 Nov 2015 20:34:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 204818] iwn0: iwn_intr: fatal firmware error Date: Wed, 25 Nov 2015 20:34:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lbolmerg@posteo.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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: Wed, 25 Nov 2015 20:34:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204818 Bug ID: 204818 Summary: iwn0: iwn_intr: fatal firmware error Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: lbolmerg@posteo.de iwn(4) firmware error settings in /etc/rc.conf: wlans_iwn0="wlan0" ifconfig_wlan0="-ht WPA DHCP powersave country DE" ... Nov 25 15:59:23 ludger-thinkpad kernel: iwn0: m em 0xf2400000-0xf2401fff irq 17 at device 0.0 on pci3 ... Nov 25 19:04:26 ludger-thinkpad kernel: 0:0): Periph destroyed Nov 25 19:12:26 ludger-thinkpad kernel: iwn0: device timeout Nov 25 19:12:35 ludger-thinkpad kernel: iwn0: iwn_intr: fatal firmware error Nov 25 19:12:35 ludger-thinkpad kernel: firmware error log: Nov 25 19:12:35 ludger-thinkpad kernel: error type = "SYSASSERT" (0x0000000 5) Nov 25 19:12:35 ludger-thinkpad kernel: program counter = 0x00011240 Nov 25 19:12:35 ludger-thinkpad kernel: source line = 0x00000654 Nov 25 19:12:35 ludger-thinkpad kernel: error data = 0x000000FE00000000 Nov 25 19:12:35 ludger-thinkpad kernel: branch link = 0x0000F46C0000F46C Nov 25 19:12:35 ludger-thinkpad kernel: interrupt link = 0x0000153200000000 Nov 25 19:12:35 ludger-thinkpad kernel: time = 8776000 Nov 25 19:12:35 ludger-thinkpad kernel: driver status: Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 0: qid=0 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 1: qid=1 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 2: qid=2 cur=1 queued=1 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 3: qid=3 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 4: qid=4 cur=11 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 5: qid=5 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 6: qid=6 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 7: qid=7 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 8: qid=8 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 9: qid=9 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 10: qid=10 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 11: qid=11 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 12: qid=12 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 13: qid=13 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 14: qid=14 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 15: qid=15 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 16: qid=16 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 17: qid=17 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 18: qid=18 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: tx ring 19: qid=19 cur=0 queued=0 Nov 25 19:12:35 ludger-thinkpad kernel: rx ring: cur=37 -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Nov 25 20:43:08 2015 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 EE09BA3775C for ; Wed, 25 Nov 2015 20:43:08 +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 DA03E1E41 for ; Wed, 25 Nov 2015 20:43:08 +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 tAPKh8rR056999 for ; Wed, 25 Nov 2015 20:43:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 204818] iwn0: iwn_intr: fatal firmware error Date: Wed, 25 Nov 2015 20:43:09 +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: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: s3erios@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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: Wed, 25 Nov 2015 20:43:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204818 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |s3erios@gmail.com --- Comment #1 from Andriy Voskoboinyk --- Can you reproduce this without "powersave" option? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Wed Nov 25 21:44:01 2015 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 F0453A37796 for ; Wed, 25 Nov 2015 21:44:01 +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 DCCD41905 for ; Wed, 25 Nov 2015 21:44:01 +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 tAPLi1mq053246 for ; Wed, 25 Nov 2015 21:44:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 204818] iwn0: iwn_intr: fatal firmware error Date: Wed, 25 Nov 2015 21:44:02 +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: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lbolmerg@posteo.de X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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: Wed, 25 Nov 2015 21:44:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204818 --- Comment #2 from Ludger Bolmerg --- the error occured just once. I can't reproduced it. The powersave option was turned on a while ago without causing any issues -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Nov 26 07:44:17 2015 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 48854A3856D for ; Thu, 26 Nov 2015 07:44:17 +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 346A01AB4 for ; Thu, 26 Nov 2015 07:44:17 +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 tAQ7iHxf066265 for ; Thu, 26 Nov 2015 07:44:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203088] [patch] net/if_media.h: remove obsolete mode (IFM_IEEE80211_IBSS) Date: Thu, 26 Nov 2015 07:44:17 +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: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: s3erios@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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: 7bit 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.20 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, 26 Nov 2015 07:44:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203088 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Overcome By Events Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Nov 26 17:26:32 2015 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 DD254A3AE43 for ; Thu, 26 Nov 2015 17:26:32 +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 C86FC160D for ; Thu, 26 Nov 2015 17:26:32 +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 tAQHQWtA074534 for ; Thu, 26 Nov 2015 17:26:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203086] [patch] security/wpa_supplicant or from base: fix WPA-None in IBSS mode Date: Thu, 26 Nov 2015 17:26:33 +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: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 26 Nov 2015 17:26:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203086 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: adrian Date: Thu Nov 26 17:26:28 UTC 2015 New revision: 291366 URL: https://svnweb.freebsd.org/changeset/base/291366 Log: [wpa] bring up interface in ap_mode=2 This is required for WPA-NONE operation. PR: bin/203086 Submitted by: avos@ Changes: head/contrib/wpa/src/drivers/driver_bsd.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Nov 26 17:29:18 2015 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 7CB4CA3AF19 for ; Thu, 26 Nov 2015 17:29:18 +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 684521B7E for ; Thu, 26 Nov 2015 17:29:18 +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 tAQHTIdE077949 for ; Thu, 26 Nov 2015 17:29:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203177] [patch] wpa_supplicant(8): initialize interface before scanning (ap_scan=2) Date: Thu, 26 Nov 2015 17:29:18 +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: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 26 Nov 2015 17:29:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203177 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org Status|New |In Progress --- Comment #1 from Adrian Chadd --- committed in -HEAD r291366. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Nov 26 17:29:34 2015 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 C6ACAA3AF2D for ; Thu, 26 Nov 2015 17:29:34 +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 B27B51BAE for ; Thu, 26 Nov 2015 17:29:34 +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 tAQHTYKP078328 for ; Thu, 26 Nov 2015 17:29:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203086] [patch] security/wpa_supplicant or from base: fix WPA-None in IBSS mode Date: Thu, 26 Nov 2015 17:29:34 +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: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.20 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, 26 Nov 2015 17:29:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203086 --- Comment #2 from commit-hook@freebsd.org --- A commit references this bug: Author: adrian Date: Thu Nov 26 17:28:40 UTC 2015 New revision: 291368 URL: https://svnweb.freebsd.org/changeset/base/291368 Log: [wpa] use IFM_IEEE80211_ADHOC for now on FreeBSD for IBSS operation. PR: bin/203086 Submitted by: avos Changes: head/contrib/wpa/src/drivers/driver_bsd.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Thu Nov 26 22:57:43 2015 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 67499A3A59B; Thu, 26 Nov 2015 22:57:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 3637019F2; Thu, 26 Nov 2015 22:57:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igl9 with SMTP id 9so17716744igl.0; Thu, 26 Nov 2015 14:57:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=RcNvqOYt9U2w6OFmW3ECPzjb0CCqmOJDLmxgObsZlCA=; b=OMwXauI/CrowtgTAsL/k+wUDMerTKamAs6psO3/bOhSzkyIpLtm+VgOrdkb5wWvQvc tNqwLE4D7Lm1U+SF9DHf1imuXsRygzH01SehwqMV1zPPX/as//SrK0ChpBfi1gj3IfaZ oEK+gskv6SXSFTTwYwfV8P9Th43W/7pJb8Zr715V+BpdWTRlQUWS0V12LP1L+hzyCrfX N3NxIve4SAneAURIgWxJuF9MFr+jlyTkWR1K7sr41pAECX0qAX7qJuJrexxxNNbogJzo hIVEzWZA6DPup0Q2Ky30s2oyQ3NhvOAKm6tp1ho/h1SArEiLE/dK943Ym/omiBJEIc0X EREA== MIME-Version: 1.0 X-Received: by 10.50.136.226 with SMTP id qd2mr5210450igb.37.1448578662242; Thu, 26 Nov 2015 14:57:42 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.217.196 with HTTP; Thu, 26 Nov 2015 14:57:42 -0800 (PST) Date: Thu, 26 Nov 2015 14:57:42 -0800 X-Google-Sender-Auth: cRIV_5TCwxZSzimfoHs7cSKyRM8 Message-ID: Subject: moving some 802.11 code into lib80211 From: Adrian Chadd To: "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 26 Nov 2015 22:57:43 -0000 hiya, I've started migrating net80211 specific bits out of ifconfig into a library. https://reviews.freebsd.org/D4290 I'd like to commit this initial step in a couple of days so I can easily add more to things. I'd love feedback. ;) Thanks, -adrian From owner-freebsd-wireless@freebsd.org Fri Nov 27 07:31:53 2015 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 8E476A39E80; Fri, 27 Nov 2015 07:31:53 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 787C91D21; Fri, 27 Nov 2015 07:31:53 +0000 (UTC) (envelope-from rpaulo@me.com) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from akita.hsd1.ca.comcast.net (c-73-162-13-215.hsd1.ca.comcast.net [73.162.13.215]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Mar 31 2015)) with ESMTPSA id <0NYG00D0CQ8XPY10@mr11p00im-asmtp001.me.com>; Fri, 27 Nov 2015 07:31:47 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-11-27_01:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=0 kscore.compositescore=1 compositescore=0.9 suspectscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 rbsscore=0 spamscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510090000 definitions=main-1511270141 Message-id: <1448609505.4088.18.camel@me.com> Subject: Re: moving some 802.11 code into lib80211 From: Rui Paulo To: Adrian Chadd , "freebsd-wireless@freebsd.org" , "freebsd-arch@freebsd.org" Date: Thu, 26 Nov 2015 23:31:45 -0800 In-reply-to: References: X-Mailer: Evolution 3.18.2-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 27 Nov 2015 07:31:53 -0000 On Thu, 2015-11-26 at 14:57 -0800, Adrian Chadd wrote: > hiya, > > I've started migrating net80211 specific bits out of ifconfig into a > library. > > https://reviews.freebsd.org/D4290 > > I'd like to commit this initial step in a couple of days so I can > easily add more to things. > > I'd love feedback. ;) > That looks useful.  A quick look at the API and I didn't see anything wrong with it... -- Rui Paulo From owner-freebsd-wireless@freebsd.org Fri Nov 27 21:26:34 2015 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 8501AA3AE96 for ; Fri, 27 Nov 2015 21:26:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001: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 482D51EFF for ; Fri, 27 Nov 2015 21:26:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iouu10 with SMTP id u10so125614950iou.0 for ; Fri, 27 Nov 2015 13:26:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=pzj9mdzdDMiJarvbPYZyEoOKeC/fytUdtjdeu/EsVsk=; b=xlsy3pPW9DDRW/wt+wNQDUsu/hTPIz1EH6NhJllg2Rct0N/0Oc1KfVnC64c5GT5T7H DzssVI0qLqpXBoxou4/r3UvVYKX3geDMECoPSadW44joHXGnrYMwSaeNOkfYd2LujsFy pE/x9VCnHi9gNxoHzP7qr7vuYz/m3j/YO3OCBg6V1pTSmEQjyjUzln8WtVO1OtSsWGwt tBQHgBZnp3SOjdviWHyI0dO25lqEzo78idfgBLq+o7rWm+JtH9VDViSDkY0WJR3j0iKS pTn0WmiHozbIecpC4ymX0nZvOJIAAnCwHaJVjdtuhRxoacSHHm8zzlp58B7ElqoJ/bR0 kT0A== MIME-Version: 1.0 X-Received: by 10.107.10.199 with SMTP id 68mr46310269iok.75.1448659593422; Fri, 27 Nov 2015 13:26:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.217.196 with HTTP; Fri, 27 Nov 2015 13:26:33 -0800 (PST) Date: Fri, 27 Nov 2015 13:26:33 -0800 X-Google-Sender-Auth: g9bzk5rZrKAfVStG6ERlxtjvMXA Message-ID: Subject: ath bug: currates != sc_currates! From: Adrian Chadd To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 27 Nov 2015 21:26:34 -0000 Hiya, I finally observed this bug in the wild. It's .. mildly annoying and tricky to fix. The ath driver has a single rate table associated with the main hardware interface, because that's in a single mode. (ie, the NIC is in 11a, 11bg, 11b, 11g, 11na, 11ng, etc mode.) Then associated stations and such can negotiate a different set of rates - eg, an 11n 3x3 HT/40 AP can have stations that are non-11n (eg 11a or 11bg as appropriate), or 1-stream HT/20, etc.) The rate control code looks at the negotiated rates from net80211 and AND's them with what's in sc->sc_currates. Now, we used to have a crash in the past where the rate control code would reference rate indexes way outside of the current table. I put in a check (the subject of this message) which detects if the main interface rate table has changed and if so, it just defaults to the lowest rate and prints an error. That's worked fine so far but I never sat down to figure out why. So i've seen it happen in IBSS. it's very annoying. I'm sure the STA side is somewhat the same. What's happening is this: * VAP is in IBSS mode, in SCAN state, looking for a peer * upon each real channel change it'll flush the node list * it is also learning neighbors based on beacons seen So if you're scanning, you're fine. then this happens: * VAP is in IBSS mode, and you hard-code the channel * it does a SCAN, but it doesn't really change channel - it just changes operating mode. yes, net80211 still sees it as a channel change but for some reason it's not flushing the neighbor table each tim * So, it sees a new neighbor during scan, then it selects an operating mode that isn't the same as the mode where it saw the neighbor, and it .. well, now the node was setup with the old channel mode and the NIC is in the new channel mode. Here's some example debugging output. In this instance I created wlan0, set it to channel 10:ht/20, disabled ht/40. The peer (00:03:7f:10:42:81) is configured as an 11g interface. It eventually gets configured as a 10:g rather than staying 10:ht/20, and that's what's getting sc_currates happening. Now, I don't yet know what the correct solution is. Ideally if you change operating mode like this you'll flush out the nodes, or at least you'll update the rate control settings. It's tricky though because what we should do to be 100% clean w/ 11n is to stop TX, anything in the software/hardware queues that didn't go out needs to have the rate control recalculated, and then we start TX again after the channel change/reset. (There's a similar requirement for this with 20/40MHz dynamic channel width changing.) I could fix the net80211 side to be smarter about choosing interface configurations for IBSS (as yes, it can put the interface into ht/20 or ht/40 and still speak to an 11b/11bg IBSS node) but that just hides the problem in ath(4). So, grr! -adrian wlan0: WPA: using KEY_MGMT WPA-NONE WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 04 01 00 00 50 f2 00 01 00 00 50 f2 00 bsd_set_key: alg=3 addr=0x0 key_idx=0 set_tx=1 seq_len=6 key_len=16 wlan0: ieee80211_crypto_newkey: cipher 3 flags 0x8b keyix 0 wlan0: ieee80211_crypto_setkey: AES-CCM keyix 0 flags 0x10b mac ff:ff:ff:ff:ff:ff rsc 0 tsc 0 len 16 wlan0: State: SCANNING -> ASSOCIATING wpa_driver_bsd_associate: ssid 'CACHEBOY_IBSS_ENCRYPT' wpa ie len 24 pairwise 1 group 16 key mgmt 16 wpa_driver_bsd_set_drop_unencrypted: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 24) wpa_driver_bsd_associate: set PRIVACY 1 wlan0: start running, 0 vaps running wlan0: ieee80211_start_locked: up parent ath0 ath0: ath_update_chainmasks: TX chainmask is now 0x1, RX is now 0x1 ath0: ath_init: imask=0xe0000863 wlan0: start running, 1 vaps running wlan0: ieee80211_new_state_locked: INIT -> SCAN (nrunning 0 nscanning 0) wlan0: ieee80211_newstate_cb: INIT -> INIT arg 0 wlan0: adhoc_newstate: INIT -> INIT (0) wlan0: ieee80211_newstate_cb: INIT -> SCAN arg 0 wlan0: adhoc_newstate: INIT -> SCAN (0) ath0: ath_node_alloc: c4:93:00:00:3c:c9: an 0xc1077000 wlan0: ieee80211_alloc_node 0xc1077000 in station table wlan0: node_reclaim: remove 0xc1070000 from station table, refcnt 1 ath0: ath_setslottime: chan 2457 MHz flags 0x480 long slot, 20 usec wlan0: ieee80211_new_state_locked: SCAN -> RUN (nrunning 0 nscanning 0) ath0: ath_node_free: c4:93:00:00:3c:c9: an 0xc1070000 ath0: ath_node_cleanup: c4:93:00:00:3c:c9: an 0xc1070000 ath0: ath_tx_node_flush: c4:93:00:00:3c:c9: flush; is_powersave=0, stack_psq=0, tim=0, swq_depth=0, clrdmask=1, leak_count=0 ath0: ath_chan_set: 10 (2457 MHz, flags 0x480) wlan0: ieee80211_add_neighbor: mac<00:03:7f:10:42:81> ath0: ath_node_alloc: 00:03:7f:10:42:81: an 0xc1070000 wlan0: ieee80211_alloc_node 0xc1070000<00:03:7f:10:42:81> in station table ath0: ath_newassoc: 00:03:7f:10:42:81: reassoc; isnew=1, is_powersave=0 wlan0: [00:03:7f:10:42:81] ath_rate_ctl_reset: size 1600 rate/tt 1 Mb /14016 2 Mb /7464 5 Mb /3355 11 Mb /2181 12 Mb /1480 18 Mb /1124 24 Mb /940 36 Mb /764 48 Mb /672 54 Mb /644 ath0: ath_edma_tx_drain: called ath0: ath_stoptxdma: tx queue [9] 0x12b3000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0x42724904, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [1] 0x1205f00, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [2] 0x251041c0, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [3] 0x10f8700, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [8] 0x106c6a5c, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_edma_tx_drain: called ath0: ath_stoptxdma: tx queue [9] 0x12b3000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0x42724904, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [1] 0x1205f00, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [2] 0x251041c0, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [3] 0x10f8700, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_tx_stopdma: tx queue [8] 0x106c6a5c, active=0, hwpending=0, flags 0x00000000, link 0, holdingbf=0 ath0: ath_update_chainmasks: TX chainmask is now 0x1, RX is now 0x1 ath0: ath_txq_update: Q1 qflags 0xf aifs 2 cwmin 15 cwmax 1023 burstTime 2048 ath0: ath_txq_update: Q0 qflags 0xf aifs 7 cwmin 15 cwmax 1023 burstTime 0 ath0: ath_txq_update: Q2 qflags 0xf aifs 2 cwmin 7 cwmax 15 burstTime 3008 ath0: ath_txq_update: Q3 qflags 0xf aifs 2 cwmin 3 cwmax 7 burstTime 1504 wlan0: ieee80211_newstate_cb: SCAN -> RUN arg -1 wlan0: adhoc_newstate: SCAN -> RUN (-1) ath0: ath_beacon_alloc: bf_m=0x82603500, bf_node=0xc107e000 ath0: ath_node_free: c4:93:00:00:3c:c9: an 0xc107e000 ath0: ath_node_cleanup: c4:93:00:00:3c:c9: an 0xc107e000 ath0: ath_tx_node_flush: c4:93:00:00:3c:c9: flush; is_powersave=0, stack_psq=0, tim=0, swq_depth=0, clrdmask=1, leak_count=0 ath0: ath_txq_update: Q1 qflags 0xf aifs 2 cwmin 15 cwmax 1023 burstTime 2048 ath0: ath_txq_update: Q0 qflags 0xf aifs 7 cwmin 15 cwmax 1023 burstTime 0 ath0: ath_txq_update: Q2 qflags 0xf aifs 2 cwmin 7 cwmax 15 burstTime 3008 ath0: ath_txq_update: Q3 qflags 0xf aifs 2 cwmin 3 cwmax 7 burstTime 1504 wlan0: ieee80211_ibss_merge: new bssid 16:cb:5a:b2:52:4d: short preamble, long slot time wlan0: node_reclaim: remove 0xc1077000 from station table, refcnt 1 ath0: ath_setslottime: chan 2457 MHz flags 0x480 long slot, 20 usec wlan0: ieee80211_new_state_locked: RUN -> RUN (nrunning 0 nscanning 0) wlan0: ieee80211_ref_node (ieee80211_send_proberesp:2727) 0xc1070000<00:03:7f:10:42:81> refcnt 4 wlan0: ieee80211_ref_node (ieee80211_send_proberesp:2727) 0xc1070000<00:03:7f:10:42:81> refcnt 5 wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (158 bytes) FAIL rate/short/long 1 Mb /0/5 nframes/nbad [1/1] wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (158 bytes) FAIL rate/short/long 1 Mb /0/5 nframes/nbad [1/1] ping 192.168.169.wlan0: ieee80211_ref_node (ieee80211_send_proberesp:2727) 0xc1070000<00:03:7f:10:42:81> refcnt 4 1wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (158 bytes) FAIL rate/short/long 1 Mb /0/5 nframes/nbad [1/1] # ping 192.168.169.10 PING 192.168.169.10 (192.168.169.10): 56 data bytes ath0: ath_rate_findrate: currates != sc_currates! wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (138 bytes) OK rate/short/long 1 Mb /0/1 nframes/nbad [1/0] 64 bytes from 192.168.169.10: icmp_seq=0 ttl=64 time=25.827 ms ath0: ath_rate_findrate: currates != sc_currates! wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (138 bytes) OK rate/short/long 1 Mb /0/1 nframes/nbad [1/0] 64 bytes from 192.168.169.10: icmp_seq=1 ttl=64 time=14.466 ms ath0: ath_rate_findrate: currates != sc_currates! wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (138 bytes) OK rate/short/long 1 Mb /0/1 nframes/nbad [1/0] 64 bytes from 192.168.169.10: icmp_seq=2 ttl=64 time=14.847 ms ath0: ath_rate_findrate: currates != sc_currates! wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (138 bytes) OK rate/short/long 1 Mb /0/1 nframes/nbad [1/0] 64 bytes from 192.168.169.10: icmp_seq=3 ttl=64 time=14.893 ms ath0: ath_rate_findrate: currates != sc_currates! wlan0: [00:03:7f:10:42:81] ath_rate_tx_complete: size 250 (138 bytes) OK rate/short/long 1 Mb /0/1 nframes/nbad [1/0] 64 bytes from 192.168.169.10: icmp_seq=4 ttl=64 time=15.846 ms From owner-freebsd-wireless@freebsd.org Sat Nov 28 00:01:01 2015 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 A98EBA3AC7B for ; Sat, 28 Nov 2015 00:01:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 757951C57 for ; Sat, 28 Nov 2015 00:01:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igcph11 with SMTP id ph11so34631177igc.1 for ; Fri, 27 Nov 2015 16:01:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oQF+altkMVxYoa+IICpjIO0aeWxoJYKAIImnjJSDvWY=; b=MsH2E8ujsa4rurd98pxoYHKl00/9NHWQ9UmiP0NKrP+IP+uBgs39eF2XGVwGpECUQR uppvTxZ/qqId5/ztJ7fvWBwdyZ3MoJio0jxbMt8G7oP0O2kR5AIrVRDzkvubG5zNMxUt hy7HtjSAa078Del6xm+X6OYhkyXpkNGN2UGYS+QqbRJnU+tKB8OBxhNuU3+DLFhNAQkP ljfzeqwGqdfiyqxjMSqUUVO+VqDeyjXm85ihDH4Bw3mWIGjH44LGiY9PWODC6wzagjXl vPi5VhYrQQdPItnXT6T62NzC3kY3pujyD3PNl1M5TPMRcWn0UvLST+E5bRv0scy0qGC3 ie8w== MIME-Version: 1.0 X-Received: by 10.50.66.144 with SMTP id f16mr10060342igt.22.1448668860779; Fri, 27 Nov 2015 16:01:00 -0800 (PST) Received: by 10.36.217.196 with HTTP; Fri, 27 Nov 2015 16:01:00 -0800 (PST) In-Reply-To: References: Date: Fri, 27 Nov 2015 16:01:00 -0800 Message-ID: Subject: Re: USB WiFi works only after cold reboot From: Adrian Chadd To: Serge Voilokov Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 28 Nov 2015 00:01:01 -0000 Ok. so it looks like something is getting wedged at device attach time. I think avos fixed a few things for returning errors but I don't think it solves the problem. can you try updating it to the latest -HEAD and trying again? Thanks, -adrian On 19 November 2015 at 20:57, Serge Voilokov wrote: > Realtek: > > urtwn0: 2> on usbus0 > urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > > From: > https://www.adafruit.com/products/814 > > > On Thu, Nov 19, 2015 at 11:36 PM, Adrian Chadd wrote: >> It looks like it's reading some invalid data via the EEPROM. I've seen >> it do it yet and I haven't sat down to figure it out. >> >> Which device is it? >> >> >> -a >> >> >> On 19 November 2015 at 19:56, Serge Voilokov wrote: >>> Hi, >>> >>> I have a problem on Raspberry PI-A with Realtek WiFi adapter. >>> After reboot on watchdog or kernel panic wifi doesn't init properly. >>> Sometimes wlan0 is not created, sometimes ethernet address is >>> ff:ff:ff:ff:ff:ff, firmware loading errors, etc. >>> >>> After cold reboot it works file. >>> >>> How can I avoid the cold reboot? >>> Now on boot I do several attempts of 'usbconfig reset' until wifi >>> starts working. >>> It doesn't seem reliable. >>> Is the other way to make cold reset of usb and/or wifi without rebooting the OS? >>> >>> Thanks, >>> --serge >>> _______________________________________________ >>> 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 Sat Nov 28 18:06:31 2015 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 1BF5FA37400 for ; Sat, 28 Nov 2015 18:06:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB8051D92; Sat, 28 Nov 2015 18:06:30 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [10.0.1.96] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id tASI6KD4079348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 28 Nov 2015 18:06:26 GMT (envelope-from swills@FreeBSD.org) To: freebsd-wireless@freebsd.org From: Steve Wills Subject: urtwn broken at r291262 Message-ID: <5659ED1D.70003@FreeBSD.org> Date: Sat, 28 Nov 2015 13:06:21 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 28 Nov 2015 18:06:26 +0000 (UTC) X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.98.7 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 28 Nov 2015 18:06:31 -0000 Hi, My Raspberry Pi has a urtwn USB WiFi device. It was working previously, at r281469. It's been a while, but I updated to r291262 and now it seems to associate, but can't get a DHCP lease. When I run tcpdump, it looks like it's receiving but not transmitting. (But obviously it transmits enough to associate.) Looking at recent commits, I'm building r290629 and will test that, as I suspect r290630. Any suggestions or should I just bisect to the exact commit? I can send more detailed debugging info if needed, just let me know what would help. Thanks, Steve From owner-freebsd-wireless@freebsd.org Sat Nov 28 19:40:00 2015 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 09394A3B44C for ; Sat, 28 Nov 2015 19:40:00 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f51.google.com (mail-lf0-f51.google.com [209.85.215.51]) (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 AFE6C1EBF; Sat, 28 Nov 2015 19:39:59 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by lfdl133 with SMTP id l133so157389299lfd.2; Sat, 28 Nov 2015 11:39:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=content-type:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=wBU/6Jav9eHjhwmsgR3oLnhMcafSb+Z8bxcwyVRRAs0=; b=Fyvdir/9ul+uBpNj1bG73kUKsMIKIGWXjuaeQPvblJ0ICEzBqK3xwxbPxHGu19tVg1 z3ecXny/4aTqKiiwlfkQMVb9hTKL/lNTv8lphol9TONXPgU5Dhr7gJd8/3UWKGL0+oeF BscmIlqafRS6FbTZ0p6G3/uKD2r2/EsrpcS9q8VGEigC3kFqBnHrCFJQTfTs6Usi62rv u23HzVLHRocuB7vd/2nGiDNOe71BP6NmKZ+az8kBUlL4VAAnL2H7uzTFlIa3FKt/3ksF cS8PDcryM8zM3qxbM8LQijJg0dUlv4NEhH06Op0LJX6UztWLyxfhv3e1lwtjiO13hAre +qbA== X-Received: by 10.25.165.202 with SMTP id o193mr21680579lfe.83.1448736250850; Sat, 28 Nov 2015 10:44:10 -0800 (PST) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id um1sm5861921lbb.23.2015.11.28.10.44.09 (version=TLS1 cipher=AES128-SHA bits=128/128); Sat, 28 Nov 2015 10:44:10 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Steve Wills" Subject: Re: urtwn broken at r291262 References: <5659ED1D.70003@FreeBSD.org> Date: Sat, 28 Nov 2015 20:43:58 +0200 Cc: "freebsd-wireless@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <5659ED1D.70003@FreeBSD.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 28 Nov 2015 19:40:00 -0000 Sat, 28 Nov 2015 20:06:21 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Steve Wills = : > Hi, > > My Raspberry Pi has a urtwn USB WiFi device. It was working previously= , > at r281469. It's been a while, but I updated to r291262 and now it see= ms > to associate, but can't get a DHCP lease. When I run tcpdump, it looks= > like it's receiving but not transmitting. (But obviously it transmits > enough to associate.) Looking at recent commits, I'm building r290629 > and will test that, as I suspect r290630. Any suggestions or should I > just bisect to the exact commit? I can send more detailed debugging in= fo > if needed, just let me know what would help. > Hi, 1) chip name? 2) have you tried to run 'tcpdump -y IEEE802_11_RADIO = --no-promiscuous-mode'? > but not transmitting Which device is used to monitor the traffic? If this is the same device,= then you will not know about transmission failure/success, since tcpdump uses info from ieee80211_radiotap_tx(). > Any suggestions or should I just bisect to the exact commit? Probably, yes (it works for me without any issues on any revision). P.S. If problem is in r290630, then you can try to replace URTWN_MACID_B= C = with URTWN_MACID_BSS in urtwn_tx_data() (it was hardcoded as 0 in previous = revision). > Thanks, > Steve From owner-freebsd-wireless@freebsd.org Sat Nov 28 22:14:01 2015 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 5CCB7A3BD54 for ; Sat, 28 Nov 2015 22:14:01 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3357A1364; Sat, 28 Nov 2015 22:14:01 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [10.0.1.96] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id tASMDmG2081893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 28 Nov 2015 22:13:54 GMT (envelope-from swills@FreeBSD.org) Subject: Re: urtwn broken at r291262 To: Andriy Voskoboinyk References: <5659ED1D.70003@FreeBSD.org> Cc: "freebsd-wireless@freebsd.org" From: Steve Wills Message-ID: <565A271C.6070107@FreeBSD.org> Date: Sat, 28 Nov 2015 17:13:48 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 28 Nov 2015 22:13:55 +0000 (UTC) X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.98.7 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 28 Nov 2015 22:14:01 -0000 On 11/28/2015 13:43, Andriy Voskoboinyk wrote: > > Hi, > 1) chip name? urtwn0: on usbus0 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > 2) have you tried to run 'tcpdump -y IEEE802_11_RADIO > --no-promiscuous-mode'? > No. Wasn't sure how to interpret the output when I did, but I don't think I saw any receive. >> but not transmitting > Which device is used to monitor the traffic? If this is the same device, > then you will not know about transmission failure/success, > since tcpdump uses info from ieee80211_radiotap_tx(). Ok, same device, so no help. >> Any suggestions or should I just bisect to the exact commit? > Probably, yes (it works for me without any issues on any revision). > > P.S. If problem is in r290630, then you can try to replace > URTWN_MACID_BC with > URTWN_MACID_BSS in urtwn_tx_data() (it was hardcoded as 0 in previous > revision). So far all I can say for sure is that r290629 works. Will test r290630 now. More soon. Steve