Erratic timings on iotlab-m3 with compression context activated #5405

miri64 · 2016-04-28T12:31:21Z

When using a compression context on iotlab-m3 nodes I get very weird long timings when pinging.

When applying the following patch to add the abcd::/64 prefix for context 0 (alternatively set-up a border router and use the 6ctx command, I just don't have enough iotlab-m3 boards left to do that and setting-up a border router on the IoT-Lab isn't possible right now):

diff --git a/examples/gnrc_networking/main.c b/examples/gnrc_networking/main.c
index 6301f42..7901ee7 100644
--- a/examples/gnrc_networking/main.c
+++ b/examples/gnrc_networking/main.c
@@ -22,6 +22,7 @@

 #include "shell.h"
 #include "msg.h"
+#include "net/gnrc/sixlowpan/ctx.h"

 #define MAIN_QUEUE_SIZE     (8)
 static msg_t _main_msg_queue[MAIN_QUEUE_SIZE];
@@ -43,6 +44,10 @@ int main(void)
     /* start shell */
     puts("All up, running the shell now");
     char line_buf[SHELL_DEFAULT_BUFSIZE];
+    ipv6_addr_t prefix = IPV6_ADDR_UNSPECIFIED;
+    prefix.u8[0] = 0xab;
+    prefix.u8[1] = 0xcd;
+    gnrc_sixlowpan_ctx_update(0, &prefix, 64, UINT16_MAX, true);
     shell_run(shell_commands, line_buf, SHELL_DEFAULT_BUFSIZE);

     /* should be never reached */

And configuring this prefix to the nodes:

m3-7;ifconfig 7 add abcd::3432:4833:46d4:7c2a
m3-9;ifconfig 7 add abcd::3432:4833:46d5:9d12
m3-7;fibroute add :: via fe80::3432:4833:46d5:9d12
m3-9;fibroute add :: via fe80::3432:4833:46d4:7c2a
m3-7;ping6 abcd::3432:4833:46d5:9d12

I get the following (with UDP the same is true, it is just not so nice to see as with pings):

1461845740.202873;m3-7;ping timeout
1461845740.204380;m3-7;dropping additional response packet (probably caused by duplicates)
1461845742.236271;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83 seq=2 hop limit=64 time = 1029.852 ms
1461845744.025064;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83 seq=3 hop limit=64 time = 787.174 ms
1461845744.025973;m3-7;--- abcd::3432:4833:46d5:9d12 ping statistics ---
1461845744.027849;m3-7;3 packets transmitted, 2 received, 34% packet loss, time 5.06351186 s
1461845744.028849;m3-7;rtt min/avg/max = 787.174/605.675/1029.852 ms

(the first 2 lines basically mean, that the ping came in after the time-out).

Without a compression context (normal release version) I get these timings:

1461845505.011304;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83 seq=1 hop limit=64 time = 10.415 ms
1461845506.022415;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83 seq=2 hop limit=64 time = 8.463 ms
1461845507.035214;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83 seq=3 hop limit=64 time = 9.131 ms
1461845507.035444;m3-7;--- abcd::3432:4833:46d5:9d12 ping statistics ---
1461845507.035702;m3-7;3 packets transmitted, 3 received, 0% packet loss, time 2.0633950 s
1461845507.036245;m3-7;rtt min/avg/max = 8.463/9.336/10.415 ms

which are comparable to the link-local pings so I would say "normal".

I wasn't able to reproduce this on samr21-xpro, so it might be a timer related issue (?) or maybe the optimization for Cortex M3 does something crazy that lets a simple array look-up (which the context lookup basically is) run incredibly long.

The text was updated successfully, but these errors were encountered:

miri64 · 2016-04-28T13:28:08Z

