Skip to content
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

smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000114: -110 #268

Closed
iz8mbw opened this issue Apr 29, 2014 · 26 comments

Comments

Projects
None yet
4 participants
@iz8mbw
Copy link

commented Apr 29, 2014

Hi,
with the latest firmware (Linux raspberrypi 3.12.18+ #677 PREEMPT Mon Apr 28 22:45:00 BST 2014 armv6l GNU/Linux
), I have in the masseges lots of the errors:

Apr 29 17:25:30 raspberrypi kernel: [  711.459215] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000114: -110
Apr 29 17:25:30 raspberrypi kernel: [  711.459243] smsc95xx 1-1.1:1.0 eth0: Error writing MII_ADDR
Apr 29 17:25:35 raspberrypi kernel: [  716.458984] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:35 raspberrypi kernel: [  716.459033] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:35 raspberrypi kernel: [  716.459052] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:41 raspberrypi kernel: [  722.558505] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:41 raspberrypi kernel: [  722.558555] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:41 raspberrypi kernel: [  722.558576] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:48 raspberrypi kernel: [  729.458191] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:48 raspberrypi kernel: [  729.458241] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:48 raspberrypi kernel: [  729.458260] smsc95xx 1-1.1:1.0 eth0: Timed out reading MII reg 01
Apr 29 17:25:48 raspberrypi kernel: [  730.054847] ttyUSB0: 1 input overrun(s)
Apr 29 17:25:48 raspberrypi kernel: [  730.059916] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:25:48 raspberrypi kernel: [  730.190480] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:25:53 raspberrypi kernel: [  735.187738] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:53 raspberrypi kernel: [  735.187770] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:53 raspberrypi kernel: [  735.187786] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:58 raspberrypi kernel: [  740.187405] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:58 raspberrypi kernel: [  740.187436] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:58 raspberrypi kernel: [  740.187472] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:04 raspberrypi kernel: [  746.187015] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:04 raspberrypi kernel: [  746.187046] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:04 raspberrypi kernel: [  746.187062] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:07 raspberrypi kernel: [  748.650790] ttyUSB0: 1 input overrun(s)

FYI on an USB port I have connected an Arduino Nano, the problems happens with this firmwmare, no problem withe the previously.

In the meantime the problem will be solved, how I can download the previous firmware with the rpi-update command?

Thanks.

@popcornmix

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2014

Can you try:
sudo rpi-update b842df82b33d8aafcd6c9be3b6a86cdc2f195ade
and reboot, and report if that works okay?

@iz8mbw

This comment has been minimized.

Copy link
Author

commented Apr 29, 2014

I'm trying,
in the mean time:

