Network problems and hangs... losing faith... (solved)

Managed to get it lose the network and just about stay alive long enough to dump syslog; looks like the whole USB subsystem went a bit funny.

The heavy spamming of syslog and kern.log hammered it pretty bad - I suspect if I'd had X up and running it would have crashed the Pi. Looks like once it got into the "unregistered net_device" messages I was getting @3500 lines per second in both file.

(For what it's worth it's currently running the wheezy beta although I've seen similar with others - is there somewhere better than a forum to send such logs?)

Code: Select all

Jul 10 17:03:21 raspberrypi dhclient: receive_packet failed on eth0: Network is down
Jul 10 17:03:21 raspberrypi kernel: [ 1833.871818] usb 1-1: USB disconnect, device number 2
Jul 10 17:03:21 raspberrypi kernel: [ 1833.871851] usb 1-1.1: USB disconnect, device number 3
Jul 10 17:03:21 raspberrypi kernel: [ 1833.872076] smsc95xx 1-1.1:1.0: eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Jul 10 17:03:22 raspberrypi ifplugd(eth0)[984]: Link beat lost.
Jul 10 17:03:22 raspberrypi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Jul 10 17:03:22 raspberrypi dhclient: send_packet: No such device
Jul 10 17:03:22 raspberrypi ifplugd(eth0)[984]: Exiting.
Jul 10 17:03:22 raspberrypi kernel: [ 1835.184686] usb 1-1.3: USB disconnect, device number 4
Jul 10 17:03:23 raspberrypi kernel: [ 1835.531818] usb 1-1: new high speed USB device number 6 using dwc_otg
Jul 10 17:03:23 raspberrypi kernel: [ 1835.732501] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Jul 10 17:03:23 raspberrypi kernel: [ 1835.732534] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:23 raspberrypi kernel: [ 1835.738551] hub 1-1:1.0: USB hub found
Jul 10 17:03:23 raspberrypi kernel: [ 1835.738829] hub 1-1:1.0: 3 ports detected
Jul 10 17:03:23 raspberrypi ntpd[1350]: Deleting interface #5 eth0, 192.168.2.131#123, interface stats: received=136, sent=136, dropped=0, active_time=1797 s
ecs
Jul 10 17:03:23 raspberrypi ntpd[1350]: 83.82.79.65 interface 192.168.2.131 -> (none)
Jul 10 17:03:23 raspberrypi ntpd[1350]: 192.53.103.108 interface 192.168.2.131 -> (none)
Jul 10 17:03:23 raspberrypi ntpd[1350]: 85.91.1.180 interface 192.168.2.131 -> (none)
Jul 10 17:03:23 raspberrypi ntpd[1350]: 89.104.194.131 interface 192.168.2.131 -> (none)
Jul 10 17:03:23 raspberrypi ntpd[1350]: Deleting interface #3 eth0, fe80::ba27:ebff:fe0d:21a#123, interface stats: received=0, sent=0, dropped=0, active_time
=1802 secs
Jul 10 17:03:23 raspberrypi ntpd[1350]: peers refreshed
Jul 10 17:03:23 raspberrypi kernel: [ 1836.011961] usb 1-1.1: new high speed USB device number 7 using dwc_otg
Jul 10 17:03:23 raspberrypi kernel: [ 1836.112222] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Jul 10 17:03:23 raspberrypi kernel: [ 1836.112267] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:23 raspberrypi kernel: [ 1836.115684] smsc95xx v1.0.4
Jul 10 17:03:23 raspberrypi kernel: [ 1836.187833] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:
0d:02:1a
Jul 10 17:03:23 raspberrypi kernel: [ 1836.282220] usb 1-1.3: new low speed USB device number 8 using dwc_otg
Jul 10 17:03:24 raspberrypi ifplugd(eth0)[1777]: ifplugd 0.28 initializing.
Jul 10 17:03:24 raspberrypi kernel: [ 1836.388266] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c31c
Jul 10 17:03:24 raspberrypi kernel: [ 1836.388303] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 10 17:03:24 raspberrypi kernel: [ 1836.388324] usb 1-1.3: Product: USB Keyboard
Jul 10 17:03:24 raspberrypi kernel: [ 1836.388352] usb 1-1.3: Manufacturer: Logitech
Jul 10 17:03:24 raspberrypi kernel: [ 1836.399754] input: Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input2
Jul 10 17:03:24 raspberrypi kernel: [ 1836.404915] generic-usb 0003:046D:C31C.0003: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-bcm2708_usb-
1.3/input0
Jul 10 17:03:24 raspberrypi ifplugd(eth0)[1777]: Using interface eth0/B8:27:EB:0D:02:1A with driver <smsc95xx> (version: 22-Aug-2005)
Jul 10 17:03:24 raspberrypi ifplugd(eth0)[1777]: Using detection mode: SIOCETHTOOL
Jul 10 17:03:24 raspberrypi kernel: [ 1836.427020] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 10 17:03:24 raspberrypi ifplugd(eth0)[1777]: Initialization complete, link beat not detected.
Jul 10 17:03:24 raspberrypi kernel: [ 1836.434487] input: Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/input/input3
Jul 10 17:03:24 raspberrypi kernel: [ 1836.437935] generic-usb 0003:046D:C31C.0004: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-bcm2708_usb-1.
3/input1
Jul 10 17:03:25 raspberrypi kernel: [ 1837.847108] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jul 10 17:03:25 raspberrypi kernel: [ 1837.849228] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Jul 10 17:03:25 raspberrypi kernel: [ 1838.122005] usb 1-1: USB disconnect, device number 6
Jul 10 17:03:25 raspberrypi kernel: [ 1838.122038] usb 1-1.1: USB disconnect, device number 7
Jul 10 17:03:25 raspberrypi kernel: [ 1838.122268] smsc95xx 1-1.1:1.0: eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Jul 10 17:03:25 raspberrypi kernel: [ 1838.127568] usb 1-1.3: USB disconnect, device number 8
Jul 10 17:03:26 raspberrypi kernel: [ 1838.532159] usb 1-1: new high speed USB device number 9 using dwc_otg
Jul 10 17:03:26 raspberrypi ifplugd(eth0)[1777]: Exiting.
Jul 10 17:03:26 raspberrypi kernel: [ 1838.772651] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Jul 10 17:03:26 raspberrypi kernel: [ 1838.772686] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:26 raspberrypi kernel: [ 1838.778683] hub 1-1:1.0: USB hub found
Jul 10 17:03:26 raspberrypi kernel: [ 1838.778975] hub 1-1:1.0: 3 ports detected
Jul 10 17:03:26 raspberrypi kernel: [ 1839.052103] usb 1-1.1: new high speed USB device number 10 using dwc_otg
Jul 10 17:03:26 raspberrypi kernel: [ 1839.152396] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Jul 10 17:03:26 raspberrypi kernel: [ 1839.152431] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:26 raspberrypi kernel: [ 1839.154374] usb 1-1.1: can't set config #1, error -110
Jul 10 17:03:26 raspberrypi kernel: [ 1839.154881] hub 1-1:1.0: hub_port_status failed (err = -19)
Jul 10 17:03:27 raspberrypi kernel: [ 1839.372093] usb 1-1: USB disconnect, device number 9
Jul 10 17:03:27 raspberrypi kernel: [ 1839.372127] usb 1-1.1: USB disconnect, device number 10
Jul 10 17:03:27 raspberrypi kernel: [ 1839.712021] usb 1-1: new high speed USB device number 11 using dwc_otg
Jul 10 17:03:27 raspberrypi kernel: [ 1839.912427] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Jul 10 17:03:27 raspberrypi kernel: [ 1839.912460] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:27 raspberrypi kernel: [ 1839.918345] hub 1-1:1.0: USB hub found
Jul 10 17:03:27 raspberrypi kernel: [ 1839.918626] hub 1-1:1.0: 3 ports detected
Jul 10 17:03:27 raspberrypi kernel: [ 1840.192096] usb 1-1.1: new high speed USB device number 12 using dwc_otg
Jul 10 17:03:28 raspberrypi kernel: [ 1840.292791] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Jul 10 17:03:28 raspberrypi kernel: [ 1840.292824] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 10 17:03:28 raspberrypi kernel: [ 1840.296222] smsc95xx v1.0.4
Jul 10 17:03:28 raspberrypi kernel: [ 1840.368089] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:
0d:02:1a
Jul 10 17:03:28 raspberrypi kernel: [ 1840.462399] usb 1-1.3: new low speed USB device number 13 using dwc_otg
Jul 10 17:03:28 raspberrypi ifplugd(eth0)[1853]: ifplugd 0.28 initializing.
Jul 10 17:03:28 raspberrypi kernel: [ 1840.568468] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c31c
Jul 10 17:03:28 raspberrypi kernel: [ 1840.568505] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 10 17:03:28 raspberrypi kernel: [ 1840.568607] usb 1-1.3: Product: USB Keyboard
Jul 10 17:03:28 raspberrypi kernel: [ 1840.568637] usb 1-1.3: Manufacturer: Logitech
Jul 10 17:03:28 raspberrypi kernel: [ 1840.580299] input: Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input4
Jul 10 17:03:28 raspberrypi kernel: [ 1840.586538] generic-usb 0003:046D:C31C.0005: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-bcm2708_usb-
1.3/input0
Jul 10 17:03:28 raspberrypi ifplugd(eth0)[1853]: Using interface eth0/B8:27:EB:0D:02:1A with driver <smsc95xx> (version: 22-Aug-2005)
Jul 10 17:03:28 raspberrypi ifplugd(eth0)[1853]: Using detection mode: SIOCETHTOOL
Jul 10 17:03:28 raspberrypi kernel: [ 1840.607693] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 10 17:03:28 raspberrypi ifplugd(eth0)[1853]: Initialization complete, link beat not detected.
Jul 10 17:03:28 raspberrypi kernel: [ 1840.616146] input: Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/input/input5
Jul 10 17:03:28 raspberrypi kernel: [ 1840.616752] generic-usb 0003:046D:C31C.0006: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-bcm2708_usb-1.
3/input1
Jul 10 17:03:28 raspberrypi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Jul 10 17:03:29 raspberrypi kernel: [ 1842.151802] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.159805] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.167805] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.175802] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.183805] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.191782] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:29 raspberrypi kernel: [ 1842.199803] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
...
Jul 10 17:03:31 raspberrypi kernel: [ 1844.159811] smsc95xx 1-1.1:1.0: eth0: kevent 4 may have been dropped
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166283] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166343] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166381] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166414] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000118
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166466] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166501] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166533] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166565] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000118
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166707] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166745] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166779] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166812] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000118
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166843] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000008
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166877] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166909] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.166940] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
...
Jul 10 17:03:31 raspberrypi kernel: [ 1844.188573] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.188604] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:31 raspberrypi kernel: [ 1844.188634] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 10 17:03:32 raspberrypi kernel: [ 1844.372316] usb 1-1: USB disconnect, device number 11
Jul 10 17:03:32 raspberrypi kernel: [ 1844.372350] usb 1-1.1: USB disconnect, device number 12
Jul 10 17:03:32 raspberrypi kernel: [ 1844.372577] smsc95xx 1-1.1:1.0: eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Jul 10 17:03:32 raspberrypi ifplugd(eth0)[1853]: Exiting.
Jul 10 17:03:36 raspberrypi kernel: [ 1849.182453] smsc95xx 1-1.1:1.0: (unregistered net_device): Failed to read register index 0x00000114
Jul 10 17:03:36 raspberrypi kernel: [ 1849.182492] smsc95xx 1-1.1:1.0: (unregistered net_device): MII is busy in smsc95xx_mdio_read
Jul 10 17:03:36 raspberrypi kernel: [ 1849.182531] smsc95xx 1-1.1:1.0: (unregistered net_device): Failed to read register index 0x00000114
Jul 10 17:03:36 raspberrypi kernel: [ 1849.182560] smsc95xx 1-1.1:1.0: (unregistered net_device): Failed to read register index 0x00000114
Jul 10 17:03:36 raspberrypi kernel: [ 1849.182588] smsc95xx 1-1.1:1.0: (unregistered net_device): Failed to read register index 0x00000114


Those are

I documented my findings in https://github.com/raspberrypi/linux/issues/29, but have yet to receive any response from anyone officially involved with the Pi. A little annoyed at that given I spent quite a few hours troubleshooting, borrowing the oscilloscope, etc.

We are tracking that issue, apologies you haven't had a response. Let me just say that we do *massively* appreciate it when users such as yourself take the time to debug the problem. Your reported issue is certainly puzzling. Other people in that issue have reported problems running out of periodic channels "schedule_periodic: No host channel available for periodic transfer." - we are actually testing a patch for that at the moment.

Interesting. I got the periodic transfer error with a different Logitech mouse & keyboard on a unifying reciever, but short of making a giant spreadsheet of hardware configurations, it was hard to capture every single thing I tried - so I stuck with 1 configuration I could replicate and change easily.

Managed to get it lose the network and just about stay alive long enough to dump syslog; looks like the whole USB subsystem went a bit funny.

The heavy spamming of syslog and kern.log hammered it pretty bad - I suspect if I'd had X up and running it would have crashed the Pi. Looks like once it got into the "unregistered net_device" messages I was getting @3500 lines per second in both file.

(For what it's worth it's currently running the wheezy beta although I've seen similar with others - is there somewhere better than a forum to send such logs?)

Those are the same errors I've seen when the USB subsystem goes south....

Well it's reassuring that we seem to be chasing the same problem, at least!

Interesting to see a mention of Logitech - my keyboard is also one of theirs, although wired rather than wireless. Seems unlikely, but I'll try reproducing it without the keyboard attached.

Have the same problem the Pi works fine for a while and then i can't connect using ssh.. I have notised that the MTU size is 1488 and not 1500??

Performing a test using 1500 right now..

Ok, well some testing overnight seems to have resulted in some progress and for me at least it starts to look like a hardware issue. I've managed to get the Pi completely stable (for 12 hours at least, which is way beyond anything I managed before) simply by shifting some networking around.

Now, the port (or router) that I've been using has always been perfectly happy running Windoze boxes but I can only assume it's unstable enough to confuse Linux somehow.

I know the OP said that they'd tried multiple different network hardware so it might not be a solution for everyone but it would appear that you can't just assume that a port / cable that works happy under Windows is stable enough for the Pi.

Hi guys,

My Pi is up for over 2 days now! I turned off the screensaver and energy saver features like described in: http://raspberrypi.stackexchange.com/questions/752/how-do-i-prevent-the-screen-from-going-blank.

same problem.
I tried installing deluged deluge-web.

Raspberry looses network connection after some minutes.

I use last official debian distro...

I've made some positive progress too, I took the Arduino (or more probably the USB) out of the equation and removed the rather intense port scanning out of my BASH scripts and the Pi has been rock solid stable for almost 3 days, and still doing network and internet access every minute. I also reduced the ARM cpu speed to 500 Mhz, but that may have been unnecessary Much of the problem seems to have been I'm expecting too much, it all works perfectly on my hacked NAS box, but that is a more powerful ARM running at 1200 Mhz. And doesn't have the 'unholy bodge' of a USB and network system joined at the hip. I think with a bit of lateral thinking and a realistic workload I can make the Pi do something useful. The Puppy suggestion was a bit on a non starter because its difficult to take the GUI out of the equation. (Not everyone want to use a Pi as a desktop substitute, - I've absolutely nothing against Linux on the desktop, I use it full time, but its on a far more capable platform than the Pi could ever be). I'm back on Arch Linux on the Pi, because that is closest to what I want 'out of the box'. I even prefer pacman to apt-get, pity its such a naff name for a package manager......

