I Woke up and my Pi was not connected to network

[pqwoerituytrueiwoq]

my pi runs heedlessly
i cant ssh in to fix the eth0 being down as eth0 need to be working to use ssh

[Wed Apr 30 11:03:57 2014] usb 1-1.1: USB disconnect, device number 3
[Wed Apr 30 11:03:57 2014] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[Wed Apr 30 11:03:57 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Wed Apr 30 11:03:57 2014] Indeed it is in host mode hprt0 = 00001101
[Wed Apr 30 11:03:57 2014] usb 1-1: reset high-speed USB device number 2 using dwc_otg
[Wed Apr 30 11:03:57 2014] Indeed it is in host mode hprt0 = 00001101
[Wed Apr 30 11:03:58 2014] usb 1-1.1: new high-speed USB device number 4 using dwc_otg
[Wed Apr 30 11:03:58 2014] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[Wed Apr 30 11:03:58 2014] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Wed Apr 30 11:03:58 2014] smsc95xx v1.0.4
[Wed Apr 30 11:03:59 2014] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a2:68:54
[Wed Apr 30 11:03:59 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Wed Apr 30 11:04:00 2014] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[Wed Apr 30 11:04:00 2014] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

I managed to hook up a old school av cable/keyboard to trouble shoot it this time
i got it working again with ifup eth0
i then made this script a root cron job that runs every minute

#!/bin/sh
checkNIC(){
    echo $(/sbin/ifconfig "$nic" | grep 10.0.0.25 | wc -l)
}
fixNIC(){
    echo "Attempting to fix NIC"
    /usr/sbin/service networking restart
    sleep 2
    echo "Attempting to configure $nic"
    /sbin/ifup "$nic"
    echo "Attempt Complete"
    sleep 13
}
nic="eth0"
if [ $(checkNIC) -ne 1 ];then
    log="/var/log/fixnic"
    if [ -f "$log.stop" ];then
        exit
    fi
    echo "BEGIN------$(date)------" >> "$log"
    dmesg -T | tail -15 >> "$log"
    echo "---------------------------------------------" >> "$log"
    mpc >> "$log"
    echo "END------------------------------------------" >> "$log"
    echo "$(fixNIC)" >> "$log"
    if [ $(checkNIC) -ne 1 ];then
        echo "---TRY_2---" >> "$log"
        /usr/sbin/service networking start >> "$log"
        echo "$(fixNIC)" >> "$log"
        if [ $(checkNIC) -ne 1 ];then
            touch "$log.stop"
        fi
    fi
fi

[pqwoerituytrueiwoq]

duplicate post, browser cache tricked me

[pqwoerituytrueiwoq]

my script manged to grab this

BEGIN------Thu May  1 07:02:01 EDT 2014------
[Wed Apr 30 12:03:11 2014] usb 1-1.3: USB disconnect, device number 5
[Wed Apr 30 12:03:11 2014] usb 1-1.3.4: USB disconnect, device number 6
[Thu May  1 07:01:35 2014] usb 1-1.1: USB disconnect, device number 4
[Thu May  1 07:01:35 2014] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[Thu May  1 07:01:35 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Thu May  1 07:01:35 2014] Indeed it is in host mode hprt0 = 00001101
[Thu May  1 07:01:35 2014] usb 1-1: reset high-speed USB device number 2 using dwc_otg
[Thu May  1 07:01:35 2014] Indeed it is in host mode hprt0 = 00001101
[Thu May  1 07:01:36 2014] usb 1-1.1: new high-speed USB device number 7 using dwc_otg
[Thu May  1 07:01:36 2014] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[Thu May  1 07:01:36 2014] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Thu May  1 07:01:36 2014] smsc95xx v1.0.4
[Thu May  1 07:01:37 2014] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a2:68:54
[Thu May  1 07:01:37 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Thu May  1 07:01:39 2014] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
END------------------------------------------

[widi2]

