Since I got my wandboard quad two years ago, I face recurring problems with the ethernet interface. After some (variable) time, the ethernet interface becomes completely stuck. It appears to be working from a "software" point of view (no error logged, interface still "UP"), but no packets are emitted or received (impossible to emit or respond to ping, for example). The only way I found to recover from the freeze is to reboot the board.
I compile the kernel directly from the sources (rev. 4.5.0-rc6+, from https://github.com/RobertCNelson/armv7- ... atform.git). I observed the same behaviour with various revisions of the kernel from this repository (4.5.0-rc6+, 4.4, 4.0, and older ones). One reproducible way to trigger the freeze is to transfer large files (> GB) by NFS. Strangely, these events becomes really rare when the files are exchanged by rsync. The problem seems to be NFS-related in some obscure way.
I tried one kernel from the wandboard repository (3.14.28-01573-ge2df042-dirty, https://github.com/wandboard-org/linux.git) with less success: the interface did not freeze but files transferred by NFSv4 were invariably corrupted (and still no errors logged by the kernel). I also observed some weird behavior of rsync during transfers, especially during gentoo portage-tree sync. The transfer was interrupted for various reasons, for example
- Code: Select all
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(1633)
I'm back on a CNelson kernel, and watchdog is taking care of the periodical reboots, but it is not very convenient...
Has anyone ever encountered this bug or has an idea to track it down?