Hm, do you have ATH_ENABLE_11N in your kernel config?


adrian


On 17 June 2013 12:04, Peter Ankerstål <pe...@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-0xa301ffff 
> irq 17 at device 0.0 on pci7
> Jun 17 20:20:47 gw kernel: ar9300_set_stub_functions: setting stub functions
> Jun 17 20:20:47 gw kernel: ar9300_set_stub_functions: setting stub functions
> 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 returned 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=0, FIFO depth = 
> 16 entries
> Jun 17 20:20:47 gw kernel: ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 
> 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
> …..
> 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=24, nbufs=128?
> 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=0, nbufs=128?
> 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=8, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=21, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=13, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=24, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=11, nbufs=128?
> 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=0, nbufs=128?
> 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=9, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=9, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=12, nbufs=128?
> 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=0, nbufs=128?
> 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=0, nbufs=128?
> 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=11, nbufs=128?
> 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=0, nbufs=128?
> …
> 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 
> kernel 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 = 0; apic id = 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  = 0x20:0xc0565c8c
> Jun 17 20:20:47 gw kernel: stack pointer                = 0x28:0xc47d9afc
> Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: 
> i=0, nbufs=128?
> Jun 17 20:20:47 gw kernel: frame pointer                = 0x28:0xc47d9b28
> Jun 17 20:20:47 gw kernel: code segment         = base 0x0, limit 0xfffff, 
> type 0x1b
> Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!
> Jun 17 20:20:47 gw kernel: = DPL 0, pres 1, def32 1, gran 1
> Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: 
> i=0, nbufs=128?
> Jun 17 20:20:47 gw kernel: processor eflags     = interrupt enabled, ath0: 
> ath_edma_rxbuf_alloc: nothing on rxbuf?!
> Jun 17 20:20:47 gw kernel: resume, IOPL = 0
> Jun 17 20:20:47 gw kernel: ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: 
> i=9, nbufs=128?
> Jun 17 20:20:47 gw kernel: current process              = 12 (swi4: clock)
> Jun 17 20:20:47 gw kernel: trap number          = 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 = 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+0xaa
> 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 <adr...@freebsd.org> wrote:
>
>> Nope, not unless someone backports it all!
>>
>>
>> adrian
>>
>>
>> On 14 June 2013 04:33, Peter Ankerstål <pe...@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 <adr...@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.html
>>>
>>> Will I be able to use this in FreeBSD 9?
>>
>
>
_______________________________________________
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to