From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f54.google.com ([209.85.215.54]:33249 "EHLO mail-la0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752021AbbGOOeL (ORCPT ); Wed, 15 Jul 2015 10:34:11 -0400 Received: by laem6 with SMTP id m6so25908057lae.0 for ; Wed, 15 Jul 2015 07:34:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20150715071339.GB5680@omega> References: <20150713174807.GA3056@omega> <20150714181114.GA3113@omega> <20150715071214.GA5680@omega> <20150715071339.GB5680@omega> Date: Wed, 15 Jul 2015 16:34:09 +0200 Message-ID: Subject: Re: ping6 -> lowpan0 -> wpan0. Ping6 doesn't succeed to send messages From: Baptiste Clenet Content-Type: text/plain; charset=UTF-8 Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Alexander Aring Cc: linux-wpan@vger.kernel.org 2015-07-15 9:13 GMT+02:00 Alexander Aring : > 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