Date: Mon, 17 Jun 2013 12:07:06 -0700 From: Adrian Chadd <adrian@freebsd.org> To: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= <peter@pean.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Support for Mini PCie card WLE300NX( (AR9380) Message-ID: <CAJ-VmonQakJE260_8eWdTz7eLXU-qB3Qjw7pOq%2Bv=bg6Mftcdw@mail.gmail.com> In-Reply-To: <6D354DC2-3D2E-441E-ABCF-8C024937ACDF@pean.org> References: <511E30FF.4050404@pean.org> <CAJ-VmonVXokD9XfY6iNz8OeSLeFjqVUgKArpcnQcj-zSXtPZCQ@mail.gmail.com> <CAJ-VmonANUT4ULhwTpZbnqP=YU=u5Nb6c9uYOW3b=NEM1=Ab=A@mail.gmail.com> <51BAFF95.6090402@pean.org> <CAJ-VmomXX_LvfFR6Fp35wa2UmcE=F3ov4sMjL_vZo=iZu_Kecg@mail.gmail.com> <6D354DC2-3D2E-441E-ABCF-8C024937ACDF@pean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hm, do you have ATH_ENABLE_11N in your kernel config? adrian On 17 June 2013 12:04, Peter Ankerst=E5l <peter@pean.org> wrote: > Hi! > > I just upgraded to 10.0. > > FreeBSD gw 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Mon Jun 17 09:56:13 CEST= 2013 root@gw:/usr/obj/usr/src/sys/SOEKRIS i386 > > Jun 17 20:20:47 gw kernel: ath0: <Atheros AR938x> mem 0xa3000000-0xa301ff= ff irq 17 at device 0.0 on pci7 > Jun 17 20:20:47 gw kernel: ar9300_set_stub_functions: setting stub functi= ons > Jun 17 20:20:47 gw kernel: ar9300_set_stub_functions: setting stub functi= ons > Jun 17 20:20:47 gw kernel: ar9300_attach: calling ar9300_hw_attach > Jun 17 20:20:47 gw kernel: ar9300_hw_attach: calling ar9300_eeprom_attach > Jun 17 20:20:47 gw kernel: ar9300_flash_map: unimplemented for now > Jun 17 20:20:47 gw kernel: Restoring Cal data from DRAM > Jun 17 20:20:47 gw kernel: Restoring Cal data from EEPROM > Jun 17 20:20:47 gw kernel: ar9300_hw_attach: ar9300_eeprom_attach returne= d 0 > Jun 17 20:20:47 gw kernel: ath0: RX status length: 48 > Jun 17 20:20:47 gw kernel: ath0: RX buffer size: 4096 > Jun 17 20:20:47 gw kernel: ath0: TX descriptor length: 128 > Jun 17 20:20:47 gw kernel: ath0: TX status length: 36 > Jun 17 20:20:47 gw kernel: ath0: TX buffers per descriptor: 4 > Jun 17 20:20:47 gw kernel: ar9300_freebsd_setup_x_tx_desc: called, 0x0/0,= 0x0/0, 0x0/0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_setup_rxfifo: type=3D0, FIFO de= pth =3D 16 entries > Jun 17 20:20:47 gw kernel: ath0: ath_edma_setup_rxfifo: type=3D1, FIFO de= pth =3D 128 entries > Jun 17 20:20:47 gw kernel: ath0: AR9380 mac 448.3 RF5110 phy 132.15 > Jun 17 20:20:47 gw kernel: ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 > =85.. > Jun 17 20:20:47 gw kernel: ar9300_Stub_GetCTSTimeout: called > Jun 17 20:20:47 gw kernel: ar9300_Stub_GetCTSTimeout: called > Jun 17 20:20:47 gw kernel: ar9300_Stub_GetAntennaSwitch: called > Jun 17 20:20:47 gw kernel: ar9300_Stub_GetAntennaSwitch: called > Jun 17 20:20:47 gw kernel: bridge0: Ethernet address: 02:e8:ea:15:66:00 > Jun 17 20:20:47 gw kernel: bridge1: Ethernet address: 02:e8:ea:15:66:01 > Jun 17 20:20:47 gw kernel: wlan0: Ethernet address: 04:f0:21:01:3d:87 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D24, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D8, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D21, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D13, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: Q1: NULL bf? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_tasklet: sc_inreset_cnt > = 0; skipping > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: Q1: NULL bf? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D24, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D11, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D9, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D9, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D12, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D11, nbufs=3D128? > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > =85 > Jun 17 20:20:47 gw kernel: > Jun 17 20:20:47 gw kernel: > Jun 17 20:20:47 gw kernel: Fatal trap 18: integer divide fault while in k= ernel mode > Jun 17 20:20:47 gw kernel: ath0: ath_edma_recv_proc_queue: handled npkts = 0 > Jun 17 20:20:47 gw kernel: cpuid =3D 0; apic id =3D 00 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: instruction pointer =3D 0x20:0xc0565c8c > Jun 17 20:20:47 gw kernel: stack pointer =3D 0x28:0xc47d9a= fc > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: frame pointer =3D 0x28:0xc47d9b= 28 > Jun 17 20:20:47 gw kernel: code segment =3D base 0x0, limit 0xfff= ff, type 0x1b > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: =3D DPL 0, pres 1, def32 1, gran 1 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D0, nbufs=3D128? > Jun 17 20:20:47 gw kernel: processor eflags =3D interrupt enabled, at= h0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: resume, IOPL =3D 0 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed:= i=3D9, nbufs=3D128? > Jun 17 20:20:47 gw kernel: current process =3D 12 (swi4: clo= ck) > Jun 17 20:20:47 gw kernel: trap number =3D 18 > Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?! > Jun 17 20:20:47 gw kernel: panic: integer divide fault > Jun 17 20:20:47 gw kernel: cpuid =3D 0 > Jun 17 20:20:47 gw kernel: KDB: stack backtrace: > Jun 17 20:20:47 gw kernel: #0 0xc0789022 at kdb_backtrace+0x52 > Jun 17 20:20:47 gw kernel: #1 0xc0753b66 at panic+0x126 > Jun 17 20:20:47 gw kernel: #2 0xc0a3f649 at trap_fatal+0x339 > Jun 17 20:20:47 gw kernel: #3 0xc0a3f30a at trap+0x7da > Jun 17 20:20:47 gw kernel: #4 0xc0a2989c at calltrap+0x6 > Jun 17 20:20:47 gw kernel: #5 0xc0570590 at ar9300_ani_poll_freebsd+0x50 > Jun 17 20:20:47 gw kernel: #6 0xc05201d4 at ath_calibrate+0xf4 > Jun 17 20:20:47 gw kernel: #7 0xc0768616 at softclock_call_cc+0xe6 > Jun 17 20:20:47 gw kernel: #8 0xc07689d5 at softclock+0x75 > Jun 17 20:20:47 gw kernel: #9 0xc0726b1a at intr_event_execute_handlers+0= xaa > Jun 17 20:20:47 gw kernel: #10 0xc0726f53 at ithread_loop+0x113 > Jun 17 20:20:47 gw kernel: #11 0xc0724577 at fork_exit+0x67 > > Does this say anything to you? > > > > On Jun 14, 2013, at 7:49 PM, Adrian Chadd <adrian@freebsd.org> wrote: > >> Nope, not unless someone backports it all! >> >> >> adrian >> >> >> On 14 June 2013 04:33, Peter Ankerst=E5l <peter@pean.org> wrote: >>> On 02/16/2013 08:33 PM, Adrian Chadd wrote: >>>> >>>> Oops, I didn't reply in public! >>>> >>>> On 15 February 2013 09:03, Adrian Chadd <adrian@freebsd.org> wrote: >>>>> >>>>> Yup! I'm working on open sourcing the HAL side of things soon. >>>> >>>> >>>> I'm going through final code approval now. >>>> >>>> Then, of course, there's all this extra work required to get it >>>> somewhat validated - I have to write a bunch of testing routines to >>>> test TX power, TX and RX EVM (to make sure that things aren't >>>> distorting), fix up some of the shortcuts I've taken (eg making ANI >>>> work right), implement MSI interrupt handling, test whether 3-stream >>>> negotiation, TX and RX works correctly, make sure the STA timers are >>>> setup right, make sure the hostap timers are setup right, implement >>>> CABQ handling for hostap mode... >>>> >>>> .. yeah, there's still a lot of work to do. :-) >>>> >>>> But it's almost there. >>>> >>>> >>>> >>>> Adrian >>>> >>> >>> Ooops. Just found: >>> >>> http://lists.freebsd.org/pipermail/freebsd-wireless/2013-May/003274.htm= l >>> >>> Will I be able to use this in FreeBSD 9? >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonQakJE260_8eWdTz7eLXU-qB3Qjw7pOq%2Bv=bg6Mftcdw>