Slightly off topic, but the distro in question is not Debian. It's Raspbian, unless you flashed an image of Debian itself, obtained from debian.org.

[pqwoerituytrueiwoq]

Slightly off topic, but the distro in question is not Debian. It's Raspbian, unless you flashed an image of Debian itself, obtained from debian.org.

true, it is Raspbian
debian was a prefix option and Raspbian is not, figured debian would be close enough, lol

[tgalati4]

It seems like an ethernet chip problem. As I recall, the ethernet chip on the PI is shared with the USB controller and is not very robust. Put your finger on the chip and feel how warm it is. It could be failing. Some PI's are made better than others. What country manufactured yours?

I've seen demos of Pi's running 3D, 1080i movies using XBMC, so I know that the graphics can handle it, but I don't know if the movies were streamed or simply stored on the SD card. With a 100 MB/sec NIC, I doubt there is enough bandwidth. For music, 100 MB/sec is generally enough, but if your network traffic is heavy, then there could be dropouts and it's possible that the NIC driver needs tuning to handle it. Or the chip is failing.

[pqwoerituytrueiwoq]

The CPU is under 50C, have never seen over 48C
mpd is playing files stored on the sd card
My PI was made in the UK

i have tried to see bring the NIC down from high use and gave up after 6 hours of continuously running iperf in a loop
Surface temps:
The chip near the NIC measures at about 43C
the large cip in the middle measures at 37C
the voltage regulator measures at 40C

until i had it run mpd it never crashed (about 5 days of uptime)
when i had it run over night a couple times it when down the second time

If it is a temperature problem i will find out tomorrow, i have a 80mm fan cooling it, core temps is down 10C as a result

i really doubt it is a high network load causing it to go down, usage should have been idle at that time
mpd may be using the loopback address, i am not sure how it works i just know it continues running when the network goes down
it is running owncloud (only me using it and all computers except the PI were off)
it is running SSH and apt-cache-ng and apt-cache-ng was not receiving any request
the only thing i can see as a cause is mpd playing over the analog audio output
when i thought the issue was a lack of power i stopped playing mpd (it was in the paused state) and the crashes stopped, i got more power and used mpd playback and it crashed the 1st night
idk why mpd would cause eth0 to fail or cause anything to fail while not interrupting itself

[tgalati4]

Do some research on the analog sound. It's possible that the sound chip is also on the same die as the USB and NIC. That means playing audio with mpd will cause that chip to get doubly hot. If you are just playing files locally from the SD and not streaming then use mocp. I would only run mpd if you are streaming your tracks to other computers as a server, not as a media player.

moc - ncurses based console audio player
moc-ffmpeg-plugin - ncurses based console audio player - ffmpeg plugin

What are the CPU loads when idle?

[pqwoerituytrueiwoq]

on idle if i don't count top 1.5%
mpd uses 8.9% when playing
only other thing that really uses cpu is apache2

i had my 80mm fan keeping it super cool last night and it ran until the power went out for about 3 seconds at about 10:30 am, nothing crashed
how ever i upgraded my surge protector and got the speaker system on a surge protector last night also

i deiced to have it also be a media player since it was syncing my music via owncloud so it already had the audio files on the disk

the chip near the usb ports is the usb controller right? perhaps i should just slap a beefy heat sync on it (edit: yes it is and it is specked to handle 70C, unless it is defective it should not a thermal issue)

i should probably point out the times it did go down mpd would have been the only thing using and resources
by only i mean only, no video, no usb, no net activity

does moc have shuffle, repeat, replay gain and have a service user name?
i added www-data to the mpd group so it could read the music files in my owncloud folder

[tgalati4]

moc handles shuffle and repeat, but I don't know about replay gain. I'm not sure what server user name is. Moc has been around a long time and if useful for low resource machines. It's possible that your owncloud instance is causing network issues. Try turning it off and run mpd for several days and see if the network connection remains stable.