After days of trying Success. A replacement power adaptor from MicroMundi ( I purchased the Pi package) done the trick. I havent been able to test exhaustively, but Pi stayed stable from shell and GUI, for about half an hour. The question now is why?

AC/DC Adaptor details
Model No. NO 0501000U
Input 100-240V AC 50/60 Hz
0 - 18 A Max
Output DC 5V 1000mA
I know nothing unusual there.

Matthew Holt from MicroMundi is willing to supply more technical information than I can elude to.

Hope this helps someone out there.

Seeing the same type of thing. Syslog logging 200+ events per second.
Also have Logitech USB devices.

Has anyone noted the fact that this issue only happens under the desktop.. ie from the command line there is no problem...

M

I'm seeing the same problems here. I just got my pi yesterday and it booted up great. I ironed out a couple of kinks and everything was working fine.
When I booted my pi this morning shortly after starting LXDE everything froze, no keyboard no mouse. I started touching the chips to see if it was overheating and noticed the smaller chip next to the USB ports was toasty warm. So I panicked and tried shutting down, but since the mouse and kb were gone I had to hard power it off. I know bad bad bad, but I didn't want my pi to start smoking.
When I rebooted after letting it cool off I couldn't start LXDE, but could do anything I wanted in console. I thought maybe I did something to corrupt my image messing around last night so I decided to just go ahead and reimage the sd card.
After reimaging still saw the same problems pi freezing and chip getting warm. So I imaged a new sd card starting completely from scratch. It booted up fine and has been sitting here idling for 4 or 5 hours and its not freezing up. I don't have the eth cable plugged in at this point.
As soon as I plug the eth cable in that chips warms up, without it plugged in the pi seems stable.
This image that running now is a fresh right out of the box image, and I haven't installed or even updated it.
I've moved the eth cable to different routers and switches and still get the same results.
So at this point I'm kinda stumped as what to try next. I might go ahead and make a wheezy or arch image and see what that does.

