Re: ping6 -> lowpan0 -> wpan0. Ping6 doesn't succeed to send messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2015-07-15 16:34 GMT+02:00 Baptiste Clenet <bapclenet@xxxxxxxxx>:
> 2015-07-15 9:13 GMT+02:00 Alexander Aring <alex.aring@xxxxxxxxx>:
>> Hi,
>>
>> adding missed cc.
>>
>> On Wed, Jul 15, 2015 at 09:12:14AM +0200, Alexander Aring wrote:
>>> On Tue, Jul 14, 2015 at 11:22:32PM +0200, Baptiste Clenet wrote:
>>> ...
>>> >
>>> > Kind of a backtrace (printk at each beginning of a function)
>>> > root@OpenWrt:/# ip link set lowpan0 up
>>> > [  214.708111] lowpan_header_create
>>> > [  214.714520] lowpan_xmit
>>> > [  214.719378] lowpan_header
>>> > [  214.724569] tx.c dev_queue_xmit
>>> > [  214.730795] at86rf230_xmit_start
>>> > [  214.737669] at86rf230_write_frame
>>> > [  214.745539] at86rf230_write_frame_complete
>>> > [  214.828082] lowpan_header_create
>>> > [  214.834484] lowpan_xmit
>>> > [  214.839334] lowpan_header
>>> > [  214.844523] tx.c dev_queue_xmit
>>> > [  215.368119] lowpan_header_create
>>> > [  215.374529] lowpan_xmit
>>> > [  215.379398] lowpan_header
>>> > [  215.384589] tx.c dev_queue_xmit
>>> > [  216.368196] lowpan_header_create
>>> > [  216.374604] lowpan_xmit
>>> > [  216.379468] lowpan_header
>>> > [  216.384658] tx.c dev_queue_xmit
>>> > [  216.390934] lowpan_header_create
>>> > [  216.397319] lowpan_xmit
>>> > [  216.402168] lowpan_header
>>> > [  216.407351] tx.c dev_queue_xmit
>>> > [  216.898090] lowpan_header_create
>>> >
>>> >     [  216.904496] lowpan_xmit
>>> >
>>> >                  [  216.909350] lowpan_header
>>> > [  216.914539] tx.c dev_queue_xmit
>>> > [  216.978063] lowpan_header_create
>>> > [  216.984464] lowpan_xmit
>>> > [  216.989312] lowpan_header
>>> > [  216.994498] tx.c dev_queue_xmit
>>> >
>>> > You see that at86rf230_xmit_start is called only once so I seems
>>> > logical that while doing a ping6, it's not called as well.
>>>
>>> I maybe know what happens here.
>>>
>>> You transmit only one frame at beginning, this occurs that the netdev
>>> queue will be stopped -> The driver layer doesn't get new "send a frame",
>>> the xmit callback.
>>>
>>> This happens once, then the queue is stopped on the "tx completion
>>> interrupt" we awake the queue again. -> The driver layer can send a
>>> frame again.
>>>
>>> It seems for me that you don't get any irq, instrument please the function:
>>>
>>> at86rf230_isr
> No call for isr but most of all, no irq on the irq line. polarity set
> to 0 (reg 0x04), TRX enable (reg 0x0E)
> This is definitely the problem
>
>>>
>>> and check
>>>
>>> cat /proc/interrupts
> Yes the spi int is defined
>  23:          0      INTC  15  spi32765.0
> Why 23 on the left and 15 ont the right?
>
>>>
>>> if you see that the at86rf230 driver gets any interrupt. If not check
>>> your irq settings.
>>>
>>> - Alex
>
>
>
> --
> Baptiste

By the way, I'm using the 212B

-- 
Baptiste
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux