Problem with network


22 posts
by andyonahill » Thu Jun 07, 2012 3:10 pm
Hi All,

I have spent some time reading around this one, so I hope that it is not answered elsewhere.

My nice new shiny Pi arrived a few days ago. I got bored of waiting for an HDMI cable to arrive, so thought I would fire it up 'headless' on my network so I can have a quick play.

I flashed an SD card, enabled the SSH server and fired it up with just the power, SD card and network cable plugged in.

It booted up fine and took an address from my DHCP server, so I tried SSH and that worked.

All very good, then it lost connection and the network lights on the Pi went out!

Now when I boot, the network lights come on for a few seconds, the Pi connect to the network, then the connection dies.

I have attached the dmesg and syslog, which show errors when the network problems begin.

Just to confirm, I have nothing plugged into the USB ports or the HDMI port, just the SDcard and network cable. The network is plugged into a Netgear FS605 v3 switch on my desk.

I am using a HTC 5v/1A power supply with a thick USB cable and have confirmed that the voltage across TP1 and TP2 is in the range 4.9 to 5.2 volts. It does vary a little while the Pi is booting.

Hopefully my HDMI/DVI cable will arrive tomorrow, which means I can access the console and play a little more to see if I can work out what is going wrong.

Does anyone think I have a bad Pi or is this a software glitch?

Thanks

Andy
Attachments
pi_logs.tar.gz
dmesg and syslog from my Pi
(13.46 KiB) Downloaded 84 times
Posts: 5
Joined: Thu Jun 07, 2012 2:50 pm
by andyonahill » Fri Jun 08, 2012 9:32 am
Further info on this problem:

Booted the Pi this morning, the network connected (judging by the lights on the Pi and Switch), but did not try to access it at all, so it was only receiving network broadcast packets and response to DHCP and NTP requests (sent from the Pi).

It lasted about five minutes before the network lights went out and it dropped off the network.

Rebooted the Pi and the network does not connect at all. Just the Link light comes on and the hub shows no connection.

Going to power it off for 30 mins now and see if it then connects again for a short while.
Posts: 5
Joined: Thu Jun 07, 2012 2:50 pm
by andyonahill » Fri Jun 08, 2012 10:10 am
Yep, after about 30 mins it boots up OK with the network then fails afer a short time (3-5 mins).

Could this be an overheat or something?
Posts: 5
Joined: Thu Jun 07, 2012 2:50 pm
by LightAxe » Fri Jun 08, 2012 3:32 pm
Does your switch have its link light on for the Pi's port?
Posts: 14
Joined: Tue May 22, 2012 2:04 am
by andyonahill » Sat Jun 09, 2012 7:49 am
Hi lightaxe,

The link light is on while the pig's light are on then goes out when the pi does.

Cheers

Andy
Posts: 5
Joined: Thu Jun 07, 2012 2:50 pm
by andyonahill » Mon Jun 11, 2012 1:56 pm
Well, Monday is a new day for me and the Pi.

My HDMI->DVI cable arrived, so I hooked up the Pi to a monitor to see what I could do about the network problem. Sure enough the network and USB ports failed after a few minutes.

I picked up the Pi to pull the power and they came back to life!

So I squeezed everything around IC3 and the crystal on the back, and tried again.

Hey presto it is working and has been stable all day. Even the keyb and mouse work on use now.

So the moral of the story is, if it does not work, squeeze it!

Happy pi'ing
Posts: 5
Joined: Thu Jun 07, 2012 2:50 pm
by LightAxe » Fri Jun 15, 2012 11:00 pm
When in doubt... get a bigger hammer?
Posts: 14
Joined: Tue May 22, 2012 2:04 am
by Geert » Sat Jun 16, 2012 1:46 pm
I had exactly the same problem. Pi worked fine with the Debian distribution and with RaspBMC (tried both on different cards).
Now the network and the USB ports are gone. No network connection anymore, no keyboard, no mouse.
I don't know what you mean by fiddling, but i can't get it to work anymore. Is it dead?
I didn't do anything with it i was not supposed to do, so i am clueless.
Both Debian and RaspBMC boot fine, but without network and USB the whole device is pretty useless...
Posts: 2
Joined: Sat Jun 16, 2012 1:31 pm
by Geert » Sat Jun 16, 2012 4:35 pm
I have just put the Pi in the fridge for an hour, it is back alive.
Puzzling. Will it keep working?
Posts: 2
Joined: Sat Jun 16, 2012 1:31 pm
by markyd » Tue Jun 19, 2012 8:08 pm
Glad to see I am not the only one! My Pi was working fine with the Debian Squeeze image, HDMI to TV, wireless keyboard and wired network that's it. Moved it to my office lab and now it dies after a few minutes, even in headless / keybordless mode :-( using the same Samsung 5V / 1000mA (off my Galaxy) charger and tried the new Wheezy image as well (looks fab for a couple of minutes) what's going on? Can ping it for 2 - 5 minutes then dead :-( its not even doing anything, none of the chips feel hot either.

Is the Pi dead or dying? HELP!!!!
Posts: 38
Joined: Fri Jan 13, 2012 11:40 am
by alfs » Tue Jun 19, 2012 8:33 pm
I'm having the same problems. I've tried both the squeeze image and now wheezy. Running off Samsung usb power adapter, 5V 1000mA (also tried other brands at 700 mA and a powered usb hub)
Posts: 1
Joined: Tue Jun 19, 2012 8:30 pm
by pjc123 » Wed Jun 20, 2012 8:17 pm
My pi was fine with the original Debian, but with Wheezy installed there is no longer a network connection. No network lights, no nuttin. I really hate to erase the Wheezy install to install Debian again just to see if it will work because it took a long time to go through all those Wheezy config screens. I would get another card, but if the pi is dead why spend more money.
Posts: 910
Joined: Thu Mar 29, 2012 3:37 pm
by pjc123 » Wed Jun 20, 2012 8:31 pm
Oops. spoke too soon. Bad ethernet cable. Everything is back up.
Posts: 910
Joined: Thu Mar 29, 2012 3:37 pm
by HugoTilapia » Wed Jun 20, 2012 10:30 pm
I have experienced a similar problem. My Pi arrived June, 11, and the ethernet worked until the morning of June, 20. Both HDMI and ethernet were used extensively during this period (using OpenELEC to stream movies/music off an NFS server). Until the recent ethernet death the only issue I experienced was constant "buffering" on any 1080p videos.

The Pi streamed music for nearly 12 consecutive hours until the ethernet died. I rebooted and OpenELEC worked normally for a few minutes until it died again. Then I booted Debian Weezy and again the ethernet worked momentarily until dying. The next time I booted Debian I had a kernel panic.

For clarification, and to rule out power issues, this is the setup which worked without issue for over a week:

[*]HP Touchpad charger for power.
[*]MicroUSB cord for an HTC Aria

I make note of my power setup because the errors the Pi spits out into syslog are, as I gather from other discussions, associated with power issues. I even ran the Pi with just ethernet plugged in to rule out an HDMI issue, and the problem persisted.

Here's the log just before ethernet died:

Jun 20 11:43:46 raspberrypi kernel: [ 438.483851] hub 1-1:1.0: hub_port_status failed (err = -71)
Jun 20 11:43:46 raspberrypi kernel: [ 438.484009] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:46 raspberrypi kernel: [ 438.484022]
Jun 20 11:43:46 raspberrypi kernel: [ 438.484053] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:46 raspberrypi kernel: [ 438.484065]
Jun 20 11:43:46 raspberrypi kernel: [ 438.484177] hub 1-1:1.0: hub_port_status failed (err = -71)
Jun 20 11:43:46 raspberrypi kernel: [ 438.485647] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:46 raspberrypi kernel: [ 438.485665]
Jun 20 11:43:46 raspberrypi kernel: [ 438.485731] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:46 raspberrypi kernel: [ 438.485744]
Jun 20 11:43:46 raspberrypi kernel: [ 438.485977] hub 1-1:1.0: hub_port_status failed (err = -71)
Jun 20 11:43:47 raspberrypi kernel: [ 439.254029] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:47 raspberrypi kernel: [ 439.254052]
Jun 20 11:43:47 raspberrypi kernel: [ 439.333155] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:47 raspberrypi kernel: [ 439.333177]
Jun 20 11:43:47 raspberrypi kernel: [ 439.333236] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:47 raspberrypi kernel: [ 439.333249]
Jun 20 11:43:47 raspberrypi kernel: [ 439.333291] DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun 20 11:43:47 raspberrypi kernel: [ 439.333304]
Jun 20 11:43:47 raspberrypi kernel: [ 439.333391] hub 1-1:1.0: hub_port_status failed (err = -71)
Jun 20 11:43:47 raspberrypi kernel: [ 439.333418] hub 1-1:1.0: connect-debounce failed, port 1 disabled


Because there are thousands of relevant error messages in this log, I decided to tally up the top five errors:

6421 smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
1773 DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
66 hub 1-1:1.0: cannot reset port 3 (err = -71)
24 smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
24 smsc95xx 1-1.1:1.0: eth0: link down


As you can see, "smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114" is the most common message. What troubles me is that no changes were made to the working setup and software which could explain why it is not working. The only thing I haven't tried yet is to reflash an sdcard with the squeeze image. If that doesn't work I may have to RMA :(.
Posts: 3
Joined: Wed Jun 20, 2012 9:50 pm
by HugoTilapia » Thu Jun 21, 2012 12:06 am
UPDATE:

Tried a fresh Debian squeeze image, and the exact same thing happens. The error is consistent across different software.

Because of the way the Pi works, I believe that I'm dealing with a hardware fault. :(
Posts: 3
Joined: Wed Jun 20, 2012 9:50 pm
by HugoTilapia » Thu Jun 21, 2012 7:49 am
UPDATE: Tried using a different power source (HTC charger), observed identical behavior.

Also, I decided to tally up andyonahill's top five errors, and this was the result:
4116 DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
1301 smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
8 usb 1-1: device descriptor read/64, error -71
8 smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114
8 smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000118


So, our top two errors are the same, but swapped. As I ran tail -f /var/syslog these errors scrolled up at blinding speed. :?
Posts: 3
Joined: Wed Jun 20, 2012 9:50 pm
by rabbidrabbit » Thu Jun 21, 2012 7:34 pm
I've had the exact same problem. The network works for a few minutes, then fails. The network leds turn off, then keep cycling between on and off. Is there a solution to the problem?
Posts: 1
Joined: Thu Jun 21, 2012 7:32 pm
by Wohn » Fri Jun 22, 2012 4:13 am
On mine the led's don't go off. they are lit and link blinks, but no connection. Not a PS issue, kinda bummed out.
Posts: 2
Joined: Fri Jun 22, 2012 3:57 am
by show-p1984 » Wed Aug 22, 2012 10:42 am
I am facing a network failure too since today.
The symptoms however are different.
My Pi sometimes shows a network connection while there is none, or shows 1000Mbit connections where there are only 100Mbit available. Additionally to this "cosmetic" issue, there is no network traffic send out by the Pi (checked with my Cisco switch).
Sometimes the switch doesn't recognize a link at all (but the Pi does) and sometimes there is no full duplex link detected, but the link works to the switch.
However there is no data send whatsoever. The day before yesterday I outfitted my Pi with Heat-sinks on the Lan chip, SoC and main PWM to keep it cool. So I don't think that this is an overheating problem, though the Lan chip gets a bit warm (my infrared thermometer says it's @42°C with heatsink). Yes I read all about the regulator issues and that some ppl burn their hands on their lan chips, but my Pi is far from that. :)