Any thought wold be helpful.
Thanks

Ok. It is a USB power issue.

Not running in the desktop clearly also implies drawing less power so that is why it does not crop up on the command line.

Simple test is to ping something and unplug USB device. Can also monitor syslog with tail -100f,
but it proves that the moment the (powered) USB device is removed the ping time drop with factor 100-1000. Also syslog spamming ceases.

Plugging USB back in goes back to previous state.

For the record, running Wheezy and Logitech KB & Mouse via KVM powered via USB.

Will play with power config to see....

See also this post:
http://www.frambozenbier.org/index.php/ ... uggestions

I plugged my eth cable in and started a ping to my desktop.
Unplugged the mouse and kb..... chips still gets hot after just a few seconds....
I really don't want to leave the eth cable in and stress that chip....and have it die or degrade it.

Monitored chip temperatures.

Seems to get warmer with network cable plugged in.
Both on command line and under desktop.

Critically it keeps working under command line. (stably - I ran it for couple of hours, pinging my router)

Under the desktop, network works only if USB keyboard / KVM is unplugged.
However, both chips gets positively toasty.

Curiously the addition of a powered USB hub has not effect. It seems to be presence of KVM/kb/mouse

Will try simple USB kb directly on device next. This should work...

Just wanted to post I was having this same problem with a log similar to ganders and just switched to arch linux and now I don't get the Network Unreachable error.

