I Woke up and my Pi was not connected to network

[pqwoerituytrueiwoq]

i have gone several days (at least 5) without mpd running and everything else i use running without issue (and that was on a measly 500mA of juice)
unless mpd is the straw that broke the camels back i dont see that making a difference
but moc does have it's own user like mpd does? it runs as a service right not just a user application (for example apache2 runs as a service while gmusicbrowser is a user app)

[pqwoerituytrueiwoq]

cooling is not the issue, had it 5C below normal idle and it crashed

BEGIN------Sat May  3 07:48:01 EDT 2014------
[Fri May  2 17:18:28 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Fri May  2 17:18:29 2014] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[Sat May  3 07:47:08 2014] usb 1-1.1: USB disconnect, device number 3
[Sat May  3 07:47:08 2014] smsc95xx 1-1.1:1.0 eth0: unregister 'smsc95xx' usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
[Sat May  3 07:47:08 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Sat May  3 07:47:08 2014] Indeed it is in host mode hprt0 = 00001101
[Sat May  3 07:47:08 2014] usb 1-1: reset high-speed USB device number 2 using dwc_otg
[Sat May  3 07:47:08 2014] Indeed it is in host mode hprt0 = 00001101
[Sat May  3 07:47:09 2014] usb 1-1.1: new high-speed USB device number 4 using dwc_otg
[Sat May  3 07:47:09 2014] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[Sat May  3 07:47:09 2014] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Sat May  3 07:47:09 2014] smsc95xx v1.0.4
[Sat May  3 07:47:09 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
[Sat May  3 07:47:09 2014] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[Sat May  3 07:47:11 2014] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
---------------------------------------------

[pqwoerituytrueiwoq]

Looks like it was a kernel issue, seems to be fixed in the 3.12.18+ kernel that i got via the rpi-update command (if it does not crash by tomorrow i will mark this as as solved)