UDP results in a hard fault (iotlab-m3) #3815
Description
I was testing on the iotlab testbed multi hop UDP with the following configuration:
m3-190;ifconfig 7 add abcd::190
m3-195;ifconfig 7 add abcd::195
m3-205;ifconfig 7 add abcd::205
m3-190;fibroute add :: via fe80::195
m3-195;fibroute add :: via fe80::205
m3-195;fibroute add abcd::190 via fe80::190
m3-205;fibroute add abcd::195 via fe80::195
m3-205;fibroute add abcd::190 via fe80::195
udp server start 1337
Issuing the following command:
m3-205;udp send abcd::190 1337 hey
Results in the following message:
m3-205;udp send abcd::190 1337 hey
1441915054.206381;m3-205;> udp send abcd::190 1337 hey
1441915054.208265;m3-205;Success: send 3 byte to abcd::190:1337
1441915054.217298;m3-190;> PKTDUMP: data received:
1441915054.217407;m3-190;~~ SNIP 0 - size: 3 byte, type: NETTYPE_UNDEF (0)
1441915054.217499;m3-190;000000 68 65 79
1441915054.218378;m3-190;~~ SNIP 1 - size: 8 byte, type: NETTYPE_UDP (4)
1441915054.219366;m3-190; src-port: 1337 dst-port: 1337
1441915054.220344;m3-190; length: 11 cksum: 0x4b8d0
1441915054.221388;m3-190;~~ SNIP 2 - size: 40 byte, type: NETTYPE_IPV6 (2)
1441915054.222358;m3-190;traffic class: 0x00 (ECN: 0x0, DSCP: 0x00)
1441915054.222462;m3-190;flow label: 0x00000
1441915054.223356;m3-190;length: 11 next header: 17 hop limit: 63
1441915054.225320;m3-190;source address: abcd::205
1441915054.225426;m3-190;destination address: abcd::190
1441915054.225513;m3-190;~~ SNIP 3 - size: 24 byte, type: NETTYPE_NETIF (-1)
1441915054.226082;m3-190;if_pid: 7 rssi: 18 lqi: 126
1441915054.227045;m3-190;src_l2addr: 36:32:48:33:46:de:8f:16
1441915054.227142;m3-190;dst_l2addr: 36:32:48:33:46:d8:7d:0a
1441915054.228033;m3-190;~~ PKT - 4 snips, total size: 75 byte
1441915054.228136;m3-190;
1441915054.229034;m3-190;Context before hardfault:
1441915054.229135;m3-190;r0: 0x20001930
1441915054.229220;m3-190;r1: 0x28
1441915054.230020;m3-190;r2: 0x4902b5
1441915054.230118;m3-190;r3: 0x4902b5
1441915054.230201;m3-190;r12: 0x2000184b
1441915054.231025;m3-190;lr : 0x80043fb
1441915054.231122;m3-190;pc : 0x80040fa
1441915054.231205;m3-190;psr: 0x81000000
1441915054.231287;m3-190;
1441915054.232018;m3-190;*** RIOT kernel panic
1441915054.232117;m3-190;HARD FAULT HANDLER
1441915054.234038;m3-190; pid | name | state Q | pri | stack ( used) | location
1441915054.235016;m3-190; 1 | idle | pending Q | 15 | 256 ( 140) | 0x20000230
1441915054.237028;m3-190; 2 | main | bl mutex _ | 7 | 1536 ( 708) | 0x20000330
1441915054.239011;m3-190; 3 | pktdump | running Q | 6 | 1536 ( 556) | 0x20002f58
1441915054.241029;m3-190; 4 | 6lo | bl rx _ | 3 | 1024 ( 408) | 0x2000355c
1441915054.242020;m3-190; 5 | ipv6 | bl rx _ | 4 | 1024 ( 488) | 0x20000e0c
1441915054.244045;m3-190; 6 | udp | bl rx _ | 5 | 1024 ( 316) | 0x20003b38
1441915054.246007;m3-190; 7 | at86rfxx | bl rx _ | 3 | 1024 ( 360) | 0x200009cc
1441915054.247019;m3-190; | SUM | | | 7424 ( 2976)
1441915054.247125;m3-190;
1441915054.247214;m3-190;*** halted.
Ping works like a charm. It's just UDP that fails AFAICT.
Can somebody with proper hardware investigate further?