After a few hours network was unreachable again.

looks like the whole USB subsystem went a bit funny.

This may be totally unrelated, but I post it anyway in the hope it may be useful.

I found this topic (ganders' post) with google when I searched for:

Code: Select all

smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
smsc95xx 1-1.1:1.0: (unregistered net_device): MII is busy in smsc95xx_mdio_read

In the past few days I've been reading data from a USB-joystick ('/dev/input/js0') as well as sending data back and forth to my laptop with a Bluetooth USB dongle. Both USB devices are directly in the USB port of the raspi. I didn't run into problems at all with that, being logged in with ssh from my main computer.

For obvious reasons, I bought a 7-port powered Sitecom USB hub this afternoon. That's when the errors mentioned above started showing up. When I plug everything (logitech optical mouse, logitech simple keyboard, USB joystick and SomeNameLessBrand Bluetooth dongle) in the USB hub and try to read the joystick, it doesn't work and my dmesg shows total mayhem. Lots of these:

Code: Select all

[ 2099.821418] INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
[ 2099.821435]
[ 2099.821455] INFO:: schedule_periodic: No host channel available for periodic transfer.
[ 2099.821467]
[ 2099.821487] ERROR::dwc_otg_hcd_urb_enqueue:518: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
[ 2099.821500]
[ 2099.931421] INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
[ 2099.931438]
[ 2099.931456] INFO:: schedule_periodic: No host channel available for periodic transfer.
[ 2099.931469]
[ 2099.931489] ERROR::dwc_otg_hcd_urb_enqueue:518: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
[ 2099.931502]
[ 2100.041434] INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
[ 2100.041450]
[ 2100.041471] INFO:: schedule_periodic: No host channel available for periodic transfer.
[ 2100.041483]
[ 2100.041503] ERROR::dwc_otg_hcd_urb_enqueue:518: DWC OTG HCD URB Enqueue failed adding QTD. Error status -4008
[ 2100.041517]
[ 2100.311707] usb 1-1.2: reset low speed USB device number 18 using dwc_otg

After unplugging the bluetooth dongle from the USB hub, I still get the 'smsc95xx' error in dmesg, and the Joystick 'sort of' works. That is: most of the time, but there are 'hickups'. Not very reliable. It misses buttonpresses. During all this, there's nothing wrong with the ethernet. I'm not being logged out of the ssh session on the raspi or anything. It's just the USB failing epically. The joystick (at least) disconnects and enumerates again, but I think I remember seeing the full hub going down.

Without the USB hub everything is fine, so I blame it on the USB hub for now. Sorry if this has nothing to do with the original problem. I'm not necessarily looking for answers here, but it might trigger something with someone.

For obvious reasons, I bought a 7-port powered Sitecom USB hub this afternoon. That's when the errors mentioned above started showing up. When I plug everything (logitech optical mouse, logitech simple keyboard, USB joystick and SomeNameLessBrand Bluetooth dongle) in the USB hub and try to read the joystick, it doesn't work and my dmesg shows total mayhem. Lots of these:

[code][ 2099.821418] INFO:: periodic_channel_available: Total channels: 8, Periodic: 6, Non-periodic: 2
[ 2099.821455] INFO:: schedule_periodic: No host channel available for periodic transfer.

The "INFO:: schedule_periodic: No host channel available for periodic transfer" message is a known symptom of an issue that is being looked at. See this thread: https://github.com/raspberrypi/linux/issues/29#issuecomment-6882473

The "INFO:: schedule_periodic: No host channel available for periodic transfer" message is a known symptom of an issue that is being looked at. See this thread: https://github.com/raspberrypi/linux/issues/29#issuecomment-6882473

Thanks!
I upgraded to Raspbian late last night. Plugged everything in the USB hub, and the joystick seems to work. No more mayhem in dmesg. Only a single 'smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114' each time I run my app.
I'll test further and report to the correct topic next time. Thanks again! I hope the network issue will also be solved quickly.

I tried raspbian last night (hexxeh's build) but still got the same problems.

My RPi hangs if too much traffic. For example if I transfer a directory with many pictures.
I think it is partially due to overheating of network chip. If I put a fan it becomes less frequent.
Another couase could be USB connection as I use USB HDD.

If no much traffic RPI can ran for a day.

I think it's necessary to keep bumping these threads as they are mostly connected. Those with usb/network clashes that have taken the time to test and diagnose are seeing definite issues with operation of mixed high and low power USB devices, which do not seem to be power supply or hub quality related. It appears that the mouse/network combination is most toxic when a hub is involved and this shows itself only after enabling an X-windows environment (the mouse isn't needed until then). It can throw any USB connected device (including the Ethernet which shares USB channels) into a spin.

To the OP and others posting on these topics - If you don't believe your power supply is the issue then checkout the Github issue raised by Marsman2020:
https://github.com/raspberrypi/linux/issues/29#
Show your support for an urgent investigation and fix to this issue by commenting on this thread and others like it.

Bumping the topic.

Hi

Same problem here...

A few minutes after starting transmission-daemon, I get a flooding in syslog with this message:

[ 1566.807512] smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped
[ 1566.807541] smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped

After a few seconds the network connection goes down, and restarting the service is useless, so I need to restart the rasPi.

I have limited the active peers, let's see if I can see any improvement.

Keep you posted

I'm running on raspbian (official build) and do also experience strange stability problems.

Code: Select all

Jul 22 12:26:20 raspberrypi kernel: [  690.806297] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 22 16:55:03 raspberrypi kernel: [ 3929.575045] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Jul 22 18:16:32 raspberrypi kernel: [  228.808247] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000118
pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux


I'm using the recommended power supply from RS and the recommended 4GB SD card.

The only additional thing I use is a wifi dongle. No other USB device, no cabled network. I get freezes every now and then, but ironically not under high CPU conditions (tested with 'openssl speed', dd, etc.).

Code: Select all

pi@raspberrypi ~ $ uprecords
     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
     1     1 day , 04:41:55 | Linux 3.1.9+              Wed Jul 18 19:11:14 2012
     2     1 day , 02:28:48 | Linux 3.1.9+              Fri Jul 20 16:37:06 2012
->   3     0 days, 23:58:25 | Linux 3.1.9+              Sat Jul 21 19:32:44 2012
     4     0 days, 16:16:50 | Linux 3.1.9+              Thu Jul 19 23:56:39 2012
     5     0 days, 00:20:14 | Linux 3.1.9+              Sat Jul 21 19:11:05 2012

The only thing I can do if my system freezes is to power cycle it. It does not respond to any network services anymore and if I plug in a composite cable to watch for on screen messages, I receive a signal but the screen is simply black.

I'm not quite happy with this situation as with raspbian, the Pi would finally be able to act as a small home server.