From: Baptiste Clenet <bapclenet@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: ping6 -> lowpan0 -> wpan0. Ping6 doesn't succeed to send messages
Date: Wed, 15 Jul 2015 16:34:09 +0200 [thread overview]
Message-ID: <CAPpUg6MmQ2KJe1XJmkv+q0L-+pQkbmh1NdBvpNY6nH=KTKXQRQ@mail.gmail.com> (raw)
In-Reply-To: <20150715071339.GB5680@omega>
2015-07-15 9:13 GMT+02:00 Alexander Aring <alex.aring@gmail.com>:
> 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
next prev parent reply other threads:[~2015-07-15 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 14:59 ping6 -> lowpan0 -> wpan0. Ping6 doesn't succeed to send messages Baptiste Clenet
2015-07-13 16:18 ` Baptiste Clenet
2015-07-13 17:48 ` Alexander Aring
2015-07-14 10:56 ` Baptiste Clenet
2015-07-14 17:45 ` Baptiste Clenet
2015-07-14 18:11 ` Alexander Aring
2015-07-14 21:18 ` Baptiste Clenet
2015-07-14 21:50 ` Baptiste Clenet
[not found] ` <CAPpUg6Odxw1F6+3frQibxtORaUic0M1F_9rGdY6RWZK1uaM17Q@mail.gmail.com>
[not found] ` <20150715071214.GA5680@omega>
2015-07-15 7:13 ` Alexander Aring
2015-07-15 14:34 ` Baptiste Clenet [this message]
2015-07-15 14:37 ` Baptiste Clenet
2015-07-15 17:48 ` Alexander Aring
2015-07-21 6:52 ` Baptiste Clenet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPpUg6MmQ2KJe1XJmkv+q0L-+pQkbmh1NdBvpNY6nH=KTKXQRQ@mail.gmail.com' \
--to=bapclenet@gmail.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.