Apr 29 17:13:43 raspberrypi kernel: [    2.340278] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Apr 29 17:13:43 raspberrypi kernel: [    2.350158] VFS: Mounted root (ext4 filesystem) on device 179:2.
Apr 29 17:13:43 raspberrypi kernel: [    2.368497] devtmpfs: mounted
Apr 29 17:13:43 raspberrypi kernel: [    2.373531] Freeing unused kernel memory: 140K (c059d000 - c05c0000)
Apr 29 17:13:43 raspberrypi kernel: [    2.413068] usb 1-1: new high-speed USB device number 2 using dwc_otg
Apr 29 17:13:43 raspberrypi kernel: [    2.421762] Indeed it is in host mode hprt0 = 00001101
Apr 29 17:13:43 raspberrypi kernel: [    2.623454] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Apr 29 17:13:43 raspberrypi kernel: [    2.631761] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 29 17:13:43 raspberrypi kernel: [    2.642546] hub 1-1:1.0: USB hub found
Apr 29 17:13:43 raspberrypi kernel: [    2.648070] hub 1-1:1.0: 3 ports detected
Apr 29 17:13:43 raspberrypi kernel: [    2.933221] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Apr 29 17:13:43 raspberrypi kernel: [    3.043493] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Apr 29 17:13:43 raspberrypi kernel: [    3.052065] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 29 17:13:43 raspberrypi kernel: [    3.080060] smsc95xx v1.0.4
Apr 29 17:13:43 raspberrypi kernel: [    3.150623] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:30:43:fd
Apr 29 17:13:43 raspberrypi kernel: [    3.253227] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Apr 29 17:13:43 raspberrypi kernel: [    3.736732] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
Apr 29 17:13:43 raspberrypi kernel: [    3.753229] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 29 17:13:43 raspberrypi kernel: [    3.762391] usb 1-1.2: Product: FT232R USB UART
Apr 29 17:13:43 raspberrypi kernel: [    3.776416] usb 1-1.2: Manufacturer: FTDI
Apr 29 17:13:43 raspberrypi kernel: [    3.782215] usb 1-1.2: SerialNumber: A987J9HH
Apr 29 17:13:43 raspberrypi kernel: [    5.144404] bcm2708_i2c_init_pinmode(0,0)
Apr 29 17:13:43 raspberrypi kernel: [    5.150231] bcm2708_i2c_init_pinmode(0,1)
Apr 29 17:13:43 raspberrypi kernel: [    5.351355] bcm2708_i2c bcm2708_i2c.0: BSC0 Controller at 0x20205000 (irq 79) (baudrate 100k)
Apr 29 17:13:43 raspberrypi kernel: [    5.513153] bcm2708_i2c_init_pinmode(1,2)
Apr 29 17:13:43 raspberrypi kernel: [    5.519101] bcm2708_i2c_init_pinmode(1,3)
Apr 29 17:13:43 raspberrypi kernel: [    5.682053] bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100k)
Apr 29 17:13:43 raspberrypi kernel: [    6.097036] usbcore: registered new interface driver usbserial
Apr 29 17:13:43 raspberrypi kernel: [    6.334332] usbcore: registered new interface driver usbserial_generic
Apr 29 17:13:43 raspberrypi kernel: [    6.342870] usbserial: USB Serial support registered for generic
Apr 29 17:13:43 raspberrypi kernel: [    6.622726] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
Apr 29 17:13:43 raspberrypi kernel: [    6.780587] usbcore: registered new interface driver ftdi_sio
Apr 29 17:13:43 raspberrypi kernel: [    6.879507] usbserial: USB Serial support registered for FTDI USB Serial Device
Apr 29 17:13:43 raspberrypi kernel: [    7.006767] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Apr 29 17:13:43 raspberrypi kernel: [    7.115279] usb 1-1.2: Detected FT232RL
Apr 29 17:13:43 raspberrypi kernel: [    7.120912] usb 1-1.2: Number of endpoints 2
Apr 29 17:13:43 raspberrypi kernel: [    7.222346] usb 1-1.2: Endpoint 1 MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.269737] usb 1-1.2: Endpoint 2 MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.316010] usb 1-1.2: Setting MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.370805] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
Apr 29 17:13:43 raspberrypi kernel: [    7.580153] pcm512x: probe of 1-004c failed with error -5
Apr 29 17:13:43 raspberrypi kernel: [   10.312607] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Apr 29 17:13:43 raspberrypi kernel: [   10.769151] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Apr 29 17:13:43 raspberrypi kernel: [   11.616080] Driver for 1-wire Dallas network protocol.
Apr 29 17:13:43 raspberrypi kernel: [   11.989744] i2c /dev entries driver
Apr 29 17:13:43 raspberrypi kernel: [   17.020001] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 29 17:13:43 raspberrypi kernel: [   19.635898] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:13:43 raspberrypi kernel: [   21.232155] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Apr 29 17:13:43 raspberrypi kernel: [   22.221313] bcm2835-cpufreq: switching to governor ondemand
Apr 29 17:13:43 raspberrypi kernel: [   22.221321] bcm2835-cpufreq: switching to governor ondemand
Apr 29 17:13:44 raspberrypi kernel: [   24.418893] Adding 102396k swap on /var/swap.  Priority:-1 extents:129 across:1754856k SSFS
Apr 29 17:13:54 raspberrypi kernel: [   34.046765] tun: Universal TUN/TAP device driver, 1.6
Apr 29 17:13:54 raspberrypi kernel: [   34.046799] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Apr 29 17:25:30 raspberrypi kernel: [  711.459215] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000114: -110
Apr 29 17:25:30 raspberrypi kernel: [  711.459243] smsc95xx 1-1.1:1.0 eth0: Error writing MII_ADDR
Apr 29 17:25:35 raspberrypi kernel: [  716.458984] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:35 raspberrypi kernel: [  716.459033] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:35 raspberrypi kernel: [  716.459052] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:41 raspberrypi kernel: [  722.558505] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:41 raspberrypi kernel: [  722.558555] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:41 raspberrypi kernel: [  722.558576] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:48 raspberrypi kernel: [  729.458191] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:48 raspberrypi kernel: [  729.458241] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:48 raspberrypi kernel: [  729.458260] smsc95xx 1-1.1:1.0 eth0: Timed out reading MII reg 01
Apr 29 17:25:48 raspberrypi kernel: [  730.054847] ttyUSB0: 1 input overrun(s)
Apr 29 17:25:48 raspberrypi kernel: [  730.059916] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:25:48 raspberrypi kernel: [  730.190480] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:25:53 raspberrypi kernel: [  735.187738] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:53 raspberrypi kernel: [  735.187770] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:53 raspberrypi kernel: [  735.187786] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:25:58 raspberrypi kernel: [  740.187405] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:25:58 raspberrypi kernel: [  740.187436] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:25:58 raspberrypi kernel: [  740.187472] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:04 raspberrypi kernel: [  746.187015] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:04 raspberrypi kernel: [  746.187046] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:04 raspberrypi kernel: [  746.187062] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:07 raspberrypi kernel: [  748.650790] ttyUSB0: 1 input overrun(s)
Apr 29 17:26:10 raspberrypi kernel: [  751.186694] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:10 raspberrypi kernel: [  751.186730] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:10 raspberrypi kernel: [  751.186765] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:15 raspberrypi kernel: [  757.186316] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:15 raspberrypi kernel: [  757.186347] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:15 raspberrypi kernel: [  757.186363] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:20 raspberrypi kernel: [  762.185991] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:20 raspberrypi kernel: [  762.186045] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:20 raspberrypi kernel: [  762.186064] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:26 raspberrypi kernel: [  768.185610] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:26 raspberrypi kernel: [  768.185641] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:26 raspberrypi kernel: [  768.185679] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:26:31 raspberrypi kernel: [  773.185282] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:26:31 raspberrypi kernel: [  773.185335] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:26:31 raspberrypi kernel: [  773.185353] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:27:06 raspberrypi kernel: [  807.753046] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:27:06 raspberrypi kernel: [  807.753077] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:27:06 raspberrypi kernel: [  807.753094] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:27:11 raspberrypi kernel: [  812.752727] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:27:11 raspberrypi kernel: [  812.752759] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:27:11 raspberrypi kernel: [  812.752793] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:27:32 raspberrypi kernel: [  833.715444] ttyUSB0: 1 input overrun(s)
Apr 29 17:27:41 raspberrypi kernel: [  842.500808] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000114: -110
Apr 29 17:27:41 raspberrypi kernel: [  842.500858] smsc95xx 1-1.1:1.0 eth0: Error writing MII_ADDR
Apr 29 17:27:42 raspberrypi kernel: [  843.500838] ttyUSB0: 1 input overrun(s)
Apr 29 17:27:53 raspberrypi kernel: [  854.450031] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000118: -110
Apr 29 17:27:53 raspberrypi kernel: [  854.450060] smsc95xx 1-1.1:1.0 eth0: Error reading MII_DATA
Apr 29 17:27:53 raspberrypi kernel: [  854.948224] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:27:53 raspberrypi kernel: [  855.062844] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 29 17:27:58 raspberrypi kernel: [  860.059671] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:27:58 raspberrypi kernel: [  860.059701] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:27:58 raspberrypi kernel: [  860.059718] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:03 raspberrypi kernel: [  865.059358] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:03 raspberrypi kernel: [  865.059390] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:03 raspberrypi kernel: [  865.059424] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:09 raspberrypi kernel: [  870.722634] ttyUSB0: 1 input overrun(s)
Apr 29 17:28:09 raspberrypi kernel: [  871.058966] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:09 raspberrypi kernel: [  871.058997] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:09 raspberrypi kernel: [  871.059013] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:14 raspberrypi kernel: [  876.058635] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:14 raspberrypi kernel: [  876.058665] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:14 raspberrypi kernel: [  876.058701] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:20 raspberrypi kernel: [  882.058262] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:20 raspberrypi kernel: [  882.058292] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:20 raspberrypi kernel: [  882.058311] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:25 raspberrypi kernel: [  887.057932] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:25 raspberrypi kernel: [  887.057985] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:25 raspberrypi kernel: [  887.058004] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:31 raspberrypi kernel: [  893.057538] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:31 raspberrypi kernel: [  893.057568] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:31 raspberrypi kernel: [  893.057586] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:36 raspberrypi kernel: [  898.057219] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:36 raspberrypi kernel: [  898.057271] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:36 raspberrypi kernel: [  898.057290] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:42 raspberrypi kernel: [  904.056838] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:42 raspberrypi kernel: [  904.056888] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:42 raspberrypi kernel: [  904.056907] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
Apr 29 17:28:47 raspberrypi kernel: [  909.056513] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Apr 29 17:28:47 raspberrypi kernel: [  909.056562] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Apr 29 17:28:47 raspberrypi kernel: [  909.056581] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read

