> -----Original Message----- > From: Fujinaka, Todd [mailto:todd.fujin...@intel.com] > Sent: Thursday, April 10, 2014 7:59 AM > To: Borislav Petkov; e1000-devel@lists.sourceforge.net > Cc: net...@vger.kernel.org; lkml > Subject: Re: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error > > We also need to know what part you're using. "lspci | grep Ethernet" should > narrow that down. > > Thanks. > > Todd Fujinaka > Software Application Engineer > Networking Division (ND) > Intel Corporation > todd.fujin...@intel.com > (503) 712-4565 > > -----Original Message----- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Thursday, April 10, 2014 5:00 AM > To: e1000-devel@lists.sourceforge.net > Cc: net...@vger.kernel.org; lkml > Subject: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error > > Hi guys, > > I started getting those sporadic > > [133178.640890] e1000e 0000:00:19.0 eth0: Hardware Error [133179.293148] > e1000e 0000:00:19.0: irq 45 for MSI/MSI-X [133179.394226] e1000e > 0000:00:19.0: irq 45 for MSI/MSI-X [133179.397200] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready [133181.338258] e1000e > 0000:00:19.0 eth0: Hardware Error [133182.077209] > pci_pm_runtime_suspend(): e1000_runtime_suspend+0x0/0x40 [e1000e] > returns -2 > > messages with 3.14 and I haven't had them before. After this, I do > > rmmod e1000e && modprobe e1000e > > and I get: > > [133221.891555] e1000e 0000:00:19.0 eth0: removed PHC [133228.181552] > e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [133228.181562] e1000e: > Copyright(c) 1999 - 2013 Intel Corporation. > [133228.182241] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode [133228.182332] e1000e 0000:00:19.0: irq 45 > for MSI/MSI-X [133229.009837] e1000e: probe of 0000:00:19.0 failed with > error -2 > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > [133307.107217] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k > [133307.107228] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. > [133307.107814] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode [133307.107959] e1000e 0000:00:19.0: irq 45 > for MSI/MSI-X [133307.935921] e1000e: probe of 0000:00:19.0 failed with > error -2 > > ... > > [133841.361905] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k > [133841.361914] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. > [133841.362451] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set > to dynamic conservative mode [133841.362520] e1000e 0000:00:19.0: irq 45 > for MSI/MSI-X [133842.192710] e1000e: probe of 0000:00:19.0 failed with > error -2 > > each time I try and eth0 is dead. Only a reboot helps, I've come to find out > so > far. > > Any ideas? > > -- > Regards/Gruss, > Boris. > > Sent from a fat crate under my desk. Formatting is fine. > -- > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration Continuously > Automate Build, Test & Deployment Start a new project now. Try Jenkins in > the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired
Could you also provide some information about the configuration of the system when this happens? Do you have Runtime Power Management configured in the kernel and enabled? (echo auto > /sys/devices/pci0000\:00/0000\:00\:19.0/power/control) Is the network cable in and link is up? Is anything happening to the link partner (going up and down, connecting and disconnecting)? Thanks, Dave Ertman ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
