The Industrial Raspberry Pi Forum

Posted: **05 Sep 2022, 12:05**

Hi,

i have detected some network problems on multiple RevPi Connects. After some debugging, i discoverd some unusual usb disconnects:

Code: Select all

[Sat Aug 27 07:31:47 2022] usb 1-1.1: USB disconnect, device number 3
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.1:1.0 eth0: Link is Down
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.1:1.0 eth0: Error updating MAC full duplex mode
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.1:1.0 eth0 (unregistered): Error disabling interrupts
[Sat Aug 27 07:31:47 2022] usb 1-1.5: USB disconnect, device number 4
[Sat Aug 27 07:31:47 2022] usb 1-1.5.1: USB disconnect, device number 8
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.5.1:1.0 eth1: unregister 'smsc95xx' usb-3f980000.usb-1.5.1, smsc95xx USB 2.0 Ethernet
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.5.1:1.0 eth1: Link is Down
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.5.1:1.0 eth1: Error updating MAC full duplex mode
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.5.1:1.0 eth1: hardware isn't capable of remote wakeup
[Sat Aug 27 07:31:47 2022] smsc95xx 1-1.5.1:1.0 eth1 (unregistered): Error disabling interrupts
[Sat Aug 27 07:31:47 2022] usb 1-1.5.2: USB disconnect, device number 9
[Sat Aug 27 07:31:47 2022] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[Sat Aug 27 07:31:47 2022] ftdi_sio 1-1.5.2:1.0: device disconnected
[Sat Aug 27 07:31:47 2022] usb 1-1.5.3: USB disconnect, device number 10
[Sat Aug 27 07:31:47 2022] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[Sat Aug 27 07:31:47 2022] ftdi_sio 1-1.5.3:1.0: device disconnected
[Sat Aug 27 07:31:48 2022] usb 1-1: reset high-speed USB device number 2 using dwc2
[Sat Aug 27 07:31:48 2022] usb 1-1.1: new high-speed USB device number 11 using dwc2
[Sat Aug 27 07:31:48 2022] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[Sat Aug 27 07:31:48 2022] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sat Aug 27 07:31:48 2022] smsc95xx v2.0.0
[Sat Aug 27 07:31:48 2022] SMSC LAN8700 usb-001:011:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:011:01, irq=MAC)
[Sat Aug 27 07:31:48 2022] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, c8:3e:a7:01:7e:e1
[Sat Aug 27 07:31:48 2022] usb 1-1.5: new high-speed USB device number 12 using dwc2
[Sat Aug 27 07:31:49 2022] usb 1-1.5: New USB device found, idVendor=0424, idProduct=9512, bcdDevice= 2.00
[Sat Aug 27 07:31:49 2022] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sat Aug 27 07:31:49 2022] hub 1-1.5:1.0: USB hub found
[Sat Aug 27 07:31:49 2022] hub 1-1.5:1.0: 3 ports detected
[Sat Aug 27 07:31:49 2022] usb 1-1.5.1: new high-speed USB device number 13 using dwc2
[Sat Aug 27 07:31:49 2022] usb 1-1.5.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[Sat Aug 27 07:31:49 2022] usb 1-1.5.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sat Aug 27 07:31:49 2022] smsc95xx v2.0.0
[Sat Aug 27 07:31:49 2022] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Sat Aug 27 07:31:49 2022] smsc95xx 1-1.1:1.0 eth0: Link is Down
[Sat Aug 27 07:31:49 2022] SMSC LAN8700 usb-001:013:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:013:01, irq=MAC)
[Sat Aug 27 07:31:49 2022] smsc95xx 1-1.5.1:1.0 eth1: register 'smsc95xx' at usb-3f980000.usb-1.5.1, smsc95xx USB 2.0 Ethernet, c8:3e:a7:01:7e:e2
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: new full-speed USB device number 14 using dwc2
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: Product: FT232R USB UART
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: Manufacturer: FTDI
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: SerialNumber: AV0JIEP7
[Sat Aug 27 07:31:49 2022] ftdi_sio 1-1.5.2:1.0: FTDI USB Serial Device converter detected
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: Detected FT232RL
[Sat Aug 27 07:31:49 2022] usb 1-1.5.2: FTDI USB Serial Device converter now attached to ttyUSB0
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: new full-speed USB device number 15 using dwc2
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: Product: FT232R USB UART
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: Manufacturer: FTDI
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: SerialNumber: AV0JIE90
[Sat Aug 27 07:31:50 2022] ftdi_sio 1-1.5.3:1.0: FTDI USB Serial Device converter detected
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: Detected FT232RL
[Sat Aug 27 07:31:50 2022] usb 1-1.5.3: FTDI USB Serial Device converter now attached to ttyUSB1
[Sat Aug 27 07:31:50 2022] smsc95xx 1-1.5.1:1.0 eth1: hardware isn't capable of remote wakeup
[Sat Aug 27 07:31:50 2022] smsc95xx 1-1.5.1:1.0 eth1: Link is Down
[Sat Aug 27 07:31:51 2022] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off
[Sat Aug 27 07:31:51 2022] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Sat Aug 27 07:31:52 2022] smsc95xx 1-1.5.1:1.0 eth1: Link is Up - 100Mbps/Full - flow control off
[Sat Aug 27 07:31:52 2022] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

Is this behaviour already known? The power supply should be sufficient (currently 60% of the capacity is used). Or could voltage dips from 24V cause this?

Posted: **06 Sep 2022, 13:08**

Hello,
A similar problem has already been dealt with here.
Please have a look here : viewtopic.php?p=12586&hilit=usb+disconn ... ect#p12597

Best Regards

Ulrich Kouatang Biakoup | Technical Support

Posted: **13 Sep 2022, 17:26**

Hello,
thanks for the quick response.
The other thread with the similar problem doesnt seem (if i unterstood it correctly) to apply to my situation, because neither an external usb device nor an IO module is used.
And with kernel-version 5.10.120-rt70-v7, it should have the latest firmware.
I, as well as mentioned in the other thread, applied a workaround at application level with the ifup-service, but i'm still interested in a further investigation and i am keep monitoring the Connects with the new kernel-version.

Best Regards.

Posted: **12 Apr 2023, 20:24**

joycerollins wrote: ↑31 Mar 2023, 20:50
u.biakoup wrote: ↑06 Sep 2022, 13:08 Hello,
A similar problem has already been dealt with here.
Please have a look here : https://revolutionpi.de/forum/viewtopic ... ect#p12597

Best Regards

Ulrich Kouatang Biakoup | Technical Support
Thank you very much!

Did you solve this? Also, would it help if we started using BalenaOS? I can paste the code here if necessary.

The Industrial Raspberry Pi Forum

Brownouts or power quality problems on RevPi?

Brownouts or power quality problems on RevPi?

Re: Brownouts or power quality problems on RevPi?

Re: Brownouts or power quality problems on RevPi?

Re: Brownouts or power quality problems on RevPi?