The Arudino is seem like ttyUSB0:

Apr 29 17:13:43 raspberrypi kernel: [    7.006767] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Apr 29 17:13:43 raspberrypi kernel: [    7.115279] usb 1-1.2: Detected FT232RL
Apr 29 17:13:43 raspberrypi kernel: [    7.120912] usb 1-1.2: Number of endpoints 2
Apr 29 17:13:43 raspberrypi kernel: [    7.222346] usb 1-1.2: Endpoint 1 MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.269737] usb 1-1.2: Endpoint 2 MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.316010] usb 1-1.2: Setting MaxPacketSize 64
Apr 29 17:13:43 raspberrypi kernel: [    7.370805] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
@iz8mbw

This comment has been minimized.

Copy link
Author

commented Apr 29, 2014

With the version "b842df82b33d8aafcd6c9be3b6a86cdc2f195ade" (Linux raspberrypi 3.12.18+ #676 PREEMPT Mon Apr 28 21:52:32 BST 2014 armv6l GNU/Linux) works OK.

@popcornmix

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2014

Okay, looks like a FIQ FSM issue. You should follow this thread:
http://www.raspberrypi.org/forums/viewtopic.php?f=28&t=70437

The latest firmware will probably work with "dwc_otg.fiq_fsm_enable=0" added to cmdline.txt.

@P33M

This comment has been minimized.

Copy link

commented Apr 29, 2014

Thanks for the datapoint.

This shows that this particular problem is reproducible only with bulk split-transaction endpoints.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented Apr 30, 2014

So the solution for using always the latest firmware is to add "dwc_otg.fiq_enable=1" and "dwc_otg.fiq_fsm_enable=1" to the cmdline.txt ?

@popcornmix

This comment has been minimized.

Copy link
Contributor

commented Apr 30, 2014

@iz8mbw I don't understand.
dwc_otg.fiq_enable=1" and "dwc_otg.fiq_fsm_enable=1" are defaults so there is no point in adding them to cmdline.txt.

If you are having issues with FIQ FSM, then adding "dwc_otg.fiq_fsm_enable=0" may be a workaround.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 1, 2014

By default the cmdline.txt in my Raspberry Pi does not have dwc_otg.fiq_enable=1" and "dwc_otg.fiq_fsm_enable=1" but it has only "dwc_otg.lpm_enable=0".
This is my original cmdline.txt:

"dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

So now, how should I set the cmdline.txt?
Thanks!

@popcornmix

This comment has been minimized.

Copy link
Contributor

commented May 1, 2014

Remove dwc_otg.lpm_enable=0 (which is a default) and you'll be fine.
The default options don't need to be specified in cmdline.txt.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

Hi.
Now it's OK, I'm running the latest firmware (Linux raspberrypi 3.12.18+ #679 PREEMPT Thu May 1 14:40:27 BST 2014 armv6l GNU/Linux) and this is my cmdline.txt:

"dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

I hope this configuration is the optimal also for USB and Ethernet throughput.

@ghollingworth

This comment has been minimized.

Copy link

commented May 2, 2014

Sorry, I didn't mean to close!

You should try again without the fiq stuff in the cmdline.txt

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

There has recently been a fix due to some randomness in the kernel update form 3.10 to 3.12 and this problem may now have been fixed

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

It works well also with this cmdline.txt:

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

Now, do I leave the cmdline.txt without the various dwc_otg options?

@ghollingworth

This comment has been minimized.

Copy link

commented May 2, 2014

Yes, you shouldn't disable the fsm unless it's really causing a problem... Just don't want to spread dis-information that's all...

Leave this open until you're happy it's really fine...

Gordon

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

Hi again, sorry but it does not work with this cmdline.txt:

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

Here the messages:

May 2 10:32:59 raspberrypi kernel: [ 1203.911152] ttyUSB0: 1 input overrun(s)
May 2 10:33:04 raspberrypi kernel: [ 1209.591442] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
May 2 10:33:04 raspberrypi kernel: [ 1209.591495] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
May 2 10:33:04 raspberrypi kernel: [ 1209.591514] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
May 2 10:33:09 raspberrypi kernel: [ 1214.591124] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
May 2 10:33:09 raspberrypi kernel: [ 1214.591155] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
May 2 10:33:09 raspberrypi kernel: [ 1214.591170] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
May 2 10:33:15 raspberrypi kernel: [ 1220.590740] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
May 2 10:33:15 raspberrypi kernel: [ 1220.590770] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
May 2 10:33:15 raspberrypi kernel: [ 1220.590786] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read
May 2 10:33:20 raspberrypi kernel: [ 1225.590419] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
May 2 10:33:20 raspberrypi kernel: [ 1225.590450] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
May 2 10:33:20 raspberrypi kernel: [ 1225.590489] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read

May 2 10:42:22 raspberrypi kernel: [ 1767.135417] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110
May 2 10:42:28 raspberrypi kernel: [ 1773.135046] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110
May 2 10:42:34 raspberrypi kernel: [ 1779.134622] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110
May 2 10:42:40 raspberrypi kernel: [ 1785.134236] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110
May 2 10:42:46 raspberrypi kernel: [ 1791.133950] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110
May 2 10:42:52 raspberrypi kernel: [ 1797.133466] smsc95xx 1-1.1:1.0 eth0: Failed to write reg index 0x00000014: -110

The problem happens after some minutes and the ethernet goes down...
Now I'm trying with this cmdline.txt:

"dwc_otg.fiq_enable=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

I will inform to you.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

Same problem with this cmdline.txt:

"dwc_otg.fiq_enable=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

OK guys, in conclusion with the firmware "Linux raspberrypi 3.12.18+ #679 PREEMPT Thu May 1 14:40:27 BST 2014 armv6l GNU/Linux"

NOT works with the cmdline.txt setted to:

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

"dwc_otg.fiq_enable=1 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

Works with the cmdline.txt setted to:

"dwc_otg.fiq_fsm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

"dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

Now, how to go on?

@P33M

This comment has been minimized.

Copy link

commented May 2, 2014

Good. It seems that fiq_fsm causes the problem.

It appears that you have a single FT232RL device attached to the USB ports, is this correct?

Are you actively accessing /dev/ttyUSB0? Does the problem still occur if you leave the Pi for some time without accessing /dev/ttyUSB0?

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 2, 2014

Yes, I have only a FT232RL device attached to the USB ports (Arduino).
Yes, I access to /dev/ttyUSB0 every 4 seconds.
About your third questions, I should test it and I will let you know.
Thanks!

@P33M

This comment has been minimized.

Copy link

commented May 3, 2014

I can replicate this issue.
Doing

while true; do
    stty -F /dev/ttyUSB0
done

on a FT323RL causes USB to drop out after a while.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 3, 2014

Yes, my script is similar, I also use stty.
The problem will be solved in a next firmware?

@P33M

This comment has been minimized.

Copy link

commented May 3, 2014

I can no longer cause USB to drop out with P33M/linux@d5c7eca applied.

It should be incorporated whenever the firmware next gets built.

@P33M

This comment has been minimized.

Copy link

commented May 3, 2014

Please retest with latest rpi-update firmware.

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 3, 2014

With "Linux raspberrypi 3.12.18+ #680 PREEMPT Sat May 3 19:29:46 BST 2014 armv6l GNU/Linux" it's seem to be OK after 15 minutes of test with this cmdline.txt:

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

If it will be always OK, is it ok to use that cmdline.txt (without any fiq_fsm options)?

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 4, 2014

OK guys, after more then 12 hours of test I can confirm that the problem is solved, I'm using this cmdline.txt:

"console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait"

I have had only this but only one time in 12 hours:

"May 3 22:02:07 raspberrypi kernel: [ 2619.813604] ttyUSB0: 1 input overrun(s)"

Many thanks for you support!!

@popcornmix

This comment has been minimized.

Copy link
Contributor

commented May 4, 2014

Okay to close?

@iz8mbw

This comment has been minimized.

Copy link
Author

commented May 4, 2014

For me, yes!

@popcornmix popcornmix closed this May 4, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.