native: long overdue fixes #2071

LudwigKnuepfer · 2014-11-22T13:58:59Z

Fixes for natives hwtimer and signal handling.

The hwtimer fixes made the signal handling fixes more pressing.

Some issues that should be fixed/closed by this:

OlegHahm · 2014-11-23T14:55:55Z

Sounds exiting - mostly because of the promised fix for #499.

LudwigKnuepfer · 2014-11-24T15:15:48Z

Well, I couldn't reliably crash it anymore (although it did segfault once), so it already comprises a significant improvement.

emmanuelsearch · 2014-11-24T15:31:37Z

any hints as to how I should test this?

LudwigKnuepfer · 2014-11-24T16:26:45Z

For the timer issues linked to in the PR description, it's easy - run the tests that fail and see if it works.
For the network issue I've been using https://github.com/LudwigOrtmann/riot-tools/tree/master/l2perf to swamp examples/default. However #1331 is still open, so you would have to employ some Linux vm.

Due to the race-condition nature of the issues it might be necessary to run the tests a couple of times until you're confident it is gone..
Also you would need to make sure you can actually produce the race condition with master in your setup.

emmanuelsearch · 2014-11-25T10:16:53Z

on LinuxMint VM, when I run hwtimer_wait test on the current master, it hangs, so I suppose I can reproduce the race condition.

With this PR, the first time I run hwtimer_wait test after compilation, I get the following and in the end it hangs (see below). If I repeat the test after that without recompiling, it works systematically. Any idea what's wrong here?

