eth0: unexpected urb length?

[gmc]

I'm running a Pi with a wireless usb dongle and trying to resolve some intermittent crashing problems with my C code.

In the messages log I am seeing the following 2 errors appearing which don't look good:

smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0

Code: Select all

reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) debug(G) kill-all-tasks(I) thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W)

Any ideas what could cause these - My Pi is up to date, running wheezy 09/25

Code: Select all

[386694.266635] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[442496.144282] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[445196.543164] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[474897.250255] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[480298.176004] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[495598.126643] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[507298.940286] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[530351.266307] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) debug(G) kill-all-tasks(I) thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W)
[530479.926524] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) debug(G) kill-all-tasks(I) thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W)
[530480.911425] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) debug(G) kill-all-tasks(I) thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W)
[550500.155771] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[624303.031272] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[645903.861922] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[649504.807130] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[721507.389293] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[757508.144292] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[781809.405819] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0
[840311.393811] smsc95xx 1-1.1:1.0: eth0: unexpected urb length 0

[astrapotro]

Hello I'm having the same problem with the usb-eth0 bus. What's happening with that issue?
There's no much info trought the foundation and I've tested a lot of solutions provided by the community but no SOLUTION. I still can't resolve this, it's very frustrating and a HUGE problem for me because i was thinking to use 450 raspis for a project ... i'll buy a beaglebone black and change to it if it works better than raspi with this.

My installation is a pi powered with a 7 ports usb hub (2A psu) trought a usb-microusb. Attached to the hub I've 2 ftdi usb serial cables, a 3G modem and an usb radio sender/receiver.

Well, with this installation I have been working about 7 hours with this line appearing in kern.log and syslog every 20 minutes, sometimes repeating every minute:

Code: Select all

smsc95xx 1-1.1:1.0 eth0: unexpected urb length 0

This issue is deribating in more critical errors laterly, loosing comunnication with usb-eth0 bus:

Code: Select all

Jan 17 06:25:13 raspberrypi kernel: [63120.514926] ftdi_sio ttyUSB0: failed to get modem status: -110
Jan 17 06:25:17 raspberrypi kernel: [63123.945140] smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110
Jan 17 06:25:17 raspberrypi kernel: [63123.945173] smsc95xx 1-1.1:1.0 eth0: Error reading MII_ACCESS
Jan 17 06:25:17 raspberrypi kernel: [63123.945191] smsc95xx 1-1.1:1.0 eth0: MII is busy in smsc95xx_mdio_read

I've to say that with this installation the pi is having 4,85 V stablelly so i think this is not a power problem but a linux usb driver, a ftdi driver or a hardware architecture problem...

Someone has resolve it ?? What's going on with that??? There's no solution with kernel/firmware updates. I'm very frustrating and those errors are doing to lost very much time in my project.

H E L P !

[m4vr]

Hi,

i'm getting a similar error while accessing an USB-device -

https://github.com/raspberrypi/linux/issues/470

Hoping to find a solution...