Hi,

I recently build my PC and noticed a very strange problem..While my download speed is fine, my upload speed is almost 0. However using the same Ethernet cable on my laptop, upload speed is fine (~5-6 Mbps). So problem is not with the cable.

Things i tried:

- Reset modem -> do not work

- Update all drivers including the Intel Ethernet connection driver 1219 (version 12.17.10.7) -> do not work

- Ipconfig/release & renew -> do not work

- Disable all windows services and stop running programs -> do not work

- Change the intel ethernet connection driver settings to increase throughput -> do not work

Kindly help me to figure out what is happening? My last resort is to buy a PCI-E Ethernet card but want to try everything before doing that..

PC Specs:

- OS: Windows 10 64 bit Home Edition

- Motherboard: Asus Rog Strix Z370-H Gaming

- CPU: Intel i5 - 6400 8th Gen

- GPU: MSI Geforce 1050Ti (4GB DDR5)

- RAM: Patriot 8GB x 2 DDR4 2400Mhz

Hello,

the Intel X550T2 does not work with Windows 10 1803 17133.1 x64 PRO (RTM).

The NIC gets no connection to the intenet and the local network. I tested this with the driver 23.1.

When will apear new drivers for Windows 10 1803?

Hallo,

die Intel X550T2 funktioniert nicht unter Windows 10 1803 17133.1 x64 Pro, welches als die RTM gilt.

Die Netzwerkkarte kann keine Verbindung zum Internet oder zum lokalen Netz aufbauen. Getestet wurde das mit Treiber in der Version 23.1

Wann sind für Windows 10 1803 neue Treiber erhältlich?

MfG MM69

Hello everyone,

My desktop motherboard uses an Intel l211 network adapter and on Windows Pro 1803 (with the latest 23.2 driver, but also with 23.1) I've noticed that TCP Checksum Offload cannot be enabled at all via Device Manager -> Advanced Adapter Settings or Windows PowerShell.

On Advanced Adapter Settings, the options seem to be set to Disabled by default, but once I set them to something else and apply the settings, the window is closed, connection is lost for a few seconds, and once I open the Settings page once again, the options are back to Disabled.

Then, I tried using Enable-NetAdapterChecksumOffload on Windows Powershell, but when I try reading the new values with Get-NetAdapterChecksumOffload, I see everything set to Disabled.

Any ideas?

Thanks!

I210-IS In both PMON and Linux, the ID is identified as 1538, but the connection cannot be connected if the network cable is plugged in.

hello,

I have a HP ZBook 15 laptop, where the "Intel(R) Ethernet Connection I217-LM" device is used for wired Ethernet. I also have two GO-SW-8G Dlink Gigabit switch (https://eu.dlink.com/se/sv/products/go-sw-8g-8-port-gigabit-dlinkgo-switch ). Below, I will call these SW1 and SW2, for better understanding. Also from the Internet Service Provider, we have 1 Gigabit/sec bandwidth (T-Home Magenta1 pack).

There are two scenarios what I setup and the 1Gbps speed was not able to work (?) in the laptop in one case.

The scenario-1, when the 1G speed was working:

The internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. The Ethernet interface in my laptop is connected to the PORT-2 in SW1 with a standard LAN cable. In this case the Ethernet interface LinkSpeed was Gigabit. It was possible to see both in the indicator LED of the PORT-2 in SW1 -this was green-, and also in the Windows when checking the LinkSpeed of the Ethernet interface, please refer to this link, Google Photos

So, in Gigabit speed point of view there is no any issue in this scenario.

The scenario-2, when the 1G speed was not working, and the LinkSpeed down set to 100Mbps:

Just similar to scenario-1, the internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. Now SW2 comes to the path, thus PORT-2 in SW1 is connected to PORT-1 in SW2 with a standard LAN cable. The Ethernet interface in my laptop is connected to the PORT-2 in SW2 with a standard LAN cable. In this scenario, the indicator LEDs on the Dlink switches are green, meaning 1G speed in all used ports, except the PORT-2 in SW2 which goes to the laptop. The indicator LED was orange of this port, also checking the LinkSpeed in the Windows side, that shows 100Mbps speed, please refer to this link, Google Photos

I have tried set manually the LinkSpeed in the Windows for the Ethernet interface to 1G, but in this case the interface was "disconnected", so the wired Ethernet was gone in the list of  connections in Windows and the laptop has started to use my WIFI NW.

When I changed back the interface LinkSpeed to "Auto", that come back to 100Mbps, and the "internet connection" returned to use the wired connection.

I did other test by using another Gigabit device, what was a Gigabit router from Dlink, and when I was connect one of the LAN interface of the router to the PORT-2 (or 3, or so) in SW2, the indicator LED was green, meaning the speed was 1Gbps.

Last week, I was issued a support ticket to Dlink, but finally they have not seen any issue with my setup in their pint of view, and also got the info from them, the scenario-2 was working very well with 1G in their LAB.

Thus now, I think the problem is not with the Dlink switches, but with the Windows and/or I217-LM device, and I would like to get some instructions, hints, ect from you, about doing some kind of troubleshooting to identify the root of the issue I have.

This morning I just refreshed the driver of the I217-LM to "Intel ® Network Connections Version:"22.9.6.0"", but I got the same result, so the expected 1Gbps LinkSpeed is not seen when both Dlink switches are in the path.

For more detail info about the drivers on my laptop, please refer to the attached text file.

Please try help me.

Thanks for your help,

/Robi

Hi.

So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.

Ou snap

Message was edited by: Tiit Talts

Hello,

I'm having some issues using VLANs on a new system. (See system Specs at Bottom)

Last coupe of days I have tried to update the drivers to make VLANs work on my laptop.

First driver I tried to install went well. I could see The VLAN tab when configuring my network connection.
However when I tried to add a VLAN the laptop gave me a BSOD with BAD_POOL_CALLER as error message.

I tried to reinstall a couple of times, rebooted a few times and it alway repaired itself to the previous Driver installed.
Driver used: Download Intel® Network Adapter Driver for Windows® 10

After some searching on the web I found that  alot of people had an issue like this. There was a problem with the ProSet option during the driver installation and one post suggested another driver provided by Intel that would fix the issue crashing.

Using this driver solved the BSOD issue, but whenever I make a VLAN, it deactivates itself. activating it doesn't work, it just stays deactivated.
Driver used: https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=...

After some searching on the web I found this article from 2016 saying that VLAN or teaming or not supported by windows 10 with the ProSet driver.

Because it was an old article I searched for a more  recent one and found this.

So I tried to install every driver beginning from the newest one and ending on 22.3 as the article says following:

Every driver has these same issues.

Driver page: Download Intel® Network Adapter Driver for Windows® 10

Anyone here who had/has similar issues?

Are there any known solutions for these issues?

Best regards,

Bert
----------------------------------------------------System Specifications

Manufacturer:Lenovo

Model: X1 Carbon

OS: Windows 10 Pro 64 Bit

Processor: Intel(R)  Core(TM) i7-7500U CPU @2.70GHz 2.90GHz

RAM: 16GB

Ethernet adapter: Intel(R) Ethernet Connection (4) I219-V

----------------------------------------------------

This issue was covered here but was NOT resolved and mark answered by accident.

VLANs disabled in Windows 10 Build 17133.1 Version 1803

My steps were as follows

1. Ran fine with Windows 10 Ver. 1709 for months using multiple tagged VLANs and one untagged VLAN on Intel NUC NUC6i7KYK (aka Skull Canyon) and Intel i219-LM NIC.
2. Clean installed Windows 10 Build 17133.1 Version 1803 with latest Drivers from Intel.
3. Recreated all my tagged VLANs only to find they were all DISABLED.
4. Permanently removed Intel NIC 23.1 driver and installed previous Intel NIC 22.9 driver with no luck still.
5. Clean installed Windows 10 Ver. 1709 with Intel NIC 23.1 driver.
6. Recreated all my tagged VLANs and BAM they all worked like normal.

In conclusion, the latest Intel NIC driver 23.1 seems fine but there is something wrong with Windows 10 Build 17133.1 Version 1803 Springs Creators Update, aka Redstone 4.

Hi,

    I am using network performance measurement tool nuttcp with IGB and E1000 cards on one of my development boards.

Issue: Observed crash/watchdog bite using testing with both IGB and E1000 cards.

Kernel: kernel_msm-3.18

Steps to reproduce.

1.) On device:  ./nuttcp-8.1.4.arm -S

2.) On PC side run below command xxx.xx.xxx.xxx -> IP address of device.

./nuttcp-8.1.4.x86 -w2m -u -R 160M -i 1 -T 1m xxx.xx.xxx.xxx

3) After a couple of iterations we see the crash reported in the log.

IGB  Log

------------------

Parsing debug information for MSM_DUMP_DATA_CPU_CTX. Version: 20 Magic: 42445953 Source:

Parsing CPU1 context start 171c8a800 end 171c8b000

Core 1 PC: arch_counter_get_cntvct+1c <ffffffc000a25164>

Core 1 LR: arch_counter_get_cntvct+1c <ffffffc000a25164>

[<ffffffc000a25164>] arch_counter_get_cntvct+0x1c

[<ffffffc000352ca0>] __delay+0x24

[<ffffffc000352c74>] __const_udelay+0x24

[<ffffffc00049235c>] msm_trigger_wdog_bite+0xd0

[<ffffffc0000f1d0c>] spin_bug+0x94

[<ffffffc0000f1e7c>] do_raw_spin_lock+0x104

[<ffffffc000eb38a0>] _raw_spin_lock+0x28

[<ffffffc000710768>] igb_get_stats64+0x30

[<ffffffc000cb8244>] dev_get_stats+0x4c

[<ffffffc000d249f8>] iface_stat_fmt_proc_show+0x98

[<ffffffc0001e77e0>] seq_read+0x18c

[<ffffffc000222874>] proc_reg_read+0x8c

[<ffffffc0001c5fcc>] vfs_read+0xa0

[<ffffffc0001c6758>] SyS_read+0x58

[<ffffffc0000864b0>] el0_svc_naked+0x24

From the code, it looks like it could be stuck in igb_update_stats and so the unlock might not be happening in time.

Code file:/kernel_msm-3.18/kernel/drivers/net/ethernet/intel/igb/igb_main.c

5160static struct rtnl_link_stats64 *igb_get_stats64(struct net_device *netdev,

5161 struct rtnl_link_stats64 *stats)

5162{

5163 struct igb_adapter *adapter = netdev_priv(netdev);

5164

5165 spin_lock(&adapter->stats64_lock);

5166 igb_update_stats(adapter, &adapter->stats64);

5167 memcpy(stats, &adapter->stats64, sizeof(*stats));

5168 spin_unlock(&adapter->stats64_lock);

5169

5170 return stats;

E1000 Log

-------------

[  100.703446] init: Service 'atfwd' (pid 765) exited with status 255

[  100.708673] init: Service 'atfwd' (pid 765) killing any children in process group

[  104.343224] init: Untracked pid 2636 exited with status 0

[  133.202677] BUG: spinlock lockup suspected on CPU#0, kworker/0:3/986

[  133.208030]  lock: iface_stat_list_lock+0x0/0x18, .magic: dead4ead, .owner: NetworkStats/1294, .owner_cpu: 1

[  133.217936] Causing a watchdog bite!

[  133.345512] Backtrace for cpu 1 (current):

[  133.348758] CPU: 1 PID: 1294 Comm: NetworkStats Tainted: G        W      3.18.31-g12d3836-dirty #2

[  133.357697] Hardware name: Qualcomm Technologies, Inc. APQ8096v3 + PMI8994 DragonBoard (DT)

[  133.366028] Call trace:

[  133.368473] [<ffffffc000089d9c>] dump_backtrace+0x0/0x278

[  133.373843] [<ffffffc00008a034>] show_stack+0x20/0x28

[  133.378884] [<ffffffc000e70b08>] dump_stack+0x9c/0xd4

[  133.383914] [<ffffffc000093700>] arch_trigger_all_cpu_backtrace+0x6c/0xdc

[  133.390687] [<ffffffc0000f1e80>] do_raw_spin_lock+0x108/0x160

[  133.396415] [<ffffffc000e7f428>] _raw_spin_lock+0x28/0x34

[  133.401800] [<ffffffc0006d2de0>] e1000e_get_stats64+0x44/0x118

[  133.407614] [<ffffffc000c83140>] dev_get_stats+0x4c/0xac

[  133.412907] [<ffffffc000cef8f4>] iface_stat_fmt_proc_show+0x98/0x198

[  133.419243] [<ffffffc0001e77e0>] seq_read+0x18c/0x3b4

[  133.424277] [<ffffffc000222874>] proc_reg_read+0x8c/0xb4

[  133.429571] [<ffffffc0001c5fcc>] vfs_read+0xa0/0x14c

[  133.434520] [<ffffffc0001c6758>] SyS_read+0x58/0x94

cheers,

mohit

Hello everyone,

My desktop motherboard uses an Intel l211 network adapter and on Windows Pro 1803 (with the latest 23.2 driver, but also with 23.1) I've noticed that TCP Checksum Offload cannot be enabled at all via Device Manager -> Advanced Adapter Settings or Windows PowerShell.

On Advanced Adapter Settings, the options seem to be set to Disabled by default, but once I set them to something else and apply the settings, the window is closed, connection is lost for a few seconds, and once I open the Settings page once again, the options are back to Disabled.

Then, I tried using Enable-NetAdapterChecksumOffload on Windows Powershell, but when I try reading the new values with Get-NetAdapterChecksumOffload, I see everything set to Disabled.

Any ideas?

Thanks!

Is possible that after 2 weeks intel ANS driver is still broken in win 1803? How many time i need to wait for this?

I can create the network LAG in LACP mode but i cant enable the interface. Is there any solution?

Hello,

the Intel X550T2 does not work with Windows 10 1803 17133.1 x64 PRO (RTM).

The NIC gets no connection to the intenet and the local network. I tested this with the driver 23.1.

When will apear new drivers for Windows 10 1803?

Hallo,

die Intel X550T2 funktioniert nicht unter Windows 10 1803 17133.1 x64 Pro, welches als die RTM gilt.

Die Netzwerkkarte kann keine Verbindung zum Internet oder zum lokalen Netz aufbauen. Getestet wurde das mit Treiber in der Version 23.1

Wann sind für Windows 10 1803 neue Treiber erhältlich?

MfG MM69

Hi, we have been redirected here from this thread in the embedded community: ARM tools for 82574 |Embedded Community

To summarize the important parts of our previous discussion, we have an Intel EXPI9301CT Gigabit CT PCI-e Desktop Adapter, which has an 82574 controller and a Winbond W25X40BVNIG flash. We are trying to use the eepromARMtool to reprogram the MAC address in the flash.

Running ./eepromARMtool -dump -NIC=1 gives us a file whose first line is:

8888 8888 8887 0C20 F746 2014 FFFF FFFF

We want to change the MAC address, so we edit the file that was dumped and change the first line to:

70B3 D501 C307 0C20 F746 2014 FFFF FFFF

Then we run ./eepromARMtool -write -NIC=1 -f=new_mac.otp. If we run the dump command again, the flash appears to have the correct contents. However, if we reboot or power cycle the machine and dump again, the output has returned to its original contents. This seems to imply that our changes were not actually flushed to the flash.

Do you have any advice for how to fix this problem? Thank you!

Hi,

I recently build my PC and noticed a very strange problem..While my download speed is fine, my upload speed is almost 0. However using the same Ethernet cable on my laptop, upload speed is fine (~5-6 Mbps). So problem is not with the cable.

Things i tried:

- Reset modem -> do not work

- Update all drivers including the Intel Ethernet connection driver 1219 (version 12.17.10.7) -> do not work

- Ipconfig/release & renew -> do not work

- Disable all windows services and stop running programs -> do not work

- Change the intel ethernet connection driver settings to increase throughput -> do not work

Kindly help me to figure out what is happening? My last resort is to buy a PCI-E Ethernet card but want to try everything before doing that..

PC Specs:

- OS: Windows 10 64 bit Home Edition

- Motherboard: Asus Rog Strix Z370-H Gaming

- CPU: Intel i5 - 6400 8th Gen

- GPU: MSI Geforce 1050Ti (4GB DDR5)

- RAM: Patriot 8GB x 2 DDR4 2400Mhz

Iam so dissappointed i left the stability of qualcomm network driver.

I have been running a KF2 Killing

floor 2 server for years.

Just recently i retired the gigabyte board and went with asus and the intel network drivers i have heard so much about!

Its been 4 mnths of torture trying to sort my high lag spike problem!!

Ping Spikes into the thousands every 5th or so refresh of server in game browser!!!

Yet when i start server on my old giga board the ping is steady!!

I want to break bones !!

How on earth do you release faulty drivers!!!

I finally thought i better atleast try ask and look for solutions in here , god knows ive looked everywhere!!!

NOT HAPPY.. intel LOLOL

i had better add... z370 asus rog strix i gaming crap, latest drivers and all dated drivers all bios now the latest .. attachment shows my 2 servers , ping spikes when running one server also.

Hey!

So I bought two of these NICs and a Dell PowerConnect 2816 to connect two computers with up to a 4Gigabit connection when teamed. The issue is, I can't seem to get the drivers to install properly in windows. ProSet seems to instal for my motherboard built in NIC, which is also INTEL Gigabit-but I dont wan't to team that-I just want a team of the 4 ports on the add in card. According to every single thing I have seen on google, there should be a teaming tab when I click "configure" on one of the Pro 1000PT connections, but it doesn't seem to exist anywhere, and Windows installs the drivers for the device automatically. I have tried installing the latest drivers, but again, it just shows the default Windows drivers installed. Help!

Thanks so much,

Rowan

I also have teaming problem with I350-T2 + I219V

I use win10 64-bit with build 14393.2214 (released at 17th, April) and the latest driver (Download Intel® Network Adapter Driver for Windows® 10 )

I can successfully teaming these two adapters(using intel ANS adaptive load balancing), and it works fine in normal situation.

BUT, its fail-over function doesn't work at all.

Here is how I test fail-over function:

I connect with 3 client pc and use Iperf2.0.10 to test the connection speed.

Then, I intentionally disable one adapter, theoretically, it will continue connecting with all 3 pc with a lower speed(which I saw under win8), but the result I see is connection abort (sometimes one or two of them, sometimes all) with two kinds of error message : "write failed, connection reset by peer" or "software cause connection abort".

This problem didn't happen under win8 I test couple weeks ago.

Does anyone have any idea?

Hello,

I'm having some issues using VLANs on a new system. (See system Specs at Bottom)

Last coupe of days I have tried to update the drivers to make VLANs work on my laptop.

First driver I tried to install went well. I could see The VLAN tab when configuring my network connection.
However when I tried to add a VLAN the laptop gave me a BSOD with BAD_POOL_CALLER as error message.

I tried to reinstall a couple of times, rebooted a few times and it alway repaired itself to the previous Driver installed.
Driver used: Download Intel® Network Adapter Driver for Windows® 10

After some searching on the web I found that  alot of people had an issue like this. There was a problem with the ProSet option during the driver installation and one post suggested another driver provided by Intel that would fix the issue crashing.

Using this driver solved the BSOD issue, but whenever I make a VLAN, it deactivates itself. activating it doesn't work, it just stays deactivated.
Driver used: https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=...

After some searching on the web I found this article from 2016 saying that VLAN or teaming or not supported by windows 10 with the ProSet driver.

Because it was an old article I searched for a more  recent one and found this.

So I tried to install every driver beginning from the newest one and ending on 22.3 as the article says following:

Every driver has these same issues.

Driver page: Download Intel® Network Adapter Driver for Windows® 10

Anyone here who had/has similar issues?

Are there any known solutions for these issues?

Best regards,

Bert
----------------------------------------------------System Specifications

Manufacturer:Lenovo

Model: X1 Carbon

OS: Windows 10 Pro 64 Bit

Processor: Intel(R)  Core(TM) i7-7500U CPU @2.70GHz 2.90GHz

RAM: 16GB

Ethernet adapter: Intel(R) Ethernet Connection (4) I219-V

----------------------------------------------------

I was looking through the i40evf source code, and it seems like the maximum number of queues supported is 4. Is there a reasoning for this? Is there a way to use more, such as 16?

I've seen patches proposing removing a few variables (MAX_QUEUES, which sets the max to 16, but doesn't actually serve a purpose since the RX queues limit is set to 4).