$ ./bin/native/*.elf
RIOT native interrupts/signals initialized.
LED_GREEN_OFF
LED_RED_ON
RIOT native board initialized.
RIOT native hardware initialization complete.

kernel_init(): This is RIOT! (Version: 2014.01-2561-g109a1b-HEAD)
kernel_init(): jumping into first task...
This is a regression test for a race condition in hwtimer_wait.
When the race condition is hit, the timer will wait for a very very long time.
The test should take about 5 sec.
isr_thread_yield(): handling signals

isr_thread_yield(): handling signals

isr_thread_yield(): handling signals

isr_thread_yield(): handling signals

isr_thread_yield(): handling signals

Remark: the number of "handling signals" outputs before it hangs varies.

LudwigKnuepfer · 2014-11-25T11:00:27Z

Interesting, I've got no explanation for the first/consecutive runs behavior.
However the 'handling signals' forced debug message suggests (I think) that the timer setting function is very slow and that HWTIMER_SPIN_BARRIER is still too low for your vm. Could you try doubling it?
It's this line.

emmanuelsearch · 2014-11-25T12:56:28Z

Works like a charm doubling HWTIMER_SPIN_BARRIER (I also restarted my VM).
However, hwtimer_spin test hangs now (and it does not hang in master for me).

$ ./bin/native/*.elf
RIOT native interrupts/signals initialized.
LED_GREEN_OFF
LED_RED_ON
RIOT native board initialized.
RIOT native hardware initialization complete.

kernel_init(): This is RIOT! (Version: 2014.01-2561-g109a1b-emmanuel-VirtualBox-HEAD)
kernel_init(): jumping into first task...
This is just a functionality test for hwtimer_spin.

remark: it hangs here, independent of the value of HWTIMER_SPIN_BARRIER

LudwigKnuepfer · 2014-11-25T13:02:11Z

Hanging is not what I'd call working like charm.. but thanks, I'll investigate further.

LudwigKnuepfer · 2014-11-25T13:03:44Z

By the way - you can make term to run the application.

emmanuelsearch · 2014-11-25T13:19:44Z

well hwtimer_wait works like a charm at least ;)

LudwigKnuepfer · 2014-11-25T13:24:47Z

Ah, sorry, I misread. (wait vs spin)

LudwigKnuepfer · 2014-11-25T13:32:45Z

Hm, I would assume the test takes very long now, yes, but that is due to the test implementation.
You should be able to see the process using 100% CPU with top.
Please verify that

diff --git a/tests/hwtimer_spin/main.c b/tests/hwtimer_spin/main.c
index 1858d3b..7b618e7 100644
--- a/tests/hwtimer_spin/main.c
+++ b/tests/hwtimer_spin/main.c
@@ -28,7 +28,7 @@ int main(void)
     puts("This is just a functionality test for hwtimer_spin.");

     for (unsigned long r = 10000; r > 0; r--) {
-        for (unsigned long i = HWTIMER_SPIN_BARRIER; i > 0; i--) {
+        for (unsigned long i = HWTIMER_SPIN_BARRIER; i > 0; i/=2) {
             hwtimer_wait(i);
         }
     }

does not "hang".

emmanuelsearch · 2014-11-25T13:38:41Z

It does not hang with i/=2 steps. Testing currently with i-- again.

LudwigKnuepfer · 2014-11-25T13:52:14Z

You could also reduce the number of iterations from 10000 to 1000 or something like that ..

emmanuelsearch · 2014-11-25T14:06:51Z

Yup. Verified it works hwtimer_spin worksfine both for 10000 and 1000 ;)
Let me try the network tests now!

emmanuelsearch · 2014-11-25T16:50:19Z

@LudwigOrtmann Can you commit a working version of https://github.com/LudwigOrtmann/riot-tools/tree/master/l2perf ?

LudwigKnuepfer · 2014-11-25T16:56:48Z

please do checkout tg_server, it is fixed already.

emmanuelsearch · 2014-11-25T18:10:42Z

Done. But definitely lacks documentation ;) In particular, nothing seems to arrive at the receiving node wether I set an address or not (and in the latter case I use broadcast address 0). What's supposed to show that the test was a success?

emmanuelsearch · 2014-11-25T18:58:30Z

I could crash (seg fault) what's in master with tg 10000000 100 0 2 i.e., 10 million packets of size 10 sent directly one after the other (if I understood correctly your tool) to the other node which I addressed with ID 2. But it did not crash with your fixes.

emmanuelsearch · 2014-11-25T18:58:48Z

however it did segfault with 100M packets.

emmanuelsearch · 2014-11-25T19:16:08Z

also quickly checked hwtimer, irq, vtimer_msg and vtimer_msg_diff
the PR seems to improve things, if not solve everything. So ACK on my side.

LudwigKnuepfer · 2014-11-25T19:28:31Z

I'll squash and polish

OlegHahm · 2016-10-12T17:22:23Z

@LudwigKnuepfer, I think we could finally move forward by squashing and merging or do you disagree?

@miri64, thanks a lot for testing.

@Yonezawa-T2, thanks for the fix!

LudwigKnuepfer · 2016-10-16T18:22:21Z

@OlegHahm I squashed.

OlegHahm · 2016-10-17T11:15:37Z

I will try to test it one last time.

miri64 · 2016-10-21T11:04:38Z

@OlegHahm did you? If not can you summarize what you planned to do?

OlegHahm · 2016-10-27T15:28:21Z

Sorry. I was planning to use an application I used for some experiments with 1000 nodes. This experiments failed rather reproducable without this PR. Unfortunately, it is not based on master and I have some difficulties rebasing. I will give it another try tomorrow.

OlegHahm · 2016-10-29T15:17:24Z

I'm still on it.

OlegHahm · 2016-10-30T18:37:27Z

Unfortunately, I was not able to reproduce my experiment setup. However, I realized that flood pinging native from Linux currently result in a segfault without this PR. Merging this PR allows for floodpinging from multiple threads. Hence: ACK!

miri64 · 2016-10-30T18:42:43Z

The long quest is at an end! :D

LudwigKnuepfer · 2016-11-06T09:38:14Z

Almost 2 years .. whoa.

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 [email protected] (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list [email protected] (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits [email protected] (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications [email protected] (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 [email protected] (http://lists.riot-os.org/mailman/listinfo/devel) * RIOT OS users list [email protected] (http://lists.riot-os.org/mailman/listinfo/users) * RIOT commits [email protected] (http://lists.riot-os.org/mailman/listinfo/commits) * Github notifications [email protected] (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.

LudwigKnuepfer added Platform: native Platform: This PR/issue effects the native platform Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) State: WIP State: The PR is still work-in-progress and its code is not in its final presentable form yet labels Nov 22, 2014

LudwigKnuepfer force-pushed the 2071 branch 3 times, most recently from aeddd04 to beece39 Compare November 22, 2014 15:16

OlegHahm assigned emmanuelsearch Nov 23, 2014

OlegHahm added the CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable label Nov 26, 2014

miri64 approved these changes Oct 7, 2016

View reviewed changes

LudwigKnuepfer added 5 commits October 15, 2016 07:40

native: improve comments, coding style

535eda8

native: indicate interrupt status in ISR context

3b6d059

native: start with interrupts disabled

83886d6

native: add thread_yield_higher misuse warning

237340b

native: add syscall-leave trampoline

0b72be7

LudwigKnuepfer force-pushed the 2071 branch from 70ccda4 to 0b72be7 Compare October 15, 2016 07:51

LudwigKnuepfer removed CI: needs squashing Commits in this PR need to be squashed; If set, CI systems will mark this PR as unmergable State: WIP State: The PR is still work-in-progress and its code is not in its final presentable form yet labels Oct 16, 2016

miri64 changed the title ~~WIP: native: overdue fixes~~ native: *long* overdue fixes Oct 16, 2016

miri64 added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Oct 16, 2016

miri64 mentioned this pull request Oct 17, 2016

enableIRQ + _native_in_isr after long idle #2530

Closed

OlegHahm merged commit 3aab6bb into RIOT-OS:master Oct 30, 2016

LudwigKnuepfer deleted the 2071 branch November 6, 2016 09:37

OlegHahm mentioned this pull request Nov 10, 2016

netdev2_tap: crashes when hammered #3341

Closed

kaspar030 mentioned this pull request Nov 15, 2016

gnrc: crash with (excessive) traffic in native #6123

Closed

OlegHahm mentioned this pull request Nov 17, 2016

cpu: native: don't handle pending signals in isr_thread_yield #6135

Closed

OlegHahm mentioned this pull request Mar 6, 2017

cpu: native: fix thread_yield_higher isr_is_in() case #6660

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

native: long overdue fixes #2071

native: long overdue fixes #2071

LudwigKnuepfer commented Nov 22, 2014 •

edited

Loading

OlegHahm commented Nov 23, 2014

LudwigKnuepfer commented Nov 24, 2014

emmanuelsearch commented Nov 24, 2014

LudwigKnuepfer commented Nov 24, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

OlegHahm commented Oct 12, 2016

LudwigKnuepfer commented Oct 16, 2016

OlegHahm commented Oct 17, 2016

miri64 commented Oct 21, 2016

OlegHahm commented Oct 27, 2016

OlegHahm commented Oct 29, 2016

OlegHahm commented Oct 30, 2016

miri64 commented Oct 30, 2016

LudwigKnuepfer commented Nov 6, 2016

native: *long* overdue fixes #2071

native: *long* overdue fixes #2071

Conversation

LudwigKnuepfer commented Nov 22, 2014 • edited Loading

OlegHahm commented Nov 23, 2014

LudwigKnuepfer commented Nov 24, 2014

emmanuelsearch commented Nov 24, 2014

LudwigKnuepfer commented Nov 24, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

emmanuelsearch commented Nov 25, 2014

LudwigKnuepfer commented Nov 25, 2014

OlegHahm commented Oct 12, 2016

LudwigKnuepfer commented Oct 16, 2016

OlegHahm commented Oct 17, 2016

miri64 commented Oct 21, 2016

OlegHahm commented Oct 27, 2016

OlegHahm commented Oct 29, 2016

OlegHahm commented Oct 30, 2016

miri64 commented Oct 30, 2016

LudwigKnuepfer commented Nov 6, 2016

native: long overdue fixes #2071

native: long overdue fixes #2071

LudwigKnuepfer commented Nov 22, 2014 •

edited

Loading