From owner-freebsd-wireless@freebsd.org Sun May 21 20:55:44 2017 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 A7A7ED77C18 for ; Sun, 21 May 2017 20:55:44 +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 973FA1E1A for ; Sun, 21 May 2017 20:55:44 +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 v4LKth6d008422 for ; Sun, 21 May 2017 20:55:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213237] [ndis][patch] ndis wireless ieee80211 communication failure Date: Sun, 21 May 2017 20:55:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marius@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: glebius@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc 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.23 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, 21 May 2017 20:55:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213237 Marius Strobl changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-net@FreeBSD.org |glebius@FreeBSD.org CC| |marius@FreeBSD.org --- Comment #8 from Marius Strobl --- Assign to glebius@, who committed r286410. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-wireless@freebsd.org Sun May 21 21:00:42 2017 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 97170D77FB6 for ; Sun, 21 May 2017 21:00:42 +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 8BAC0661 for ; Sun, 21 May 2017 21:00:42 +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 v4LL01XE015108 for ; Sun, 21 May 2017 21:00:42 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201705212100.v4LL01XE015108@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, 21 May 2017 21:00:42 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 21 May 2017 21:00:42 -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. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Mon May 22 19:29:18 2017 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 5DCC8D781C3; Mon, 22 May 2017 19:29:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 EB9561A59; Mon, 22 May 2017 19:29:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id l50so44382543wrc.3; Mon, 22 May 2017 12:29:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=fRko37wv6ABCVwMhFF6X/sU93qzX/tIAwxJoTpvnrp0=; b=LvQb7mBWy4IZ05lzFyag91RUKebAtDJCFD49eP03606GdpgUByGXBZbyolcrLptYS1 K2FoZroyWOdlNSCbQinYNc4LF0hbhn8HKHfiVolhuzhjYKyjC2gZzku5GFpEYrUg5j5w ztRuKQ9aKalVrCmWX7sM38/O2Y4IrmdNoXB5sWKuiSmshjNiBJGcE8zUt30tjUPBKk76 g+TmkZ8ZmBZgW9eWM2lUAWBiejWzRXAqEeVmFWjV9stQcolySc23SJuO2klKDLeyS0er avXEUxzwQiAPTtYnF/NSrg+LVRdbHcNlo7tzQDRPlkDco1/jUkVPSSBjY1m6Viq1D62N 7Tvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=fRko37wv6ABCVwMhFF6X/sU93qzX/tIAwxJoTpvnrp0=; b=D08Fv6GT0d4fBbnZfQLPH22+wN0C31TO4sjSsgAdOuHc4zMsJrK7gbma7cwxh/8wkm Ne1jUQXqIWQWyGNQJqOhGKJAl/U7/LmLww2ykhI5B5p92j2nkkftulwKGgu0ow7O8m02 kv2MHeZS+XkMH2FKrGT/ALVvCq1viSfPUvENQTK5mDvJlqf/dnCOuqA6htfx22nBT0tE D1vL2iGwWVoJwGDNTih366XuNCsWlp7Gg1AJl9G8LXmJnmbSzUWNWFXcQ7KKIuYBdYYe T6PG5cnxzjZA6IEG9tEsaMP6xAxY5ZYLgWtfIi3ZeRN4Nh2pH3fA/02rtAWLpGW8rD+F 6ZuA== X-Gm-Message-State: AODbwcAfK/tPVX1qk7+z8LelDvY+87SSKJ539cYnZRbv1r/5UiPeswHG lecGuToPFdYFIXy3WG3AupnkUaXgnK6Z X-Received: by 10.223.134.80 with SMTP id 16mr14969019wrw.62.1495481355834; Mon, 22 May 2017 12:29:15 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.193.134 with HTTP; Mon, 22 May 2017 12:29:15 -0700 (PDT) From: Adrian Chadd Date: Mon, 22 May 2017 12:29:15 -0700 X-Google-Sender-Auth: 2i8jdfJTTPAcNiVt_N2d1Jb9WDg Message-ID: Subject: [rfc] breaking out if_ath into ... lots of modules To: "freebsd-wireless@freebsd.org" , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 22 May 2017 19:29:18 -0000 Hi, I've been putting this off for a few years, but now I've reached a point where I kind of need to do this. The TL;DR is this - I'd like to break the ath driver /back/ out into separate modules, and then have them be run-time loadable. It's part for space savings, and part for the upcoming ath10k work where I need to reuse the regulatory EEPROM code. The reason? I can't easily build a modular ath driver without compiling in /everything/. For the AR933x/AR934x embedded platforms which don't require the previous HAL chipset code, this is almost 800kbyte extra binary code in the kernel that doesn't ever get run. For earlier boards (say the AR9280 embedded boards), it's roughly 600kbyte of AR9300 HAL code that doesn't ever get run. I have a patchset (which I'll push up soon) which turns if_ath into: * if_ath - only the driver; * (if_ath_pci / if_ath_ahb stay the same); * ath_hal - only the shared, global HAL code (osdep routines, HAL core, regulatory code); * ath_rate - the ath rate control code (either sample, amrr, onoe); * ath_dfs - just dfs_null for now, but this will eventually be a radar detector; * ath_hal_{ar5210,ar5211,ar5212,ar5416,ar9300} - the individual chipset HALs. Now, I'm thinking of further breaking out ar5416 into {ar5416,ar9001,ar9002} just to save space for the embedded builds (like AR9103/AR9106 which some people still use) but that can come later. There's no AR2312/AR5312 11abg + MIPS4k core support in FreeBSD, so I'll go and look at making the AR5312 wifi support work. That'll become another HAL module. On the regulatory side, I then need to divorce the EEPROM regulatory code from ath_hal and turn /it/ into a separate module because, surprise, the ath10k 11ac hardware uses the same regulatory code. I'll do this particular step later. What does this mean? * If you compile up a kernel with everything in it, nothing will change - hopefully this is the majority of users; * If you compile a modular kernel or embedded platform - you need to load ath_hal and the relevant HAL modules before you load if_ath / if_ath_pci otherwise it won't find your hardware. I realise this is a bit of a POLA change, but I'd like to get it into -HEAD before FreeBSD-12 is cut. Thanks! -adrian From owner-freebsd-wireless@freebsd.org Mon May 22 20:00:30 2017 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 BBEA9D79262 for ; Mon, 22 May 2017 20:00:30 +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 AB7471283 for ; Mon, 22 May 2017 20:00:30 +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 v4MK0SbJ014828 for ; Mon, 22 May 2017 20:00:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213237] [ndis][patch] ndis wireless ieee80211 communication failure Date: Mon, 22 May 2017 20:00:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: glebius@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 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, 22 May 2017 20:00:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213237 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: glebius Date: Mon May 22 20:00:02 UTC 2017 New revision: 318677 URL: https://svnweb.freebsd.org/changeset/base/318677 Log: Fix regression in ndis(4) after r286410. This adds a bunch of checks for whether this is a Ethernet or 802.11 device and does proper dereferencing. PR: 213237 Submitted by: MFC after: 2 weeks Changes: head/sys/compat/ndis/kern_ndis.c head/sys/compat/ndis/subr_ndis.c head/sys/dev/if_ndis/if_ndis.c head/sys/dev/if_ndis/if_ndisvar.h --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-wireless@freebsd.org Mon May 22 20:38:06 2017 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 7CB59D79F54; Mon, 22 May 2017 20:38:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5942D1BCD; Mon, 22 May 2017 20:38:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 6256710AFA3; Mon, 22 May 2017 16:38:03 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Adrian Chadd , "freebsd-wireless@freebsd.org" Subject: Re: [rfc] breaking out if_ath into ... lots of modules Date: Mon, 22 May 2017 13:17:06 -0700 Message-ID: <1901874.v6m8jKq4cl@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-STABLE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 22 May 2017 16:38:03 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 22 May 2017 20:38:06 -0000 On Monday, May 22, 2017 12:29:15 PM Adrian Chadd wrote: > Hi, > > I've been putting this off for a few years, but now I've reached a > point where I kind of need to do this. > > The TL;DR is this - I'd like to break the ath driver /back/ out into > separate modules, and then have them be run-time loadable. It's part > for space savings, and part for the upcoming ath10k work where I need > to reuse the regulatory EEPROM code. > > The reason? I can't easily build a modular ath driver without > compiling in /everything/. For the AR933x/AR934x embedded platforms > which don't require the previous HAL chipset code, this is almost > 800kbyte extra binary code in the kernel that doesn't ever get run. > For earlier boards (say the AR9280 embedded boards), it's roughly > 600kbyte of AR9300 HAL code that doesn't ever get run. > > I have a patchset (which I'll push up soon) which turns if_ath into: > > * if_ath - only the driver; > * (if_ath_pci / if_ath_ahb stay the same); > * ath_hal - only the shared, global HAL code (osdep routines, HAL > core, regulatory code); > * ath_rate - the ath rate control code (either sample, amrr, onoe); > * ath_dfs - just dfs_null for now, but this will eventually be a radar detector; > * ath_hal_{ar5210,ar5211,ar5212,ar5416,ar9300} - the individual chipset HALs. > > Now, I'm thinking of further breaking out ar5416 into > {ar5416,ar9001,ar9002} just to save space for the embedded builds > (like AR9103/AR9106 which some people still use) but that can come > later. > > There's no AR2312/AR5312 11abg + MIPS4k core support in FreeBSD, so > I'll go and look at making the AR5312 wifi support work. That'll > become another HAL module. > > On the regulatory side, I then need to divorce the EEPROM regulatory > code from ath_hal and turn /it/ into a separate module because, > surprise, the ath10k 11ac hardware uses the same regulatory code. I'll > do this particular step later. > > What does this mean? > > * If you compile up a kernel with everything in it, nothing will > change - hopefully this is the majority of users; > * If you compile a modular kernel or embedded platform - you need to > load ath_hal and the relevant HAL modules before you load if_ath / > if_ath_pci otherwise it won't find your hardware. > > I realise this is a bit of a POLA change, but I'd like to get it into > -HEAD before FreeBSD-12 is cut. Why not have if_ath.ko just be a wrapper module that depends on everything like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading code in ifconfig still DTRT. You could name the "only the driver" module ath.ko or some such. -- John Baldwin From owner-freebsd-wireless@freebsd.org Mon May 22 20:44:08 2017 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 348F8D772B8 for ; Mon, 22 May 2017 20:44:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 EF1B410FD for ; Mon, 22 May 2017 20:44:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id a10so5357143itg.1 for ; Mon, 22 May 2017 13:44:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fZni93DQa3eQKKZWPH71Fa4Dh/ZePUdAsUFd21rYnfc=; b=ebvSfH8tEPrGCuwJW0BgvBQaSdIuM33mU4a182SQ/oJiOCiZgeyswN50/j7wUu5zD2 WfYZ76cJXWofVBqExVp967lg2IiQukVHirZkxmno9pb9sJ6lO7HJCOgqR/pAelRI/e30 m+wqIcKjE5XqIK2Yyq7SiGop5ynuY4niTkyFv0Zzsiyd5sVIOZT97mHbv/eXQOXSBzLL IBSh81QWSMc81g4a6bYrfrVgh5pzt8TtmYuZobx/I7aNb/qZ8HUWW5pbsIXzY3/ue8H0 PSGljActFgUWk0x1oyCLiIhC5T3sh0eFgiFGqR4gXOrejhhxXVkfMTO/bFiZq/T33UfI BIBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=fZni93DQa3eQKKZWPH71Fa4Dh/ZePUdAsUFd21rYnfc=; b=CLD6KFeTfi22UWYhFX6uAojR4FZF0LDBCvq+F8VTxjTAWgJxIDSCykuGrOaAnp+5az RemE/1TEzuZCTx/X1IC2SWl2RnhjjrK5iUemn4FtOTWDTmVtkXYVpnO3aU5Q27Z4fg3R 4ugSt8dafNiPpGJ9ymM0lHY9j1XfQktH0nixzcatUOhCZIXH/w5w0CX6j32ERGGE9Bkx TFB6YVlqLqXOMliwSY/SaEZQx2rCDWSPwlR48lgbA2wMzbEVmjvXpj496WGOSb/4ftjf dTYHtOKVZ2rwboKLJZpsV/qU8NgaIUrekbu6YxJTHULbMUJY9UN2mdcDFSLhzmnR1zlL F0gg== X-Gm-Message-State: AODbwcB1G0Mc08PwjITzR/jMhZkQAmlcS8YTGSdPqqk8HtLLYAirTOKP qVizEAPPt7+NXlydnwrYF12fvTZI+oXU X-Received: by 10.107.188.132 with SMTP id m126mr26963166iof.148.1495485847298; Mon, 22 May 2017 13:44:07 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.126.6 with HTTP; Mon, 22 May 2017 13:44:06 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:64b3:7ae1:cf64:fe87] In-Reply-To: <1901874.v6m8jKq4cl@ralph.baldwin.cx> References: <1901874.v6m8jKq4cl@ralph.baldwin.cx> From: Warner Losh Date: Mon, 22 May 2017 14:44:06 -0600 X-Google-Sender-Auth: 3Tao-lAn2txZX5BKMNqP9fQN4_U Message-ID: Subject: Re: [rfc] breaking out if_ath into ... lots of modules To: John Baldwin Cc: FreeBSD Current , Adrian Chadd , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 22 May 2017 20:44:08 -0000 On Mon, May 22, 2017 at 2:17 PM, John Baldwin wrote: > On Monday, May 22, 2017 12:29:15 PM Adrian Chadd wrote: > > Hi, > > > > I've been putting this off for a few years, but now I've reached a > > point where I kind of need to do this. > > > > The TL;DR is this - I'd like to break the ath driver /back/ out into > > separate modules, and then have them be run-time loadable. It's part > > for space savings, and part for the upcoming ath10k work where I need > > to reuse the regulatory EEPROM code. > > > > The reason? I can't easily build a modular ath driver without > > compiling in /everything/. For the AR933x/AR934x embedded platforms > > which don't require the previous HAL chipset code, this is almost > > 800kbyte extra binary code in the kernel that doesn't ever get run. > > For earlier boards (say the AR9280 embedded boards), it's roughly > > 600kbyte of AR9300 HAL code that doesn't ever get run. > > > > I have a patchset (which I'll push up soon) which turns if_ath into: > > > > * if_ath - only the driver; > > * (if_ath_pci / if_ath_ahb stay the same); > > * ath_hal - only the shared, global HAL code (osdep routines, HAL > > core, regulatory code); > > * ath_rate - the ath rate control code (either sample, amrr, onoe); > > * ath_dfs - just dfs_null for now, but this will eventually be a radar > detector; > > * ath_hal_{ar5210,ar5211,ar5212,ar5416,ar9300} - the individual chipset > HALs. > > > > Now, I'm thinking of further breaking out ar5416 into > > {ar5416,ar9001,ar9002} just to save space for the embedded builds > > (like AR9103/AR9106 which some people still use) but that can come > > later. > > > > There's no AR2312/AR5312 11abg + MIPS4k core support in FreeBSD, so > > I'll go and look at making the AR5312 wifi support work. That'll > > become another HAL module. > > > > On the regulatory side, I then need to divorce the EEPROM regulatory > > code from ath_hal and turn /it/ into a separate module because, > > surprise, the ath10k 11ac hardware uses the same regulatory code. I'll > > do this particular step later. > > > > What does this mean? > > > > * If you compile up a kernel with everything in it, nothing will > > change - hopefully this is the majority of users; > > * If you compile a modular kernel or embedded platform - you need to > > load ath_hal and the relevant HAL modules before you load if_ath / > > if_ath_pci otherwise it won't find your hardware. > > > > I realise this is a bit of a POLA change, but I'd like to get it into > > -HEAD before FreeBSD-12 is cut. > > Why not have if_ath.ko just be a wrapper module that depends on everything > like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading > code in ifconfig still DTRT. You could name the "only the driver" module > ath.ko or some such. > I like this a lot. There's much magic in places like netstat and people's loader.conf files that this solution would preseve that yours would break. Warner From owner-freebsd-wireless@freebsd.org Mon May 22 21:01:24 2017 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 8754FD777C0; Mon, 22 May 2017 21:01:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 1DD8719D6; Mon, 22 May 2017 21:01:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id 123so14416547wmg.1; Mon, 22 May 2017 14:01:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Map2q/ytlEwoLM/gtCKY9HprWf+CR3GooWHiNQqUAms=; b=c7QL6AOdW2d60MmXp9Z7u5InCSctQOmOwbezfsF/c+CLlp5mttM08Eo0EoOphm56X7 0ZZ5ANa+VHLRE/rcPTkUa0pdbY9o9lZLXHKH4TtXxpqA/soUm7yyrNS1pUlCDzkmPo2j NQO6kFOI8/IURofUU9QJ8Uh0m8pC/Vt1jJlAR7nDFVLKywwnMZesSMuP6bZ/aDwn2Rgm Hsmb4btqtXk3Nlup7+icjsdIo2sNwGqrq1ceytwuFXkka8KVuEEELGER0ewTiuVhIG4I sOARB3oRJd57WkBE33og0breSRySG/zAnf5EGL60/ZXAEMce/p7rIR0Lgo+CRKpS+sF4 F98A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Map2q/ytlEwoLM/gtCKY9HprWf+CR3GooWHiNQqUAms=; b=irGSeWAhgvB+5u1AfH5V1GCC0PbAW9yANNb0u4qJliPbbAnE5ij5E6qHdfbeRFZW+V 8Nmy37BnuR/B28QqYEXkyLmKQTRFJjRzcQ7vY/DzwWxBVi/Wd2x7YpToG+bLS9jmxuC9 BW1muuqsLSOaegeHwXtebU8Nv0WuNMRnbZbF/KI/Li6n68V6LKQo1jJOM+90eqhFeP3n 1+XL0xLQR6TTlYfJyOM7/2YZ+yRM2ClSUibbFORlHzUOfFDw/lNRUKGX+6FJQ9Rk3R74 SVwKwLniIUMr+on9UCWYxDRpp7iHICC5rF6H1tSGz85wKj98uLPJAO3aT5Le0tpnQFno FZEg== X-Gm-Message-State: AODbwcAhGydNwL8dIppqucxC346tEKZX69/IUp+BdMF6yRrIfyP8WpyQ wKHS5aQG3pKgu5eT4M+Xn1dxdefdyXDd X-Received: by 10.28.93.10 with SMTP id r10mr1524642wmb.68.1495486881865; Mon, 22 May 2017 14:01:21 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.28.193.134 with HTTP; Mon, 22 May 2017 14:01:21 -0700 (PDT) In-Reply-To: <1901874.v6m8jKq4cl@ralph.baldwin.cx> References: <1901874.v6m8jKq4cl@ralph.baldwin.cx> From: Adrian Chadd Date: Mon, 22 May 2017 14:01:21 -0700 X-Google-Sender-Auth: emgWswI0pXSWK0zYa7veNaO1jfM Message-ID: Subject: Re: [rfc] breaking out if_ath into ... lots of modules To: John Baldwin Cc: freebsd-current , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 22 May 2017 21:01:24 -0000 On 22 May 2017 at 13:17, John Baldwin wrote: > Why not have if_ath.ko just be a wrapper module that depends on everything > like dtraceall.ko? That would let 'kldload if_ath' and the auto-loading > code in ifconfig still DTRT. You could name the "only the driver" module > ath.ko or some such. Oh yeah, I could also do that to reduce POLA. :) Ok, I'll add that to the TODO list before I submit a review. I'll rename if_ath to if_ath_drv or something. -adrian From owner-freebsd-wireless@freebsd.org Tue May 23 07:27:50 2017 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 94C33D7A7CE for ; Tue, 23 May 2017 07:27:50 +0000 (UTC) (envelope-from pinjy@anthonypinder.wanadoo.co.uk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 82FCE1DA0 for ; Tue, 23 May 2017 07:27:50 +0000 (UTC) (envelope-from pinjy@anthonypinder.wanadoo.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 825D8D7A7CD; Tue, 23 May 2017 07:27:50 +0000 (UTC) Delivered-To: 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 8207AD7A7CC for ; Tue, 23 May 2017 07:27:50 +0000 (UTC) (envelope-from pinjy@anthonypinder.wanadoo.co.uk) Received: from sout.wanadoo.co.uk (sout3.wanadoo.co.uk [193.252.22.226]) by mx1.freebsd.org (Postfix) with ESMTP id 2B97E1D9F for ; Tue, 23 May 2017 07:27:49 +0000 (UTC) (envelope-from pinjy@anthonypinder.wanadoo.co.uk) Received: from outlook.com ([219.141.127.176]) by mwinf5d57 with ME id PjTL1v0053oV1W303jTUD2; Tue, 23 May 2017 09:27:42 +0200 X-ME-Helo: outlook.com X-ME-Auth: YW50aG9ueXBpbmRlckB3YW5hZG9vLmNvLnVr X-ME-Date: Tue, 23 May 2017 09:27:42 +0200 X-ME-IP: 219.141.127.176 Date: Tue, 23 May 2017 10:27:47 +0300 Subject: Get rid of the baby fat Message-ID: From: "Sexy Girl" To: websupport@gsquaredcomputing.com, dcooper@ldbassoc.com, are@bluestarcooking.com, wireless@freebsd.org, developments@healthcarerealty.com, abrown@clark.edu, greg@landeggeresq.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 07:27:50 -0000 After three days, I noticed the change in my butt.-https://goo.gl/69yR= pH From owner-freebsd-wireless@freebsd.org Tue May 23 14:35:54 2017 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 424EED7A76C for ; Tue, 23 May 2017 14:35:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 08F571702 for ; Tue, 23 May 2017 14:35:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.17.133] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 0543685B for ; Tue, 23 May 2017 17:35:46 +0300 (MSK) To: "freebsd-wireless@freebsd.org" Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: Status of QCA9882 support? Organization: FreeBSD Message-ID: <4422984a-ab73-f566-1bef-d7570489b44d@FreeBSD.org> Date: Tue, 23 May 2017 17:35:40 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6QJfBqJQcrRP7UbBwHI3WrBT0hPI79laE" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 14:35:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6QJfBqJQcrRP7UbBwHI3WrBT0hPI79laE Content-Type: multipart/mixed; boundary="r6LLpUWS7KAq98TV4upeRlwfQp9uxveJ7"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: "freebsd-wireless@freebsd.org" Message-ID: <4422984a-ab73-f566-1bef-d7570489b44d@FreeBSD.org> Subject: Status of QCA9882 support? --r6LLpUWS7KAq98TV4upeRlwfQp9uxveJ7 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I want to buy some new MiniPCIe WiFi adapters to make ny home network dual-banded (now I'm using one SR71-E from Ubiquiti, which is 9280). Could I buy QCA9882-based card? Will it work right now with -CURRENT? I don't speak about 802.11ac, 802.11n will be Ok right now, but can I bought new hardware to have new standards in future, or should I buy another 9280-based card? Thank you. --=20 // Lev Serebryakov --r6LLpUWS7KAq98TV4upeRlwfQp9uxveJ7-- --6QJfBqJQcrRP7UbBwHI3WrBT0hPI79laE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZJEi8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePn0MQAKBZqXEe7TROIWpCZ/yA2CvB u8uj48mpX3AHz7C+gysF/8lB+DJfeRlAphRb7x5KKzyEsQAN1F+JP2lb5pFx0gIZ pl3je8H6siXEwn/qjQH7aGyyDoVsP5w0QLn+72VL6E9Gn3Zxj4WmSPlSgwQrzmwR xrdqn09EX0INRndhz2IKJm18bWU1a6eeSs5qudGkDOn/gcn3en1DGxVmbAcO/Jgp A1miP7fltoYBsqwkj1rwMMSzUOTsqmSnka52pyHMTN1GlcARFdKGWxUmxWOruuEs Olf2XskAuowRZCeanrUYE4Qm8jOk9VZSbXn9pLzDzPvPuI33g6WmcnewxBtA2mO1 0oXK9yU/YvDTygfjf1epUlLZ6aFK4Tdv1YHV4WEYw8AtPkpzXIpj9nLdrHqPmW/d eLmlSuLdELOHdiqLq8DigEIyMS5BfbajhQR1ijUVipCI/IukQ7xQA91t8924J3xh vZMzw+ar/3lTLZsIJSf9jnqaRBx7+10f0E3BeUtlQnK1o5Xv5GzYw1fjybiJZqo9 bhB7GBuqUQZlVIWF6X0QnjW7Pjhmy48L7xL4WRitVVn6Gotyg1SzNSAKAg4HnKnW nYxtnw8t2rrdZOjIKqDq8yErCumYnwdqtbHI0YRaScFI0b6GxQ6ePVEofOfHAl/W dpiNYGCd1qpXXM+w+J0e =+5O8 -----END PGP SIGNATURE----- --6QJfBqJQcrRP7UbBwHI3WrBT0hPI79laE-- From owner-freebsd-wireless@freebsd.org Tue May 23 15:18:04 2017 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 6A995D7A1D2 for ; Tue, 23 May 2017 15:18:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 147ED16D3; Tue, 23 May 2017 15:18:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id 7so28508507wmo.1; Tue, 23 May 2017 08:18:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=84JWi2OBZcSOio7NclvLKt6MrTR3N2JH6OWkdRqQYL8=; b=tHtxdCdQdBJgnaMnoxKyAVWqTiAO56l40QAhDSAJnk11laZEYCWs4vVQvHfqtToihR tnhfTJEDqvnG/FUKAoKNbmHy4nKI4xoAjpPB6uUUZbskpFyBSuGNEh+8HeeIVJger0Xg rnSyNE5YbYNk+y6PHOUhN89tabN/fwN6v0EaZfuppX1e48JtsF8zEeoz/hGaoStKi0fO hWVZ36hhMYqb40JOUSxXhciz3dnwAG8x3iqHSomCPRtd3L/u6qkdh7gZT83XkVkoIrVV ICkS5+LygIjI2J83vo9XifYjNVtP3NuoPC7gZzU3BOQzcPiV58MdYo5rgmnyCsy0hHos VayQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=84JWi2OBZcSOio7NclvLKt6MrTR3N2JH6OWkdRqQYL8=; b=qFUnNi2qicR/eNWoxtDuzMdBa7gWAohuwq0fX0XX1M6xE+/rj3Yzodd/bdEuzdbvXV I17ROfBUsw8Z9NHdSbqiulm08i7272T0HUl8K00DgK6rZe6TUwi4UMY5JD6IfSg4LQyP PLXPWDoDSpqX8u/uGMlYpnepehq6FgAxD3gF4DiAu64kJpFG8WrJ+9S5qrCUTNdStJIj j1SFcbaZRXjDtaQ68RftjgXKyCoo/udPAsOvMtXb7Xz4dVGByvI8paOY4s2u9QqLuaM+ +EhIU1rW+1hxD2WEO54YB7DYnVjRUrNVrboGX1Tsz8It+sTF1b2YAmVcBLBBuBZ9Wyuf jzLQ== X-Gm-Message-State: AODbwcCL7NgqhOO33iGq/syIASAvApnnlYk7GC6pz9WgdRjq+bjidIhi aRQAnmQP1vdhu7vQR5fziz4fDcm1CLtC X-Received: by 10.28.10.6 with SMTP id 6mr2823164wmk.5.1495552681186; Tue, 23 May 2017 08:18:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.193.134 with HTTP; Tue, 23 May 2017 08:18:00 -0700 (PDT) In-Reply-To: <4422984a-ab73-f566-1bef-d7570489b44d@FreeBSD.org> References: <4422984a-ab73-f566-1bef-d7570489b44d@FreeBSD.org> From: Adrian Chadd Date: Tue, 23 May 2017 08:18:00 -0700 Message-ID: Subject: Re: Status of QCA9882 support? To: Lev Serebryakov Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 15:18:04 -0000 hiya, I still recommend sticking with the AR9280. The QCA988x 11ac stuff is coming, but I wouldn't at all recommend trying my driver out in hostap mode. It's a sufficiently different card (ie requires firmware API) that it requires a new driver. (Do buy one to do some local testing though!) I'm chipping away at it.. :-) -adrian On 23 May 2017 at 07:35, Lev Serebryakov wrote: > > I want to buy some new MiniPCIe WiFi adapters to make ny home network > dual-banded (now I'm using one SR71-E from Ubiquiti, which is 9280). > > Could I buy QCA9882-based card? Will it work right now with -CURRENT? I > don't speak about 802.11ac, 802.11n will be Ok right now, but can I > bought new hardware to have new standards in future, or should I buy > another 9280-based card? > > Thank you. > > -- > // Lev Serebryakov > From owner-freebsd-wireless@freebsd.org Tue May 23 17:28:05 2017 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 A3198D7A60C for ; Tue, 23 May 2017 17:28:05 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (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 7692C16CC for ; Tue, 23 May 2017 17:28:05 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [10.44.135.177] (nat-192-187-90-116.nat.tribpub.com [192.187.90.116]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id bb0964f6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 23 May 2017 10:28:04 -0700 (PDT) To: "freebsd-wireless@freebsd.org" From: Pete Wright Subject: Panic On Restarting netif Message-ID: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> Date: Tue, 23 May 2017 10:28:02 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 17:28:05 -0000 This morning I was restarting netif on my system running the drm-next branch off of CURRENT and experienced a kernel panic. My system has the following wireless NIC: iwm0@pci0:1:0:0: class=0x028000 card=0x44108086 chip=0x31658086 rev=0x79 hdr=0x00 vendor = 'Intel Corporation' device = 'Wireless 3165' class = network Here is what I think is the relevant section from the core.txt file that was generated: Unread portion of the kernel message buffer: MCA: Bank 6, Status 0xfe00000000801136 MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error MCA: Address 0xaa000000 MCA: Misc 0x30e2000086 vt_kms_postswitch() at vt_kms_postswitch+0x52/frame 0xfffffe034114cfb0 vt_window_switch() at vt_window_switch+0xdb/frame 0xfffffe034114cff0 vtterm_cngrab() at vtterm_cngrab+0x20/frame 0xfffffe034114d010 cngrab() at cngrab+0x42/frame 0xfffffe034114d030 vpanic() at vpanic+0x10a/frame 0xfffffe034114d0b0 panic() at panic+0x43/frame 0xfffffe034114d110 mca_intr() at mca_intr+0xab/frame 0xfffffe034114d130 trap() at trap+0xc0/frame 0xfffffe034114d2f0 calltrap() at calltrap+0x8/frame 0xfffffe034114d2f0 --- trap 0x1c, rip = 0xffffffff80394b74, rsp = 0xfffffe034114d3c8, rbp = 0xfffffe034114d420 --- rijndaelEncrypt() at rijndaelEncrypt+0x2a4/frame 0xfffffe034114d420 ccmp_decap() at ccmp_decap+0x480/frame 0xfffffe034114d540 The wireless network I was joining has the following wpa_supplicant config: network={ ssid="XXXX" #+ any_bssid key_mgmt=WPA-EAP proto=RSN eap=PEAP identity="homer@simpson" password="doh!" eap_workaround=1 } I can post the backtrace or other data if needed. This is the first time I've seen this error, so I'm not sure I'll be able to easily reproduce. Also, if this isn't a known issue and is probably related to wireless I can open a PR. Cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-wireless@freebsd.org Tue May 23 17:43:42 2017 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 08738D7ADC1 for ; Tue, 23 May 2017 17:43:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5E56113A1 for ; Tue, 23 May 2017 17:43:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA27671; Tue, 23 May 2017 20:43:33 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dDDqH-000Epm-MY; Tue, 23 May 2017 20:43:33 +0300 Subject: Re: Panic On Restarting netif To: Pete Wright , "freebsd-wireless@freebsd.org" References: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> From: Andriy Gapon Message-ID: Date: Tue, 23 May 2017 20:42:57 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 17:43:42 -0000 On 23/05/2017 20:28, Pete Wright wrote: > MCA: Bank 6, Status 0xfe00000000801136 > MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 > MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 > MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. The CPU might have started dying. > MCA: Address 0xaa000000 > MCA: Misc 0x30e2000086 -- Andriy Gapon From owner-freebsd-wireless@freebsd.org Tue May 23 17:45:31 2017 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 C7228D7AE65 for ; Tue, 23 May 2017 17:45:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (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 AE8E6145E; Tue, 23 May 2017 17:45:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [10.44.135.177] (nat-192-187-90-116.nat.tribpub.com [192.187.90.116]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3477e886 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 23 May 2017 10:45:30 -0700 (PDT) Subject: Re: Panic On Restarting netif To: Andriy Gapon , "freebsd-wireless@freebsd.org" References: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> From: Pete Wright Message-ID: <1f7f1692-12be-451e-d9f6-995a70476651@nomadlogic.org> Date: Tue, 23 May 2017 10:45:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 23 May 2017 17:45:31 -0000 On 05/23/2017 10:42, Andriy Gapon wrote: > On 23/05/2017 20:28, Pete Wright wrote: >> MCA: Bank 6, Status 0xfe00000000801136 >> MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 >> MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 >> MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error > This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. > The CPU might have started dying. > I hope that's not the case, this is a new Kabylake system :( Time to run extended BIOS diagnostics over lunch. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-wireless@freebsd.org Wed May 24 08:59:58 2017 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 B7780D7B2D4 for ; Wed, 24 May 2017 08:59:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0D7951BF3 for ; Wed, 24 May 2017 08:59:57 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA29730; Wed, 24 May 2017 11:59:54 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dDS94-000FeU-Ne; Wed, 24 May 2017 11:59:54 +0300 Subject: Re: Panic On Restarting netif To: Pete Wright , "freebsd-wireless@freebsd.org" References: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> <1f7f1692-12be-451e-d9f6-995a70476651@nomadlogic.org> From: Andriy Gapon Message-ID: <4bf0fc74-527d-d7cb-1eba-4fedc360b67b@FreeBSD.org> Date: Wed, 24 May 2017 11:58:33 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <1f7f1692-12be-451e-d9f6-995a70476651@nomadlogic.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 24 May 2017 08:59:58 -0000 On 23/05/2017 20:45, Pete Wright wrote: > > > On 05/23/2017 10:42, Andriy Gapon wrote: >> On 23/05/2017 20:28, Pete Wright wrote: >>> MCA: Bank 6, Status 0xfe00000000801136 >>> MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 >>> MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 >>> MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error >> This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. >> The CPU might have started dying. >> > > I hope that's not the case, this is a new Kabylake system :( The hope could be that this was a one-time glitch (proverbial cosmic ray). Machine Check Architecture is designed to report hardware problems. -- Andriy Gapon From owner-freebsd-wireless@freebsd.org Wed May 24 21:26:06 2017 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 05D6DD7C95E for ; Wed, 24 May 2017 21:26:06 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (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 D5D3F1525; Wed, 24 May 2017 21:26:05 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5a6d2be6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 24 May 2017 14:26:04 -0700 (PDT) Subject: Re: Panic On Restarting netif To: Andriy Gapon , "freebsd-wireless@freebsd.org" References: <98a7a7a7-0227-385f-4cee-87f352490345@nomadlogic.org> <1f7f1692-12be-451e-d9f6-995a70476651@nomadlogic.org> <4bf0fc74-527d-d7cb-1eba-4fedc360b67b@FreeBSD.org> From: Pete Wright Message-ID: <0ddbbce7-1ab4-52fb-4473-8b334092fcd9@nomadlogic.org> Date: Wed, 24 May 2017 14:26:03 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <4bf0fc74-527d-d7cb-1eba-4fedc360b67b@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 24 May 2017 21:26:06 -0000 On 05/24/2017 01:58, Andriy Gapon wrote: > On 23/05/2017 20:45, Pete Wright wrote: >> >> On 05/23/2017 10:42, Andriy Gapon wrote: >>> On 23/05/2017 20:28, Pete Wright wrote: >>>> MCA: Bank 6, Status 0xfe00000000801136 >>>> MCA: Global Cap 0x0000000000000c08, Status 0x0000000000000005 >>>> MCA: Vendor "GenuineIntel", ID 0x806e9, APIC ID 2 >>>> MCA: CPU 2 UNCOR PCC OVER DCACHE L2 DRD error >>> This looks like an uncorrectable [hardware] error in the CPU2 L2 cache. >>> The CPU might have started dying. >>> >> I hope that's not the case, this is a new Kabylake system :( > The hope could be that this was a one-time glitch (proverbial cosmic ray). > Machine Check Architecture is designed to report hardware problems. cheers - thanks for pointing that logline out btw! i was so focused on the following lines i missed the MCA lines. d'oh! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-wireless@freebsd.org Fri May 26 02:39:54 2017 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 4EE76D82116 for ; Fri, 26 May 2017 02:39:54 +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 3E9A91B3A for ; Fri, 26 May 2017 02:39:54 +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 v4Q2dra0023358 for ; Fri, 26 May 2017 02:39:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213237] [ndis][patch] ndis wireless ieee80211 communication failure Date: Fri, 26 May 2017 02:39:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ota@j.email.ne.jp X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: glebius@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.23 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, 26 May 2017 02:39:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213237 --- Comment #10 from ota@j.email.ne.jp --- I tested my laptop with NDIS with the latest 12-CURRENT and confirmed worki= ng. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-wireless@freebsd.org Sat May 27 03:27:54 2017 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 752DED840F1 for ; Sat, 27 May 2017 03:27:54 +0000 (UTC) (envelope-from kusanagiyang@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::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 0E3B91E46 for ; Sat, 27 May 2017 03:27:54 +0000 (UTC) (envelope-from kusanagiyang@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id z52so10336151wrc.2 for ; Fri, 26 May 2017 20:27:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UWUKwTiOZvW6ewWtDfTJPiZkplE2BbzwL3N0cbukhrY=; b=caEaTwBz+/Nlh9WPzl5RG3cZTdP+3n4EAx2ghPFJcAf+aLpEdkfTvry0JV5Su1ddBZ +W8vDb8L5VWeEmxBJUpoCKtPJ275IydFt124GvCRXXoqlQrvQoH18UNCideim7cm7kI0 4G6VQpJS0kv9C80JW+knummudRSi+Lk7ZsQKnEpD2Ky6t5ZypfeeNyed66cBv+6jOvG4 MC12WYxx9UdRQpcim0eEktwNMXp3c7XrbbvrEa372Ds2yQhoMUc6vh4T+nnNiV+5/IWq 5zFS4VhbSmy0nayT4UVWd8/Hcz0TjbQtwBlUbfo6TznV08bk5CFlVFUId8Ydkm5B9Y7j 1YRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UWUKwTiOZvW6ewWtDfTJPiZkplE2BbzwL3N0cbukhrY=; b=AIApHB8mlIxkHEOpKW9SJcMSWp0OALcKdjrbZbIUeY4ARCt77YHcrSvAz3Bd3Xw4+j NmblB3QyXKLlGg80Q2rGOtJtjhshUIH6zxm17Xc2G/S/S1fmkn4T3LDBEsBzBLAoSiCv n2wE7R29L5g8eK+k3NDAfXEMxpfUQfvSecV+f9bnTTi/CNBK9zIEri3WOJyYE96udV+f 7RFVk6zMiagHqu7IHgHfjef4Omrfj1ojIxtG2Jf+X/Wv4F77O6H4faSAwAOz1Hl7tDAh nf2jH2WzmzeoKk8ZYD9+2nt7qKI4QMXMWQSj2GIYi6G82DuQGipnm0SBflentKjh05/7 AbAA== X-Gm-Message-State: AODbwcARvUtKXMtZrvltMOQteW2xDkOmrZslvz72U/ghuur0A2yV/odh 1pruvl01qxbtEsgpyGaYJyCWr+Z06liL X-Received: by 10.223.134.80 with SMTP id 16mr4124499wrw.62.1495855672349; Fri, 26 May 2017 20:27:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.49.138 with HTTP; Fri, 26 May 2017 20:27:51 -0700 (PDT) From: Richard Yang Date: Sat, 27 May 2017 11:27:51 +0800 Message-ID: Subject: Re: BCM4321 wireless card To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 27 May 2017 03:27:54 -0000 Hello, Thank you for the great work on broadcom's wireless cards. I have a bunch of BCM4321 and it works!! In addition to the procedures that you described, I needed to compile bwn-firmware-kmod to produce bwn_v4_ucode.ko and bwn_v4_n_ucode.ko on my freebsd 11.0 release. I am curious though why bwn0 keeps saying "RX dexryption attempted (old 0 keyidx 0x1)" =E2=80=8Band also, bwn0 is not shown with ifconfig... =E2=80=8Bmy other w= ifi card, AR242x, does show up as ath0 with ifconfig, so I was really surprised when bwn0 began to work. Is this normal? I would like to learn more. thank yo= u --=20 Warm Regards Richard Yang kusanagiyang@gmail.com kusanagiyang@yahoo.com From owner-freebsd-wireless@freebsd.org Sat May 27 03:38:05 2017 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 B7A6FD84725 for ; Sat, 27 May 2017 03:38:05 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 70A3214E3 for ; Sat, 27 May 2017 03:38:05 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-ua0-x230.google.com with SMTP id u10so14679309uaf.1 for ; Fri, 26 May 2017 20:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CbM2B6lPqrPslwvJyMfOg8nFj3gsqW/EkO44aACXCeg=; b=XWYiXG/4O6UEyNKZ7tdXg/Lf/TITBcrsRwzizCyK8hXeuNSzz6Y9FI/VmnWZHQG3zU EG45Tbb9+zvzn5K5SH0fvTuO0gw6zmOE4T5sKlQ8JwTmcqmB2qoDcjUzZBi0FY/WzOsz rH15s+0p6T3p3n7r8oLp2wVkpxkAzddYVWtU+OBtYyXWHFDx+A/eVJJe7L8mRsfV7Iu1 5J+KTzs20ccMbhClxK9sD4anE+7J0yefJhQ9jOrSfdmWcl7q1AdmJCDTieX9496glAh2 XAX0iwnoyDJ9RlCOJuNIuk65qFHs/8DrCD++jKVkawmP2OMhbDlw5q+pmVsNV4gaoeXX 4vbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CbM2B6lPqrPslwvJyMfOg8nFj3gsqW/EkO44aACXCeg=; b=SGwhz+uEh9xB8f84XEnkpxnXlCRP/Prm6toapPyQw5L19iF8vQIKJwNZ5Pa1KB/wY2 He/z09JLBq46U7C4/5QbeJ+4GaITYbrOTPpdMAqRmcT7/nPq4N9xQ3Za4Wl/UlzP4Cdy 5035vsE6W8DHeXJZUJeqGG9785kwdfn2BsK76edYYBGkkP8+fbz5ea1LGrYhzO09cKOz mdvQcxEYxqsEbNWkP5JOz+ws4rFXQTV9WWoCESzm1G1u3hEHhE8X1LSgBU2wNTYTUuVo dC8lVoaSSlVkhycueow6B7Qsz6bdeeFOuvNJx44138gwwBUm0+ZglS5Z/goU/Mvu6GQy QVgw== X-Gm-Message-State: AODbwcDrGp79U2hQv+pAjzobAYuk4i7vNKcUfYSF2gQ7LUjIZCmt/Ejd XLG7ij4snWrxe6Ixynv8pP1Cb8AYkCzpGiI= X-Received: by 10.176.84.212 with SMTP id q20mr2358132uaa.103.1495856284555; Fri, 26 May 2017 20:38:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.166.22 with HTTP; Fri, 26 May 2017 20:38:04 -0700 (PDT) In-Reply-To: References: From: Michael Zhilin Date: Sat, 27 May 2017 06:38:04 +0300 Message-ID: Subject: Re: BCM4321 wireless card To: Richard Yang Cc: freebsd-wireless Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 27 May 2017 03:38:05 -0000 Hi, Starting with freebsd 11.0-release, please use "sysctl net.wlan.devices" to list active wifi devices. To connect to WiFi network, you still can "ifconfig wlan0 create wlandev bwn0" and proceed further steps with wpa_supplicant. Thanks, Michael. On Sat, May 27, 2017 at 6:27 AM, Richard Yang wrote: > Hello, > > Thank you for the great work on broadcom's wireless cards. I have a bunc= h > of BCM4321 and it works!! > In addition to the procedures that you described, I needed to compile > bwn-firmware-kmod to produce bwn_v4_ucode.ko and bwn_v4_n_ucode.ko on my > freebsd 11.0 release. > I am curious though why bwn0 keeps saying "RX dexryption attempted (old 0 > keyidx 0x1)" > =E2=80=8Band also, bwn0 is not shown with ifconfig... =E2=80=8Bmy other= wifi card, > AR242x, does show up as ath0 with ifconfig, so I was really surprised whe= n > bwn0 began to work. Is this normal? I would like to learn more. thank > you > > -- > Warm Regards > > Richard Yang > kusanagiyang@gmail.com > kusanagiyang@yahoo.com > _______________________________________________ > 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 > "