smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110 #3088
Comments
|
In order to exclude a possible hardware issue with your custom carrier board, it would be helpful to reproduce this issue on a Raspberry Pi board. |
|
I cannot reproduce it with the official I/O board since it doesn't have Ethernet. And reproducing this on a full Pi doesn't seem relevant (different hardware). What else can I do to debug this? |
|
What's the difference between your custom IO board and a Raspberry Pi 3 regarding SMSC95xx wiring? |
JamesH65
added
the
Waiting for external input
|
I too am seeing this on a CM3 with an SMSC95xx. I too have looked at the other bug reports and was not able to find a solution to this issue. I am confused about what in the device tree source you are looking for? Jul 22 16:21:58 RevPi11734 kernel: [ 0.000000] Linux version 4.9.76-rt60-v7+ (admin@kunbus.de) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #1 SMP PREEMPT RT Tue, 17 Jul 2018 14:20:12 +0200 |
|
-110 is a timeout, but I don't think I can help much more than that. Raspberry Pi boards don't exhibit this problem, and the rare and random nature of the errors makes it look much more like a hardware issue than software (unless it is a very subtle configuration error). |
|
I found a quick test for this issue using iperf. I have a custom board PI CM3L with dual ethernet. I can use iperf on one as a master and one as a slave. See here: Using this the kernel/driver from Rasbian with mods by Kunbus errors out very quickly (<15 mins) with the timeout error as described above, but the version I built with Yocto has been running for several days now with no errors. The good Yocto version of the kernel is: The Rasbian/Kunbus version is: |
|
We've checked the wiring on our board. We don't have full schematic for RPi3B (AFAIK they are not open-sourced), so we're basing this on Pi1B 2.1 schematic. The difference is that nRESET pin on LAN9512 (we don't need 4 USB ports so we're not using LAN9514) is not wired to any GPIO pin and is pulled high instead. We haven't changed anything in the Devicetree regarding this pin (i.e. LAN_RUN) either. This seems in accordance with LAN9512 specs, Table 2-3. However, according to @pelwell this is an issue. Is this the case and are we misreading LAN9512 specs? |
|
In order to answer your question, we need to know how do you provide the 25 MHz clock source (e.g. via GPIO of BCM2835). |
|
XI and XO pins of LAN9512 are wired same as in RPiB 2.1 schematic to an external 25 MHz clock source. I'm going to try to connect an unused GPIO pin from CM3 to nRESET on LAN9512, configure it as LAN_RUN in DT and see if I can still reproduce the issue. |
|
We've made a few test boards with nRESET connected to GPIO pin 13 and configured that pin as We're currently investigating whether this issue could be related to crosstalk from LED traces. |
|
@GeorgeSapkin I'm having this same issue, I'm building my self the Raspbian operating system with pi-gen with some custom configurations, my last build was by Oct 2, my entire setup is the RPi connected to a ST32 board (it has a serial connection and a storage drive inside it), for testing there is no sensors/gpio connections to the ST32 boards, and for production it has several others devices connected to it. Testing case works ok, no issues, I am able to mount the storage into linux and all the applications that interact with it just works. On the other side, production does not works, when I plug in the ST32 board to RPi it gives me this: Two ST32 boards has the same firmware, RPi is the same, I tested different power sources (thinking it was that because prod ST32 board has other devices connected). I have a previous RPi image version that is working on prod though, and it is almost one year old. This is my report of the situation, I will see if I can rollback to another kernel version and see how it goes. |
|
Looks like it might be related to #2924 |
|
@GeorgeSapkin thanks for point me out that issue, my solution right now was to compile a 4.14.107 kernel and modules and that solved the issue I mentioned and another issue I had with the HDMI screen being yellow when the kernel starts. But for now this was my workaround. |
|
@xyklex I'm glad to hear it solved your issue. We're stress-testing 4.14.x branch as well to see if it's an improvement. |
|
@GeorgeSapkin could you tell me if you solved the problem with version 4.14.x? |
|
@ckamas We are facing this or very similar issue on our kunbus revpi as well. Did you manage to find a solution? |
Describe the bug
Network connectivity drops out at random on CM3 with a custom carrier board with LAN9512. Device becomes completely unreachable over any network going through that chip (e.g. Ethernet, LTE).
To reproduce
Unknown.
Expected behaviour
Network connectivity doesn't randomly drop out.
Actual behaviour
Network connectivity drops out.
System
cat /etc/rpi-issue)? Raspberry Pi reference 2018-06-27vcgencmd version)? VCHI initialization faileduname -a)? 4.19.42-v7+ system freeze while unplug r8152 usb2network card #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/LinuxLogs
Additional context
I've already checked issues #60, #149, #552 and #746 but none of them really contain anything useful besides mentioning that the issue is already fixed.
nRESET pin on LAN9512 is pulled high and not connected to a GPIO pin.
The text was updated successfully, but these errors were encountered: