-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
native: segfault on heavy network usage in transceiver #499
Comments
Another possible effect is in valgrind: process becomes unresponsive. |
|
../RIOT/examples/ccn-lite-client/bin/native/ccn-lite-client.elf: _native_lpm_sleep: select(): Resource temporarily unavailable
|
|
../RIOT/examples/ccn-lite-client/bin/native/ccn-lite-client.elf: _native_lpm_sleep: select(): Resource temporarily unavailable |
Is this only happening when you use the ltc? |
I'm not using the LTC since months |
Is it possible to create a testcase? |
It's nondeterministic, but somewhat reproducible with https://github.com/LudwigOrtmann/riot-tools/tree/master/l2perf by sending packets really fast. |
This issue is not apparent with the new network stack. It is possible to send pings with high throughput without crashing native (for the normal case). @OlegHahm what's your opinion on this? Should we close this? |
Yeah, let's close this. Even if there are problem with native and heavy network usage, this issue is about the transceiver module which has vanished. |
sending >100 packets per second causes a segfault in RIOT
in 9 of 10 cases it's:
in 1 of 10 cases it is:
This looks strange, because receive_packet with
type argument=0
indicates it's a packet from CC1100 transceiver. So this might be a corrupted stackThe text was updated successfully, but these errors were encountered: