Hi,

I'm having serious trouble with Intel PRO/1000 network adapters and the 
e1000e Linux driver. I have tried every possible fix I can figure out 
and now I'm reaching to you for new ideas.

The PC (Lanner LEC-2220P) in question comes with two Intel NICs on 
board. We have installed a third card in a PCIe slot.

$ lspci | grep Ethernet
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network 
Connection

The first one is connected to a 10/100 embedded device, the second one 
to PC with a 1Gb NIC, and the last one to a GigE camera (which produces 
data some 300Mbs at maximum). No switches in between. The problem occurs 
in a similar way in four identical systems. Thus, I believe we can rule 
out hardware failures.

The operating system in question is Debian Squeeze, running Linux kernel 
2.6.32-5-amd64 by default. It comes with an old e1000e driver module 
(1.2.something).

Most of the time, the connections work fine. However, any of the three 
devices may go down after a seemingly random amount of time with no 
clear reason. What I see in system logs is this:

Aug 17 22:08:56 XXX kernel: [22144.179804] e1000e: eth0 NIC Link is Down
Aug 17 22:08:57 XXX kernel: [22145.806317] e1000e: eth0 NIC Link is Up 
100 Mbps Full Duplex, Flow Control: Rx/Tx
Aug 17 22:08:57 XXX kernel: [22145.806321] e1000e 0000:01:00.0: eth0: 
10/100 speed: disabling TSO

Sometimes, it is only one of the devices (in this case eth0), sometimes 
two, sometimes all three. The order in which the links go down follows 
no pattern. After the failure, the link seems to recover, but it makes 
the camera to lose some data, and its connection.

In some (relatively rare) cases, I don't see the "Link is Down" message 
at all. Just "Link is Up".

I updated the e1000e driver to the latest one found on Intel's site 
(2.0.0.1). I used "make CFLAGS_EXTRA=-DDISABLE_PM install" to disable 
power management because this was suggested by some people who had had 
problems with the driver. The new driver loaded fine but didn't solve 
the problem.

To avoid power management issues I have disabled both pcie_aspm and acpi 
at boot.

I tried setting InterruptThrottleRate=3000,3000,3000 to module 
parameters. No luck. Setting the rate to 10000 had no effect either.

Then, I updated the Linux kernel to 3.2.0 and recompiled the driver as 
well. That did have an effect: the problem now occured more frequently, 
so I switched back to the original kernel.

I'm out of ideas. Is there anything else I could try out?

Best regards,
-- 
Topi Mäenpää
Co-founder, Intopii
intopii.com
+358 40 774 7749

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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

Reply via email to