From owner-freebsd-stable@freebsd.org Sun Apr 1 16:25:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 403F3F6AF60 for ; Sun, 1 Apr 2018 16:25:26 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C39C073074 for ; Sun, 1 Apr 2018 16:25:25 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id 1E0586002F3 for ; Sun, 1 Apr 2018 18:25:23 +0200 (CEST) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAPh90UkPA-Z for ; Sun, 1 Apr 2018 18:25:12 +0200 (CEST) Received: from elch.exwg.net (elch.exwg.net [IPv6:2001:470:7120:1:127b:44ff:fe4f:148d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "elch.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS for ; Sun, 1 Apr 2018 18:25:12 +0200 (CEST) Received: by elch.exwg.net (Postfix, from userid 1000) id DF2A327323; Sun, 1 Apr 2018 18:25:11 +0200 (CEST) Date: Sun, 1 Apr 2018 18:25:11 +0200 From: Christoph Moench-Tegeder To: freebsd-stable@freebsd.org Subject: Panic with Dual-Band WLANs on ath Message-ID: <20180401162511.GA52648@elch.exwg.net> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Apr 2018 16:25:26 -0000 Hi, I've got a fairly reproducable kernel panic when trying to configure two wlan devices on one ath card. The basics: FreeBSD 11.1-RELEASE-p8 amd64 ath0@pci0:4:0:0: class=0x028000 card=0x3099168c chip=0x002a168c rev=0x01 hdr=0x00 vendor = 'Qualcomm Atheros' device = 'AR928X Wireless Network Adapter (PCI-Express)' class = network (This is a Compex WLE200NX miniPCIe card in a PCEngines APU2: https://www.compex.com.sg/product/wle200nx/ for specifications). I want to create two access points on this device: one in 5Ghz and one in 2.4GHz (5GHz gives good bandwidth, but cannot radio it's way out of a cardboard box, so rather less-than-good coverage - and I still have hardware which is not 5GHz capable; 2.4GHz has less bandwidth but much better coverage (this is also true for my neighbours' networks, so I've got quite some interference here)). The naive approach was setting wlans_ath0="wlan0 wlan1" in rc.conf, and configuring wlan0 and wlan1 in parallel (hostap and stuff). Unfortunately, after short time (30 seconds to 5 minutes), I get a kernel panic: ath0: ath_rate_tx_complete: ts_rate=11 ts_finaltsi=0, final_rix=4 ath0: bad series0 hwrate 0xb, tries 7 ts_status 0x1 Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff8164aefc stack pointer = 0x28:0xfffffe011bbfe8a0 frame pointer = 0x28:0xfffffe011bbfe8f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (irq40: ath0) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: #0 0xffffffff80585997 at kdb_backtrace+0x67 #1 0xffffffff80543a76 at vpanic+0x186 #2 0xffffffff805438e3 at panic+0x43 #3 0xffffffff8087c642 at trap_fatal+0x322 #4 0xffffffff8087c69b at trap_pfault+0x4b #5 0xffffffff8087beba at trap+0x2ca #6 0xffffffff8085ed20 at calltrap+0x8 #7 0xffffffff814e25c5 at ath_beacon_generate+0x45 #8 0xffffffff814e244b at ath_beacon_proc+0x22b #9 0xffffffff814d066d at ath_intr+0x24d #10 0xffffffff8050a0bc at intr_event_execute_handlers+0xec #11 0xffffffff8050a3a6 at ithread_loop+0xd6 #12 0xffffffff80507715 at fork_exit+0x85 #13 0xffffffff8085f9ee at fork_trampoline+0xe I can provide core dumps on request. Is this a case of "don't do that"? In that case, an error message instead of a kernel panic would be nice - it took me several roundtrips to disable the wlans again, the box sometimes paniced faster than I could fix my configuration. For the time being I'm back to 2.4GHz only (which worked for several days, as did 5GHz only - only the combination got my box panicing). Any ideas? Regards, Christoph -- Spare Space