Here is a sniff (sorry different addresses, since it was a different experiment and since cloudshark now is a payed service I can't use it anymore, but you can obtain the dump here. The filter I used is wpan.src64 == 36:32:48:33:46:d5:aa:16 || wpan.src64 == 36:32:48:33:46:d8:aa:22)

The set-up was 3 times using ping6 without any extra parameters.

The time in-between pings is weirdly long (up to 3 seconds) and the time differences to the replies are similar to the latencies seen above, so it seems not just to be a problem on the pinging node.

kaspar030 · 2016-04-28T13:47:24Z

Hm, as the iot-lab seems to be running with 16bit timers, this might be
a manifestation of #5338.

Could you try to make the timer run a lot slower?

set the timer_init value in xtimer_init() (sys/xtimer/xtimer_core.c)
to something slower, e.g., change from 1000000lu to 125000lu (1/8th)
confirm that tests/xtimer_msg still works but with 1/8th of expected speed
confirm that ping without 6ctx shows values * 1/8th
see if the behaviour with 6ctx is different

Unfortunately I don't have an iotlab-m3 around. I tried above on samr21,
but it's periph timer only supports 1mhz.

On 04/28/2016 02:31 PM, Martine Lenders wrote:

When using a compression context on |iotlab-m3| nodes I get very weird
long timings when pinging.

When applying the following patch to add the |abcd::/64| prefix for
context 0 (alternatively set-up a border router and use the |6ctx|
command, I just don't have enough |iotlab-m3| boards left to do that and
setting-up a border router on the IoT-Lab isn't possible right now):

diff --git a/examples/gnrc_networking/main.c
b/examples/gnrc_networking/main.c
index 6301f42..7901ee7 100644
--- a/examples/gnrc_networking/main.c
+++ b/examples/gnrc_networking/main.c
@@ -22,6 +22,7 @@

#include "shell.h"
#include "msg.h"
+#include "net/gnrc/sixlowpan/ctx.h"

#define MAIN_QUEUE_SIZE (8)
static msg_t _main_msg_queue[MAIN_QUEUE_SIZE];
@@ -43,6 +44,10 @@ int main(void)
/* start shell */
puts("All up, running the shell now");
char line_buf[SHELL_DEFAULT_BUFSIZE];

ipv6_addr_t prefix = IPV6_ADDR_UNSPECIFIED;

prefix.u8[0] = 0xab;

prefix.u8[1] = 0xcd;

gnrc_sixlowpan_ctx_update(0, &prefix, 64, UINT16_MAX, true);
shell_run(shell_commands, line_buf, SHELL_DEFAULT_BUFSIZE);

/* should be never reached */

And configuring this prefix to the nodes:

|m3-7;ifconfig 7 add abcd::3432:4833:46d4:7c2a m3-9;ifconfig 7 add
abcd::3432:4833:46d5:9d12 m3-7;fibroute add :: via
fe80::3432:4833:46d5:9d12 m3-9;fibroute add :: via
fe80::3432:4833:46d4:7c2a m3-7;ping6 abcd::3432:4833:46d5:9d12 |

I get the following (with UDP the same is true, it is just not so nice
to see as with pings):

|1461845740.202873;m3-7;ping timeout 1461845740.204380;m3-7;dropping
additional response packet (probably caused by duplicates)
1461845742.236271;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83
seq=2 hop limit=64 time = 1029.852 ms 1461845744.025064;m3-7;12 bytes
from abcd::3432:4833:46d5:9d12: id=83 seq=3 hop limit=64 time = 787.174
ms 1461845744.025973;m3-7;--- abcd::3432:4833:46d5:9d12 ping statistics
--- 1461845744.027849;m3-7;3 packets transmitted, 2 received, 34% packet
loss, time 5.06351186 s 1461845744.028849;m3-7;rtt min/avg/max =
787.174/605.675/1029.852 ms |

(the first 2 lines basically mean, that the ping came in after the
time-out).

Without a compression context (normal release version) I get these timings:

|1461845505.011304;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83
seq=1 hop limit=64 time = 10.415 ms 1461845506.022415;m3-7;12 bytes from
abcd::3432:4833:46d5:9d12: id=83 seq=2 hop limit=64 time = 8.463 ms
1461845507.035214;m3-7;12 bytes from abcd::3432:4833:46d5:9d12: id=83
seq=3 hop limit=64 time = 9.131 ms 1461845507.035444;m3-7;---
abcd::3432:4833:46d5:9d12 ping statistics --- 1461845507.035702;m3-7;3
packets transmitted, 3 received, 0% packet loss, time 2.0633950 s
1461845507.036245;m3-7;rtt min/avg/max = 8.463/9.336/10.415 ms |

which are comparable to the link-local pings so I would say "normal".

I wasn't able to reproduce this on |samr21-xpro|, so it might be a timer
related issue (?) or maybe the optimization for Cortex M3 does something
crazy that lets a simple array look-up (which the context lookup
basically is) run incredibly long.

—
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub
#5405

miri64 · 2016-04-28T21:56:54Z

Yupp, with the setup you described it works (with 6ctx):

m3-9;ping6 abcd::3432:4833:46db:8b1a
1461880295.173963;m3-9;> ping6 abcd::3432:4833:46db:8b1a
1461880295.183940;m3-9;12 bytes from abcd::3432:4833:46db:8b1a: id=83 seq=1 hop limit=64 time = 0.986 ms
1461880303.192782;m3-9;12 bytes from abcd::3432:4833:46db:8b1a: id=83 seq=2 hop limit=64 time = 0.746 ms
1461880311.201164;m3-9;12 bytes from abcd::3432:4833:46db:8b1a: id=83 seq=3 hop limit=64 time = 0.826 ms
1461880311.202442;m3-9;--- abcd::3432:4833:46db:8b1a ping statistics ---
1461880311.204428;m3-9;3 packets transmitted, 3 received, 0% packet loss, time 2.063289 s
1461880311.205363;m3-9;rtt min/avg/max = 0.746/0.852/0.986 ms

[pcap] (first ping exchange is without ctx)

RIOT-2016.10 - Release Notes ============================ RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things: 8-bit microcontrollers, 16-bit microcontrollers and light-weight 32-bit processors. RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance). RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community) and is licensed with a non-viral copyleft license (LGPLv2.1), which allows indirect business models around the free open-source software platform provided by RIOT. About this release: =================== This release provides a lot of new features as well as it fixes several major bugs. Among these new features are the new simplified network socket API called sock, the GNRC specific CoAP implementation gcoap and several new packages: TinyDTLS, the Aversive++ microcontroller library for robotics, the u8g2 graphic library, and nanocoap. Using the new sock API an implementation of the Simple Time Network Protocol (SNTP) was also introduced, allowing for time synchronization between nodes. New platforms include the Arduino Uno, the Arduino Duemilanove, the Arduino Zero, SODAQ Autonomo, and the Zolertia remote (rev. B). The most significant bug fix was done in native which led to a significantly more robust handling of ISRs and now allows for at least 1,000 native instances running stably on one machine. About 263 pull requests with about 398 commits have been merged since the last release and about 42 issues have been solved. 37 people contributed with code in 100 days. 1006 files have been touched with 166500 insertions and 26926 deletions. Notations used below: ===================== + means new feature/item * means modified feature/item - means removed feature/item New features and changes ======================== General ------- * Verbose behavior for assert() macro Core ---- + MPU support for Cortex-M API changes ----------- + Socket-like sock API (replacing conn) * netdev2: Add Testmodes and CCA modes * IEEE 802.15.4: clean-up Intra-PAN behavior * IEEE 802.15.4: centralize default values * gnrc_pktbuf: allow for 0-sized snips + gnrc_netapi: mbox and arbitrary callback support System libraries ---------------- No new features or changes Networking ---------- + Provide sock-port for GNRC + gcoap: a GNRC-based CoAP implementation + Simple Network Time Protocol (RFC 5905, section 14) + Priority Queue for packet snips + IPv4 header definitions Packages -------- + nanocoap: CoAP header parser/builder + TinyDTLS: DTLS library + tiny-asn1: asn.1/der decoder + Aversive++ microcontroller programming library + u8g2 graphic library Platforms --------- + Support for stm32f2xx MCU family + Low power modes for samd21 CPUs + More Arduino-based platforms: + Arduino Uno + Arduino Duemilanove + Arduino Zero + More boards of ST's Nucleo platforms: + ST Nucleo F030 board support + ST Nucleo F070 board support + ST Nucleo F446 board support + SODAQ Automono + Zolertia remote rev. B Drivers ------- + W5100 Ethernet device + Atmel IO1 Xplained extension + LPD8808 LED strips * at86rf2xx: provide capability to access the RND_VALUE random value register Build System ------------ + static-tests build target for easy local execution of CI's static tests Other ----- + Provide Arduino API to Nucleo boards + Packer configuration file to build vagrant boxes + CC2650STK Debugger Support + ethos: add Ethos over TCP support Fixed Issues from the last release ================================== #534: native debugging on osx fails #2071: native: *long* overdue fixes #3341: netdev2_tap crashes when hammered #5007: gnrc icmpv6: Ping reply goes out the wrong interface #5432: native: valgrind fails Known Issues ============ Networking related issues ------------------------- #3075: nhdp: unnecessary microsecond precision: NHDP works with timer values of microsecond precision which is not required. Changing to lower precision would save some memory. #4048: potential racey memory leak: According to the packet buffer stats, flood-pinging a multicast destination may lead to a memory leak due to a race condition. However, it seems to be a rare case and a completely filled up packet buffer was not observed. #4388: POSIX sockets: open socket is bound to a specific thread: This was an inherit problem of the conn API under GNRC. Since the POSIX sockets are still based on conn for this release, this issue persists #4527: gnrc_ipv6: Multicast is not forwarded if routing node listens to the address (might still be fixable for release, see #5729, #5230: gnrc ipv6: multicast packets are not dispatched to the upper layers) #5016: gnrc_rpl: Rejoining RPL instance as root after reboot messes up routing #5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple interfaces might get the same EUI-64 for them since they are generated from the same CPU ID. #5656: Possible Weakness with locking in the GNRC network stack: For some operations mutexes to the network interfaces need to get unlocked in the current implementation to not get deadlocked. Recursive mutexes as provided in #5731 might help to solve this problem. #5748: gnrc: nodes crashing with too small packet buffer: A packet buffer of size ~512 B might lead to crashes. The issue describes this for several hundret nodes, but agressive flooding with just two nodes was also shown to lead to this problem. #5858: gnrc: 6lo: potential problem with reassembly of fragments: If one frame gets lost the reassembly state machine might get out of sync ### NDP is not working properly #4499: handle of l2src_len in gnrc_ndp_rtr_sol_handle: Reception of a router solicitation might lead to invalid zero-length link-layer addresses in neighbor cache. #5005: ndp: router advertisement sent with global address: Under some circumstances a router might send RAs with GUAs. While they are ignored on receive (as RFC 4861 specifies), RAs should have link-local addresses and not even be send out this way. #5122: NDP: global unicast address on non-6LBR nodes disappears after a while: Several issues (also see #5760) lead to a global unicast address effectively being banned from the network (disappears from neighbor cache, is not added again) #5467: ipv6 address vanishes when ARO (wrongly) indicates DUP caused by outdated ncache at router #5539: Border Router: packet not forwarded from ethos to interface 6 #5790: ND: Lost of Global IPV6 on node after sending lot of UDP frame from BR Timer related issues -------------------- #4841: xtimer: timer already in the list: Under some conditions an xtimer can end up twice in the internal list of the xtimer module #4902: xtimer: xtimer_set: xtimer_set does not handle integer overflows well #5338: xtimer: xtimer_now() not ISR safe for non-32-bit platforms. #5928: xtimer: usage in board_init() crashes: some boards use the xtimer in there board_init() function. The xtimer is however first initialized in the auto_init module which is executed after board_init() #6052: tests: xtimer_drift gets stuck: xtimer_drift application freezes after ~30-200 seconds native related issues --------------------- #495: native not float safe: When the FPU is used when an asynchronous context switch occurs, either the stack gets corrupted or a floating point exception occurs. #2175: ubjson: valgind registers "Invalid write of size 4" in unittests #4590: pkg: building relic with clang fails. #5796: native: tlsf: early malloc will lead to a crash: TLSF needs pools to be initialized (which is currently expected to be done in an application). If a malloc is needed before an application's main started (e.g. driver initialization) the node can crash, since no pool is allocated yet. other platform related issues ----------------------------- #1891: newlib-nano: Printf formatting does not work properly for some numberic types: PRI[uxdi]64, PRI[uxdi]8 and float are not parsed in newlib-nano #2006: cpu/nrf51822: timer callback may be fired too early #2143: unittests: tests-core doesn't compile for all platforms: GCC build-ins were used in the unittests which are not available with msp430-gcc #2300: qemu unittest fails because of a page fault #4512: pkg: tests: RELIC unittests fail on iotlab-m3 #4522: avsextrem: linker sometimes doesn't find `bl_init_clks()` #4560: make: clang is more pedantic than gcc oonf_api is not building with clang. (Partly solved by #4593) #4694: drivers/lm75a: does not build #4737: cortex-m: Hard fault after a thread exits (under some circumstances) #4822: kw2xrf: packet loss when packets get fragmented #4876: at86rf2xx: Simultaneous use of different transceiver types is not supported #4954: chronos: compiling with -O0 breaks #4866: not all GPIO driver implementations are thread safe: Due to non-atomic operations in the drivers some pin configurations might get lost. #5009: RIOT is saw-toothing in energy consumption (even when idling) #5103: xtimer: weird behavior of tests/xtimer_drift: xtimer_drift randomly jumps a few seconds on nrf52 #5361: cpu/cc26x0: timer broken #5405: Eratic timings on iotlab-m3 with compression context activated #5460: cpu/samd21: i2c timing with compiler optimization #5486: at86rf2xx: lost interrupts #5489: cpu/lpc11u34: ADC broken #5603: atmega boards second UART issue #5678: at86rf2xx: failed assertion in _isr #5719: cc2538: rf driver doesn't handle large packets #5799: kw2x: 15.4 duplicate transmits #5944: msp430: ipv6_hdr unittests fail #5848: arduino: Race condition in sys/arduino/Makefile.include #5954: nRF52 uart_write get stuck #6018: nRF52 gnrc 6lowpan ble memory leak other issues ------------ #1263: TLSF implementation contains (a) read-before-write error(s). #3256: make: Setting constants on compile time doesn't really set them everywhere #3366: periph/i2c: handle NACK #4488: Making the newlib thread-safe: When calling puts/printf after thread_create(), the CPU hangs for DMA enabled uart drivers. #4866: periph: GPIO drivers are not thread safe #5128: make: buildtest breaks when exporting FEATURES_PROVIDED var #5207: make: buildest fails with board dependent application Makefiles #5390: pkg: OpenWSN does not compile: This package still uses deprecated modules and was not tested for a long time. #5520: tests/periph_uart not working #5561: C++11 extensions in header files #5776: make: Predefining CFLAGS are parsed weirdly #5863: OSX + SAMR21-xpro: shell cannot handle command inputs larger than 64 chars #5962: Makefile: UNDEF variable is not working as documented #6022: pkg: build order issue Special Thanks ============== We like to give our special thanks to all the companies that provided us with their hardware for porting and testing, namely the people from (in alphabeticalorder): Atmel, Freescale, Imagination Technologies, Limifrog, Nordic, OpenMote, Phytec, SiLabs, UDOO,and Zolertia; and also companies that directly sponsored development time: Cisco Systems, Eistec, Ell-i, Enigeering Spirit, Nordic, FreshTemp LLC, OTAkeys and Phytec. More information ================ http://www.riot-os.org Mailing lists ------------- * RIOT OS kernel developers list devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications notifications@riot-os.org (http://lists.riot-os.org/mailman/listinfo/notifications) IRC --- * Join the RIOT IRC channel at: irc.freenode.net, #riot-os License ======= * Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation. * Some external sources are published under a separate, LGPL compatible license (e.g. some files developed by SICS). All code files contain licensing information.

RIOT-2016.10 - Release Notes ============================ RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things: 8-bit microcontrollers, 16-bit microcontrollers and light-weight 32-bit processors. RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance). RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community) and is licensed with a non-viral copyleft license (LGPLv2.1), which allows indirect business models around the free open-source software platform provided by RIOT. About this release: =================== This release provides a lot of new features as well as it fixes several major bugs. Among these new features are the new simplified network socket API called sock, the GNRC specific CoAP implementation gcoap and several new packages: TinyDTLS, the Aversive++ microcontroller library for robotics, the u8g2 graphic library, and nanocoap. Using the new sock API an implementation of the Simple Time Network Protocol (SNTP) was also introduced, allowing for time synchronization between nodes. New platforms include the Arduino Uno, the Arduino Duemilanove, the Arduino Zero, SODAQ Autonomo, and the Zolertia remote (rev. B). The most significant bug fix was done in native which led to a significantly more robust handling of ISRs and now allows for at least 1,000 native instances running stably on one machine. About 263 pull requests with about 398 commits have been merged since the last release and about 42 issues have been solved. 37 people contributed with code in 100 days. 1006 files have been touched with 166500 insertions and 26926 deletions. Notations used below: ===================== + means new feature/item * means modified feature/item - means removed feature/item New features and changes ======================== General ------- * Verbose behavior for assert() macro Core ---- + MPU support for Cortex-M API changes ----------- + Socket-like sock API (replacing conn) * netdev2: Add Testmodes and CCA modes * IEEE 802.15.4: clean-up Intra-PAN behavior * IEEE 802.15.4: centralize default values * gnrc_pktbuf: allow for 0-sized snips + gnrc_netapi: mbox and arbitrary callback support System libraries ---------------- No new features or changes Networking ---------- + Provide sock-port for GNRC + gcoap: a GNRC-based CoAP implementation + Simple Network Time Protocol (RFC 5905, section 14) + Priority Queue for packet snips + IPv4 header definitions Packages -------- + nanocoap: CoAP header parser/builder + TinyDTLS: DTLS library + tiny-asn1: asn.1/der decoder + Aversive++ microcontroller programming library + u8g2 graphic library Platforms --------- + Support for stm32f2xx MCU family + Low power modes for samd21 CPUs + More Arduino-based platforms: + Arduino Uno + Arduino Duemilanove + Arduino Zero + More boards of ST's Nucleo platforms: + ST Nucleo F030 board support + ST Nucleo F070 board support + ST Nucleo F446 board support + SODAQ Automono + Zolertia remote rev. B Drivers ------- + W5100 Ethernet device + Atmel IO1 Xplained extension + LPD8808 LED strips * at86rf2xx: provide capability to access the RND_VALUE random value register Build System ------------ + static-tests build target for easy local execution of CI's static tests Other ----- + Provide Arduino API to Nucleo boards + Packer configuration file to build vagrant boxes + CC2650STK Debugger Support + ethos: add Ethos over TCP support Fixed Issues from the last release ================================== RIOT-OS#534: native debugging on osx fails RIOT-OS#2071: native: *long* overdue fixes RIOT-OS#3341: netdev2_tap crashes when hammered RIOT-OS#5007: gnrc icmpv6: Ping reply goes out the wrong interface RIOT-OS#5432: native: valgrind fails Known Issues ============ Networking related issues ------------------------- RIOT-OS#3075: nhdp: unnecessary microsecond precision: NHDP works with timer values of microsecond precision which is not required. Changing to lower precision would save some memory. RIOT-OS#4048: potential racey memory leak: According to the packet buffer stats, flood-pinging a multicast destination may lead to a memory leak due to a race condition. However, it seems to be a rare case and a completely filled up packet buffer was not observed. RIOT-OS#4388: POSIX sockets: open socket is bound to a specific thread: This was an inherit problem of the conn API under GNRC. Since the POSIX sockets are still based on conn for this release, this issue persists RIOT-OS#4527: gnrc_ipv6: Multicast is not forwarded if routing node listens to the address (might still be fixable for release, see RIOT-OS#5729, RIOT-OS#5230: gnrc ipv6: multicast packets are not dispatched to the upper layers) RIOT-OS#5016: gnrc_rpl: Rejoining RPL instance as root after reboot messes up routing RIOT-OS#5055: cpuid: multiple radios will get same EUI-64 Nodes with multiple interfaces might get the same EUI-64 for them since they are generated from the same CPU ID. RIOT-OS#5656: Possible Weakness with locking in the GNRC network stack: For some operations mutexes to the network interfaces need to get unlocked in the current implementation to not get deadlocked. Recursive mutexes as provided in RIOT-OS#5731 might help to solve this problem. RIOT-OS#5748: gnrc: nodes crashing with too small packet buffer: A packet buffer of size ~512 B might lead to crashes. The issue describes this for several hundret nodes, but agressive flooding with just two nodes was also shown to lead to this problem. RIOT-OS#5858: gnrc: 6lo: potential problem with reassembly of fragments: If one frame gets lost the reassembly state machine might get out of sync ### NDP is not working properly RIOT-OS#4499: handle of l2src_len in gnrc_ndp_rtr_sol_handle: Reception of a router solicitation might lead to invalid zero-length link-layer addresses in neighbor cache. RIOT-OS#5005: ndp: router advertisement sent with global address: Under some circumstances a router might send RAs with GUAs. While they are ignored on receive (as RFC 4861 specifies), RAs should have link-local addresses and not even be send out this way. RIOT-OS#5122: NDP: global unicast address on non-6LBR nodes disappears after a while: Several issues (also see RIOT-OS#5760) lead to a global unicast address effectively being banned from the network (disappears from neighbor cache, is not added again) RIOT-OS#5467: ipv6 address vanishes when ARO (wrongly) indicates DUP caused by outdated ncache at router RIOT-OS#5539: Border Router: packet not forwarded from ethos to interface 6 RIOT-OS#5790: ND: Lost of Global IPV6 on node after sending lot of UDP frame from BR Timer related issues -------------------- RIOT-OS#4841: xtimer: timer already in the list: Under some conditions an xtimer can end up twice in the internal list of the xtimer module RIOT-OS#4902: xtimer: xtimer_set: xtimer_set does not handle integer overflows well RIOT-OS#5338: xtimer: xtimer_now() not ISR safe for non-32-bit platforms. RIOT-OS#5928: xtimer: usage in board_init() crashes: some boards use the xtimer in there board_init() function. The xtimer is however first initialized in the auto_init module which is executed after board_init() RIOT-OS#6052: tests: xtimer_drift gets stuck: xtimer_drift application freezes after ~30-200 seconds native related issues --------------------- RIOT-OS#495: native not float safe: When the FPU is used when an asynchronous context switch occurs, either the stack gets corrupted or a floating point exception occurs. RIOT-OS#2175: ubjson: valgind registers "Invalid write of size 4" in unittests RIOT-OS#4590: pkg: building relic with clang fails. RIOT-OS#5796: native: tlsf: early malloc will lead to a crash: TLSF needs pools to be initialized (which is currently expected to be done in an application). If a malloc is needed before an application's main started (e.g. driver initialization) the node can crash, since no pool is allocated yet. other platform related issues ----------------------------- RIOT-OS#1891: newlib-nano: Printf formatting does not work properly for some numberic types: PRI[uxdi]64, PRI[uxdi]8 and float are not parsed in newlib-nano RIOT-OS#2006: cpu/nrf51822: timer callback may be fired too early RIOT-OS#2143: unittests: tests-core doesn't compile for all platforms: GCC build-ins were used in the unittests which are not available with msp430-gcc RIOT-OS#2300: qemu unittest fails because of a page fault RIOT-OS#4512: pkg: tests: RELIC unittests fail on iotlab-m3 RIOT-OS#4522: avsextrem: linker sometimes doesn't find `bl_init_clks()` RIOT-OS#4560: make: clang is more pedantic than gcc oonf_api is not building with clang. (Partly solved by RIOT-OS#4593) RIOT-OS#4694: drivers/lm75a: does not build RIOT-OS#4737: cortex-m: Hard fault after a thread exits (under some circumstances) RIOT-OS#4822: kw2xrf: packet loss when packets get fragmented RIOT-OS#4876: at86rf2xx: Simultaneous use of different transceiver types is not supported RIOT-OS#4954: chronos: compiling with -O0 breaks RIOT-OS#4866: not all GPIO driver implementations are thread safe: Due to non-atomic operations in the drivers some pin configurations might get lost. RIOT-OS#5009: RIOT is saw-toothing in energy consumption (even when idling) RIOT-OS#5103: xtimer: weird behavior of tests/xtimer_drift: xtimer_drift randomly jumps a few seconds on nrf52 RIOT-OS#5361: cpu/cc26x0: timer broken RIOT-OS#5405: Eratic timings on iotlab-m3 with compression context activated RIOT-OS#5460: cpu/samd21: i2c timing with compiler optimization RIOT-OS#5486: at86rf2xx: lost interrupts RIOT-OS#5489: cpu/lpc11u34: ADC broken RIOT-OS#5603: atmega boards second UART issue RIOT-OS#5678: at86rf2xx: failed assertion in _isr RIOT-OS#5719: cc2538: rf driver doesn't handle large packets RIOT-OS#5799: kw2x: 15.4 duplicate transmits RIOT-OS#5944: msp430: ipv6_hdr unittests fail RIOT-OS#5848: arduino: Race condition in sys/arduino/Makefile.include RIOT-OS#5954: nRF52 uart_write get stuck RIOT-OS#6018: nRF52 gnrc 6lowpan ble memory leak other issues ------------ RIOT-OS#1263: TLSF implementation contains (a) read-before-write error(s). RIOT-OS#3256: make: Setting constants on compile time doesn't really set them everywhere RIOT-OS#3366: periph/i2c: handle NACK RIOT-OS#4488: Making the newlib thread-safe: When calling puts/printf after thread_create(), the CPU hangs for DMA enabled uart drivers. RIOT-OS#4866: periph: GPIO drivers are not thread safe RIOT-OS#5128: make: buildtest breaks when exporting FEATURES_PROVIDED var RIOT-OS#5207: make: buildest fails with board dependent application Makefiles RIOT-OS#5390: pkg: OpenWSN does not compile: This package still uses deprecated modules and was not tested for a long time. RIOT-OS#5520: tests/periph_uart not working RIOT-OS#5561: C++11 extensions in header files RIOT-OS#5776: make: Predefining CFLAGS are parsed weirdly RIOT-OS#5863: OSX + SAMR21-xpro: shell cannot handle command inputs larger than 64 chars RIOT-OS#5962: Makefile: UNDEF variable is not working as documented RIOT-OS#6022: pkg: build order issue Special Thanks ============== We like to give our special thanks to all the companies that provided us with their hardware for porting and testing, namely the people from (in alphabeticalorder): Atmel, Freescale, Imagination Technologies, Limifrog, Nordic, OpenMote, Phytec, SiLabs, UDOO,and Zolertia; and also companies that directly sponsored development time: Cisco Systems, Eistec, Ell-i, Enigeering Spirit, Nordic, FreshTemp LLC, OTAkeys and Phytec. More information ================ http://www.riot-os.org Mailing lists ------------- * RIOT OS kernel developers list devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications notifications@riot-os.org (http://lists.riot-os.org/mailman/listinfo/notifications) IRC --- * Join the RIOT IRC channel at: irc.freenode.net, #riot-os License ======= * Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation. * Some external sources are published under a separate, LGPL compatible license (e.g. some files developed by SICS). All code files contain licensing information.

