-
Notifications
You must be signed in to change notification settings - Fork 15
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
Cascoda driver stops working #255
Comments
@mtusnio the above logs do not indicate that the ca8210 driver has stopped working, this is in fact a workaround put in by Cascoda to reload the driver when it stops. Can you please check 6lowpan ping test to confirm whether the driver has actually stopped working? |
I haven't tried pinging, but in all cases running tcpdump on the interface reports no traffic at all despite clickers sending packets. |
@mtusnio is there an automated test case that is likely to be able to check this doesn't reoccur (once it's fixed) |
Not at the moment, but it might be related to some of the iperf3 issues we've noticed, so it might be worth investigating that. |
root@myCi40:/# ping6 -I lowpan0 fe80:0000:0000:0000:0204:a30b:0000:e4f4 |
Blocked on #295 |
The failure seems more prominent with Cascoda driver v1.3.0 on simply pinging 2 Ci40 boards with each other. The ping has not survived more than an hour's time.
Test: Ci40 A and B ping simultaneously to each other (Channel: 25, PAN: 0xdcba) |
Just to state clearly, the driver died after getting these logs, had to reboot the board to get 6lowpan working again. Managed to reproduce on 3 rev7 boards. Build used (includes Cascoda driver v1.3.0): http://jenkins.creatordev.io/job/CreatorDev/job/openwrt/job/ci40/293/artifact/bin/pistachio/
|
blocked on Cascoda/ca8210-linux#4 |
I left a board overnight after a fresh restart, running ping test first thing after 15 hours resulted in failure with these logs
|
In some circumstances, especially under high load, the cascoda driver stops working. Running ifconfig lowpan0 down throws:
[ 58.514110] ca8210 spi0.0: ca8210 was busy during attempted write
[ 58.540137] ca8210 spi0.0: spi write retry 1...
[ 58.545942] ca8210 spi0.0: ca8210 was busy during attempted write
[ 58.570183] ca8210 spi0.0: spi write retry 1...
Steps to reproduce:
The text was updated successfully, but these errors were encountered: