-
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
cpu/sam0_common: Ethernet driver stops working after a while #16298
Comments
@benpicco |
I am not sure its related, but I saw a similar behavior last weekend when building an Ethernet based node: after booting the node Ethernet works as expected, but after a while (anywhere between 5min and 30min) the node stops responding. In my cases its a |
I can confirm there is a weird behavior, I'll investigate and report back if the problem is related to sam0 or not. |
It's actually quite quick to reproduce with the
I have a node that gets an IP and can ping an address on the Internet:
Now I flood ping this node, and withing a few seconds, the border router stops routing:
Border router is dead too
|
Detect RX of frame also when other bits of RSR are set. fixes RIOT-OS#16298
Detect RX of frame also when other bits of RSR are set. fixes RIOT-OS#16298
Description
The sam0 ethernet driver will stop working after a while of use.
Steps to reproduce the issue
I don't have a good way of reproducing the issue yet.
Basically I just leave the
same54-xpro
connected to an ethernet network for a while usingexamples/gnrc_networking
orexamples/gnrc_border_router
.After some time, it will cease to receive any packets (send still works) on the Ethernet interface.
Expected results
Packet reception is reliable
Actual results
Ethernet can not receive packets after some time.
Sending packets still works.
Versions
current RIOT master
The text was updated successfully, but these errors were encountered: