----------------eredeti üzenet----------------- Feladó: [email protected] Címzett: [email protected] Dátum: Wed, 25 Sep 2013 15:13:39 +0200 ------------------------------------------------- > > Zitat von Pongrácz István : > >> Hi, >> >> I found that, with the recent pve kernel the network controller just >> crash and cannot back to life again without power off/on the system. >> >> This occurs on a almost no-traffic interface after 1-2 days. >> > > Looks like the packet of death to me: > http://blog.krisk.org/2013/02/packets-of-death-update.html > What Motherboard are you using and are you able to update the BIOS? > > Regards
Thank you guys for the hints! So, I upgraded to the latest 2.6.32-24-pve kernel with the latest e1000e driver. I use an embedded industrial board with 6 x gigabit ports. After reading the mentioned post, I started a port logger to catch POD if exists. For the record, here is the eeprom: ethtool -e eth1 Offset Values ------ ------ 0x0000: 00 03 1d 0b 8a e3 30 0b 46 f7 11 30 ff ff ff ff 0x0010: ff ff ff ff 6b 02 00 00 86 80 d3 10 86 80 df 80 0x0020: 00 00 00 20 14 7e 00 00 00 00 d8 00 00 00 00 27 0x0030: c9 6c 50 31 2e 07 0b 04 84 09 00 00 00 c0 06 07 0x0040: 08 10 00 00 04 0f ff 7f 01 4d ff ff ff ff ff ff 0x0050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0060: 00 01 00 40 1c 12 07 40 ff ff ff ff ff ff ff ff 0x0070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 86 42 So, if the situation will happen again, we will know: - the latest kernel with e1000e does not solve the issue - probably we will have log about the data transferred last time, maybe POD Anyway, I will contact the factory too about this issue and ask their help. Bye, István _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