I am almost at the point to RMA it, since I need the network connection for my appliances.
(Home server & weather station including: webcam, temp, wind speed, humidity, pressure, precipitation, forecast, database, etc... | which makes having an Ethernet port a necessity)
Posts: 2
Joined: Wed Aug 22, 2012 10:27 am
by show-p1984 » Wed Aug 22, 2012 11:48 am
UPDATE: (since edit isn't possible anymore =/)
After some more fiddling with the Pi I found another puzzling circumstance. If I start the Pi with network connected, it is not recognized (leds, or switch). However the LNK led blinks for a tenth of a second around 6 seconds after power on.
If I then remove the network cable, the Pi shows me a full duplex network connection... what the f...? :)
Now I reconnect the network cable and I see that the LNK led is blinking as it should when there would be traffic and the switch recognizes the link too, however the Pi does now put through DHCP DISCOVERS as it should be, but does not seem to get anything back since it is re-sending the DISCOVER over and over again and ultimately fails (see below for a wireshark/router log)
Whatever I do now (disconnecting everything except power from the Pi multiple times, put down the link from raspian), I can't get the Pi to see that there is no friggin network cable connected ^^
Only way: Cut the power.

Wireshark log: http://pastebin.com/raw.php?i=jPDdgxgF
Router: (pfsense)
Code: Select all
Aug 22 13:32:25   dhcpd: DHCPOFFER on 10.0.1.134 to b8:27:eb:9d:7b:25 (raspberrypi) via re0
Aug 22 13:32:24   dhcpd: DHCPDISCOVER from b8:27:eb:9d:7b:25 via re0


My conclusion:
The Pi does now send out data, but for some reason does not receive any.
In this case: DHCP DISCOVER is send, the router reacts and OFFERS an IP but the Pi does not seem to get that response.
Posts: 2
Joined: Wed Aug 22, 2012 10:27 am
by designsavage » Tue Sep 18, 2012 5:28 am
Hi,

Just wanted to post in case someone else runs into this issue. I was having the same problem with the usb and ethernet dropping out while trying to get raspmbc to run. Turned out that the power source I was using was not powerful enough.

Switching to a stronger power source (a laptop usb port) solved this issue for me.
Posts: 1
Joined: Tue Sep 18, 2012 5:26 am
by msakms » Fri Mar 29, 2013 10:30 pm
I had the same issue, however it was resolved once I removed the network bridge between my Ethernet & WLAN on windows 8. I hope this might come in handy for anyone.
Could anyone explain why it was resolved after removing the bridge?
I might dig deeper into that issue when I've time.
Cheers,
Posts: 1
Joined: Fri Mar 29, 2013 1:27 pm