[riot-notifications] [RIOT] native stops receiving packets after a while (#298)

LudwigOrtmann notifications at github.com
Wed Nov 6 11:02:12 CET 2013

Thanks a lot!
It appears signal-driven IO is effectively edge triggered..

And yes, the segfaults are a different issue and I'm trying to fix them as well. It's a little difficult to pinpoint though as makecontext probably is not the cause but the victim of the underlying problem.

If all you need is a running system (until this is fixed) you could try slowing things down a bit. You could do that either in-RIOT by sending less often (maybe this is in tune with your goals to save energy consumption anyways?), or externally with tc. I could provide you with a tc wrapper script to build upon if you want to try that way. Or, if you are using desvirt, you could add  a `latency` parameter to `add_link` in `desvirt/lossnet.py` and change the tc invocation accordingly.

Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20131106/41763dcd/attachment.html>

More information about the notifications mailing list