Hi,

We are trying to integrate the I350-F2 Ethernet card to our products, and we are facing to this problem: The I350-F2 is detected but the 2 Ethernet Ports are not recognised. It seems that there is a conflict between the 2 Ethernet ports of the motherboard and the 2 Ethernet port of the I350-F2.

Here is the output  ifconfig:

__tmp370698911 Link encap:Ethernet  HWaddr A0:36:9F:67:D3:C9

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

__tmp1412522235 Link encap:Ethernet  HWaddr A0:36:9F:67:D3:C8

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:1535 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1535 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1856694 (1.7 MiB)  TX bytes:1856694 (1.7 MiB)

eth0      Link encap:Ethernet  HWaddr 0C:C4:7A:72:2E:9A

          inet addr:192.168.3.200  Bcast:192.168.31.255  Mask:255.255.224.0

          inet6 addr: fe80::ec4:7aff:fe72:2e9a/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:106167 errors:0 dropped:0 overruns:0 frame:0

          TX packets:903 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:8426155 (8.0 MiB)  TX bytes:81922 (80.0 KiB)

eth1      Link encap:Ethernet  HWaddr 0C:C4:7A:72:2E:9B

          inet addr:192.168.3.195  Bcast:192.168.31.255  Mask:255.255.224.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Here is the dmesg log:

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.0: eth0: MAC: a0:36:9f:67:d3:c8

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: eth0: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: PCI INT B -> GSI 36 (level, low) -> IRQ 36

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: (PCIe:5.0GT/s:Width x4) <6>igb 0000:02:00.1: eth1: MAC: a0:36:9f:67:d3:c9

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: eth1: PBA No: G15813-004

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:02:00.1: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:07:00.0: eth2: MAC: 0c:c4:7a:72:2e:9a

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: eth2: PBA No: 013A00-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:07:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Intel(R) Gigabit Ethernet Network Connection

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: (PCIe:2.5GT/s:Width x1) <6>igb 0000:08:00.0: eth2: MAC: 0c:c4:7a:72:2e:9b

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: eth2: PBA No: 011000-000

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: LRO is disabled

May 28 14:42:02 RTServer_3_200 kernel: igb 0000:08:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)

Kernel: 2.6.29.6

igb driver : 5.0.6

Is there a solution for this issue ?

If you need more info, don't hesitate to ask me.

Thank in advance.