kYc0o · 2018-07-17T14:02:34Z

Sorry for the noise... is this issue still present? There was a significant rework on networking (although not in xtimer, which might be the cause of the problem) which might have solved this issue.

miri64 · 2018-07-17T14:38:30Z

Can't reproduce anymore, so I deem it fixed.

miri64 assigned kaspar030 Apr 28, 2016

miri64 added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Area: network Area: Networking GNRC Area: timers Area: timer subsystems labels Apr 28, 2016

miri64 added this to the Release 2016.10 milestone Oct 18, 2016

miri64 modified the milestones: Release 2016.10, Release 2017.01 Nov 11, 2016

PeterKietzmann modified the milestones: Release 2017.01, Release 2017.04 Jan 26, 2017

aabadie modified the milestones: Release 2017.04, Release 2017.07 Jun 21, 2017

kYc0o added this to To Do - Other platform issues in Bug tracker 2018.04 Oct 31, 2017

miri64 closed this as completed Jul 17, 2018

Bug tracker 2018.04 automation moved this from To Do - Other platform issues to Done Jul 17, 2018

fjmolinas changed the title ~~Eratic timings on iotlab-m3 with compression context activated~~ Erratic timings on iotlab-m3 with compression context activated Feb 3, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Erratic timings on iotlab-m3 with compression context activated #5405

Erratic timings on iotlab-m3 with compression context activated #5405

miri64 commented Apr 28, 2016

miri64 commented Apr 28, 2016

kaspar030 commented Apr 28, 2016

miri64 commented Apr 28, 2016 •

edited

Loading

kYc0o commented Jul 17, 2018

miri64 commented Jul 17, 2018

Erratic timings on iotlab-m3 with compression context activated #5405

Erratic timings on iotlab-m3 with compression context activated #5405

Comments

miri64 commented Apr 28, 2016

miri64 commented Apr 28, 2016

kaspar030 commented Apr 28, 2016

miri64 commented Apr 28, 2016 • edited Loading

kYc0o commented Jul 17, 2018

miri64 commented Jul 17, 2018

miri64 commented Apr 28, 2016 •

edited

Loading