Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Matteo Petracca <matteo.petracca@sssup.it>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Ieee802154 socket problem with SIOCGIFADDR
Date: Tue, 12 May 2015 11:48:36 +0200	[thread overview]
Message-ID: <5551CC74.60702@sssup.it> (raw)
In-Reply-To: <20150512083917.GC733@omega>

You were right, I did not remove the Assertion.

Now the patch is all there and the modules are
updated.

What happens now is a strange behaviour, booting
the system I just turn on the wpan interface putting
as panid 0xaaaa:

ifconfig wpan0 up

the device starts to read from the network, and this is
what I have in output with dmesg is:

[  131.445285] ieee802154: bad frame received (type = 3)
[  133.777933] ieee802154: bad frame received (type = 3)
[  136.110635] ieee802154: bad frame received (type = 3)
[  148.318471] ieee802154: bad frame received (type = 3)
[  150.651288] ieee802154: bad frame received (type = 3)
[  152.984910] ieee802154: bad frame received (type = 3)
[  165.195277] ieee802154: bad frame received (type = 3)
[  167.527936] ieee802154: bad frame received (type = 3)
[  169.860422] ieee802154: bad frame received (type = 3)
[  182.071635] ieee802154: bad frame received (type = 3)
[  184.406857] ieee802154: bad frame received (type = 3)
[  186.739487] ieee802154: bad frame received (type = 3)
[  198.947054] ieee802154: bad frame received (type = 3)
[  201.279710] ieee802154: bad frame received (type = 3)
[  203.612262] ieee802154: bad frame received (type = 3)
[  215.819843] ieee802154: bad frame received (type = 3)
[  218.155852] ieee802154: bad frame received (type = 3)
[  220.488465] ieee802154: bad frame received (type = 3)

Moreover SIOCGIFADDR still does not work.

Sorry for bothering you.

I don't know what to think.

Matteo

On 12/05/2015 10:39, Alexander Aring wrote:
> On Tue, May 12, 2015 at 10:32:57AM +0200, Matteo Petracca wrote:
>> I've applied your patch properly.
>>
>> By using your example this is what I have with kernel 4.0.2 for
>> beagleboneblack
>>
>> [   44.362497] NET: Registered protocol family 36
>> [   44.369646] RTNL: assertion failed at net/mac802154/iface.c (65)
> can't be. The patch removes the RTNL assertion. Please check if you
> really rebuild and update your kernel/modules.
>
> Maybe try `uname -a` and check kernels build date/git HEAD id/whatever.
>
> - Alex
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2015-05-12  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 14:41 Ieee802154 socket problem with SIOCGIFADDR Matteo Petracca
2015-05-09 16:42 ` Alexander Aring
2015-05-11 16:43   ` Matteo Petracca
2015-05-11 16:51     ` Alexander Aring
2015-05-11 16:58       ` Matteo Petracca
2015-05-11 17:29         ` Alexander Aring
2015-05-11 17:37       ` Alexander Aring
2015-05-11 17:51     ` Alexander Aring
2015-05-12  8:32       ` Matteo Petracca
2015-05-12  8:39         ` Alexander Aring
2015-05-12  9:48           ` Matteo Petracca [this message]
2015-05-12 10:33             ` Alexander Aring

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=5551CC74.60702@sssup.it \
    --to=matteo.petracca@sssup.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox