Yes, the PF works fine for both ping and iperf.
Regards,
William
On Wed, Aug 7, 2013 at 5:38 PM, Ronciak, John <[email protected]>wrote:
> Is the PF interface up and working before you bring up the VF?****
>
> ** **
>
> Cheers,****
>
> John****
>
> ** **
>
> *From:* William Tu [mailto:[email protected]]
> *Sent:* Wednesday, August 07, 2013 2:30 PM
>
> *To:* Ronciak, John
> *Cc:* [email protected]
> *Subject:* Re: [E1000-devel] PF still in reset state and vpd r/w failed***
> *
>
> ** **
>
> Hi John,
>
> I tested on Linux kernel 3.10.0. The VF still fails, the message is a
> little bit different. It shows "PF still in reset state. Is the PF
> interface up?" For 3.10.0, the PF driver version is 3.13.10-k, while the
> 3.6-rc4 is 3.9.15. The VF driver for 3.10 is 2.7.12-k. A full message from
> 3.10.0 kernel is below:
>
> ---
> [ 71.005225] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version 3.13.10-k
> [ 71.005230] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
> [ 71.130003] ixgbe 0000:01:00.0: Enabling SR-IOV VFs using the module
> parameter is deprecated - please use the pci sysfs interface.
> [ 71.230707] pci 0000:02:10.0: [8086:10ed] type 00 class 0x020000
> [ 71.230879] pci 0000:02:10.2: [8086:10ed] type 00 class 0x020000
> [ 71.231019] pci 0000:02:10.4: [8086:10ed] type 00 class 0x020000
> [ 71.231153] pci 0000:02:10.6: [8086:10ed] type 00 class 0x020000
> [ 71.231291] ixgbe 0000:01:00.0 (unregistered net_device): SR-IOV
> enabled with 4 VFs
> [ 71.255259] ixgbe 0000:01:00.0: irq 48 for MSI/MSI-X
> [ 71.255268] ixgbe 0000:01:00.0: irq 49 for MSI/MSI-X
> [ 71.255286] ixgbe 0000:01:00.0: Multiqueue Disabled: Rx Queue count =
> 1, Tx Queue count = 1
> [ 71.255413] ixgbe 0000:01:00.0: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:05:b2:d8
> [ 71.255739] ixgbe 0000:01:00.0: MAC: 2, PHY: 15, SFP+: 5, PBA No:
> G18786-003
> [ 71.257160] ixgbe 0000:01:00.0 eth0: IOV is enabled with 4 VFs
> [ 71.257192] ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
> [ 72.330838] ixgbe 0000:01:00.1: Enabling SR-IOV VFs using the module
> parameter is deprecated - please use the pci sysfs interface.
> [ 72.431496] pci 0000:02:10.1: [8086:10ed] type 00 class 0x020000
> [ 72.431693] pci 0000:02:10.3: [8086:10ed] type 00 class 0x020000
> [ 72.431832] pci 0000:02:10.5: [8086:10ed] type 00 class 0x020000
> [ 72.431986] pci 0000:02:10.7: [8086:10ed] type 00 class 0x020000
> [ 72.432146] ixgbe 0000:01:00.1 (unregistered net_device): SR-IOV
> enabled with 4 VFs
> [ 72.456015] ixgbe 0000:01:00.1: irq 50 for MSI/MSI-X
> [ 72.456022] ixgbe 0000:01:00.1: irq 51 for MSI/MSI-X
> [ 72.456038] ixgbe 0000:01:00.1: Multiqueue Disabled: Rx Queue count =
> 1, Tx Queue count = 1
> [ 72.456165] ixgbe 0000:01:00.1: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:05:b2:d9
> [ 72.456511] ixgbe 0000:01:00.1: MAC: 2, PHY: 1, PBA No: G18786-003
> [ 72.458177] ixgbe 0000:01:00.1 eth1: IOV is enabled with 4 VFs
> [ 72.458210] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection
> [ 102.343970] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function
> Network Driver - version 2.7.12-k
> [ 102.343974] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
> [ 102.343997] ixgbevf 0000:02:10.0: enabling device (0000 -> 0002)
> [ 102.345187] ixgbevf 0000:02:10.0: PF still in reset state. Is the PF
> interface up?
> [ 102.345190] ixgbevf 0000:02:10.0: Assigning random MAC address
> [ 102.345222] ixgbevf 0000:02:10.0: irq 52 for MSI/MSI-X
> [ 102.345228] ixgbevf 0000:02:10.0: irq 53 for MSI/MSI-X
> [ 102.345452] ixgbevf 0000:02:10.2: enabling device (0000 -> 0002)
> [ 102.346602] ixgbevf 0000:02:10.2: PF still in reset state. Is the PF
> interface up?
> [ 102.346605] ixgbevf 0000:02:10.2: Assigning random MAC address
> [ 102.346639] ixgbevf 0000:02:10.2: irq 54 for MSI/MSI-X
> [ 102.346645] ixgbevf 0000:02:10.2: irq 55 for MSI/MSI-X
> [ 102.346832] ixgbevf 0000:02:10.4: enabling device (0000 -> 0002)
> [ 102.347978] ixgbevf 0000:02:10.4: PF still in reset state. Is the PF
> interface up?
> [ 102.347981] ixgbevf 0000:02:10.4: Assigning random MAC address
> [ 102.348016] ixgbevf 0000:02:10.4: irq 56 for MSI/MSI-X
> [ 102.348022] ixgbevf 0000:02:10.4: irq 57 for MSI/MSI-X
> [ 102.348216] ixgbevf 0000:02:10.6: enabling device (0000 -> 0002)
> [ 102.349361] ixgbevf 0000:02:10.6: PF still in reset state. Is the PF
> interface up?
> [ 102.349363] ixgbevf 0000:02:10.6: Assigning random MAC address
> [ 102.349419] ixgbevf 0000:02:10.6: irq 58 for MSI/MSI-X
> [ 102.349426] ixgbevf 0000:02:10.6: irq 59 for MSI/MSI-X
> [ 102.349681] ixgbevf 0000:02:10.1: enabling device (0000 -> 0002)
> [ 102.350845] ixgbevf 0000:02:10.1: PF still in reset state. Is the PF
> interface up?
> [ 102.350849] ixgbevf 0000:02:10.1: Assigning random MAC address
> [ 102.350881] ixgbevf 0000:02:10.1: irq 60 for MSI/MSI-X
> [ 102.350887] ixgbevf 0000:02:10.1: irq 61 for MSI/MSI-X
> [ 102.351123] ixgbevf 0000:02:10.3: enabling device (0000 -> 0002)
> [ 102.352277] ixgbevf 0000:02:10.3: PF still in reset state. Is the PF
> interface up?
> [ 102.352280] ixgbevf 0000:02:10.3: Assigning random MAC address
> [ 102.352312] ixgbevf 0000:02:10.3: irq 62 for MSI/MSI-X
> [ 102.352318] ixgbevf 0000:02:10.3: irq 63 for MSI/MSI-X
> [ 102.352573] ixgbevf 0000:02:10.5: enabling device (0000 -> 0002)
> [ 102.353727] ixgbevf 0000:02:10.5: PF still in reset state. Is the PF
> interface up?
> [ 102.353730] ixgbevf 0000:02:10.5: Assigning random MAC address
> [ 102.353761] ixgbevf 0000:02:10.5: irq 64 for MSI/MSI-X
> [ 102.353768] ixgbevf 0000:02:10.5: irq 65 for MSI/MSI-X
> [ 102.354152] ixgbevf 0000:02:10.7: enabling device (0000 -> 0002)
> [ 102.355309] ixgbevf 0000:02:10.7: PF still in reset state. Is the PF
> interface up?
> [ 102.355312] ixgbevf 0000:02:10.7: Assigning random MAC address
> [ 102.355361] ixgbevf 0000:02:10.7: irq 66 for MSI/MSI-X
> [ 102.355368] ixgbevf 0000:02:10.7: irq 67 for MSI/MSI-X
> [ 102.434952] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> firmware bug on this device. Contact the card vendor for a firmware update.
> [ 102.487904] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> firmware bug on this device. Contact the card vendor for a firmware update.
> [ 102.540861] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> firmware bug on this device. Contact the card vendor for a firmware update.
> [ 102.593801] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> firmware bug on this device. Contact the card vendor for a firmware update.
> [ 102.646741] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> firmware bug on this device. Contact the card vendor for a firmware update.
>
>
> ****
>
> ** **
>
> ** **
>
> On Wed, Aug 7, 2013 at 5:07 PM, Ronciak, John <[email protected]>
> wrote:****
>
> Try a stable kernel and not an RC. Also something newer, like 3.10 or
> Fedora 19.****
>
> ****
>
> Cheers,****
>
> John****
>
> ****
>
> *From:* William Tu [mailto:[email protected]]
> *Sent:* Wednesday, August 07, 2013 2:06 PM****
>
>
> *To:* Ronciak, John
> *Cc:* [email protected]
> *Subject:* Re: [E1000-devel] PF still in reset state and vpd r/w failed***
> *
>
> ****
>
> Hi John,****
>
> You are right. ifconfig -a shows the two ixgbe interaces (dual port). I
> test the PF using ping / iperf and it works fine. However, when I load the
> VF, it still shows that "PF still in reset state, assigning new address"
> and vpd r/w failed. Thanks.****
>
> Regards,****
>
> William****
>
> ****
>
> ****
>
> On Wed, Aug 7, 2013 at 4:56 PM, Ronciak, John <[email protected]>
> wrote:****
>
> That’s a different statement. The driver has clearly loaded. What does
> ‘ifconfig –a’ show you? I’m guessing that you’ll see the interface, it
> just has not be brought up. Please check this.****
>
> ****
>
> Cheers,****
>
> John****
>
> ****
>
> *From:* William Tu [mailto:[email protected]]
> *Sent:* Wednesday, August 07, 2013 1:39 PM
> *To:* Ronciak, John
> *Cc:* [email protected]
> *Subject:* Re: [E1000-devel] PF still in reset state and vpd r/w failed***
> *
>
> ****
>
> Hi John,
>
> No... after loading the ixgbe with no VF, I did not see any interface
> brought up by ixgbe. However, the message did not should any error. Thanks
> for your help.
>
> William****
>
> --- full message of loading PF only ---****
>
> [ 1625.214033] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version 3.9.15-k
> [ 1625.214035] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
> [ 1625.362704] ixgbe 0000:01:00.0: irq 48 for MSI/MSI-X
> [ 1625.362714] ixgbe 0000:01:00.0: irq 49 for MSI/MSI-X
> [ 1625.362720] ixgbe 0000:01:00.0: irq 50 for MSI/MSI-X
> [ 1625.362727] ixgbe 0000:01:00.0: irq 51 for MSI/MSI-X
> [ 1625.362733] ixgbe 0000:01:00.0: irq 52 for MSI/MSI-X
> [ 1625.362740] ixgbe 0000:01:00.0: irq 53 for MSI/MSI-X
> [ 1625.362747] ixgbe 0000:01:00.0: irq 54 for MSI/MSI-X
> [ 1625.362754] ixgbe 0000:01:00.0: irq 55 for MSI/MSI-X
> [ 1625.362761] ixgbe 0000:01:00.0: irq 56 for MSI/MSI-X
> [ 1625.362795] ixgbe 0000:01:00.0: Multiqueue Enabled: Rx Queue count = 8,
> Tx Queue count = 8
> [ 1625.363045] ixgbe 0000:01:00.0: registered PHC device on 0000:01:00.0
> [ 1625.363132] ixgbe 0000:01:00.0: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:05:b2:d8
> [ 1625.363472] ixgbe 0000:01:00.0: MAC: 2, PHY: 15, SFP+: 5, PBA No:
> G18786-003
> [ 1625.419323] ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network Connection
> [ 1626.516510] ixgbe 0000:01:00.1: irq 57 for MSI/MSI-X
> [ 1626.516519] ixgbe 0000:01:00.1: irq 58 for MSI/MSI-X
> [ 1626.516526] ixgbe 0000:01:00.1: irq 59 for MSI/MSI-X
> [ 1626.516533] ixgbe 0000:01:00.1: irq 60 for MSI/MSI-X
> [ 1626.516540] ixgbe 0000:01:00.1: irq 61 for MSI/MSI-X
> [ 1626.516546] ixgbe 0000:01:00.1: irq 62 for MSI/MSI-X
> [ 1626.516553] ixgbe 0000:01:00.1: irq 63 for MSI/MSI-X
> [ 1626.516560] ixgbe 0000:01:00.1: irq 64 for MSI/MSI-X
> [ 1626.516567] ixgbe 0000:01:00.1: irq 65 for MSI/MSI-X
> [ 1626.516605] ixgbe 0000:01:00.1: Multiqueue Enabled: Rx Queue count = 8,
> Tx Queue count = 8
> [ 1626.516852] ixgbe 0000:01:00.1: registered PHC device on 0000:01:00.1
> [ 1626.516938] ixgbe 0000:01:00.1: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:05:b2:d9
> [ 1626.517284] ixgbe 0000:01:00.1: MAC: 2, PHY: 1, PBA No: G18786-003
> [ 1626.572170] ixgbe 0000:01:00.1: Intel(R) 10 Gigabit Network Connection*
> ***
>
> ****
>
> On Wed, Aug 7, 2013 at 4:35 PM, Ronciak, John <[email protected]>
> wrote:****
>
> Does the ixgbe driver work with any virtualization? Like bare metal 10
> gig interface in the host system?
>
> Cheers,
> John****
>
>
>
> > -----Original Message-----
> > From: William Tu [mailto:[email protected]]
> > Sent: Wednesday, August 07, 2013 1:17 PM
> > To: [email protected]
> > Subject: [E1000-devel] PF still in reset state and vpd r/w failed
> >
> > Hi,
> >
> > Today after a few tests and reboot, I load my ixgbe and ixgbevf driver
> > under Linux kernel 3.6-rc4 (Fedora 15). Suddenly I'm not able to load
> > the VF driver and I could find the reason. When I load the VF driver,
> > the message says:
> >
> > 1. ixgbevf: PF still in reset state, assigning new addres 2. ixgbe
> > 0000:01:00.1: vpd r/w failed. This is likely a firmware bug on this
> > device. Contact the card vendor for a firmware update.
> >
> > I tried many times with different kernels but still the same. Does this
> > mean a firmware bug and I have to contact the vendor? Thanks!
> >
> > Regards,
> > William
> >
> >
> > ---- The full message is below ----
> > [ 207.187070] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> > version 3.9.15-k [ 207.187075] ixgbe: Copyright (c) 1999-2012 Intel
> > Corporation.
> > [ 207.412642] pci_bus 0000:02: busn_res: [bus 02] is inserted under
> > [bus 01-02] [ 207.412696] pci 0000:02:10.0: [8086:10ed] type 00 class
> > 0x020000 [ 207.412894] pci 0000:02:10.2: [8086:10ed] type 00 class
> > 0x020000 [ 207.413113] pci 0000:02:10.4: [8086:10ed] type 00 class
> > 0x020000 [ 207.413289] pci 0000:02:10.6: [8086:10ed] type 00 class
> > 0x020000 [ 207.413444] ixgbe 0000:01:00.0: (unregistered net_device):
> > SR-IOV enabled with 4 VFs [ 207.437309] ixgbe 0000:01:00.0: irq 48 for
> > MSI/MSI-X [ 207.437318] ixgbe 0000:01:00.0: irq 49 for MSI/MSI-X [
> > 207.437336] ixgbe 0000:01:00.0: Multiqueue Disabled: Rx Queue count =
> > 1, Tx Queue count = 1 [ 207.437483] ixgbe 0000:01:00.0: registered PHC
> > device on 0000:01:00.0 [ 207.437568] ixgbe 0000:01:00.0: (PCI
> > Express:5.0GT/s:Width x8)
> > 90:e2:ba:05:b2:d8
> > [ 207.437900] ixgbe 0000:01:00.0: MAC: 2, PHY: 15, SFP+: 5, PBA No:
> > G18786-003
> > [ 207.439624] ixgbe 0000:01:00.0: eth0: IOV is enabled with 4 VFs [
> > 207.439628] ixgbe 0000:01:00.0: eth0: IOV: VF 0 is enabled MAC
> > 42:90:6a:2a:5d:73
> > [ 207.439630] ixgbe 0000:01:00.0: eth0: IOV: VF 1 is enabled MAC
> > 86:83:e1:5e:5b:3b [ 207.439632] ixgbe 0000:01:00.0: eth0: IOV: VF 2 is
> > enabled MAC
> > f2:3a:0e:58:d5:45
> > [ 207.439634] ixgbe 0000:01:00.0: eth0: IOV: VF 3 is enabled MAC
> > aa:bb:5d:bb:73:53
> > [ 207.439656] ixgbe 0000:01:00.0: Intel(R) 10 Gigabit Network
> > Connection [ 208.613442] pci 0000:02:10.1: [8086:10ed] type 00 class
> > 0x020000 [ 208.613644] pci 0000:02:10.3: [8086:10ed] type 00 class
> > 0x020000 [ 208.613802] pci 0000:02:10.5: [8086:10ed] type 00 class
> > 0x020000 [ 208.613945] pci 0000:02:10.7: [8086:10ed] type 00 class
> > 0x020000 [ 208.614087] ixgbe 0000:01:00.1: (unregistered net_device):
> > SR-IOV enabled with 4 VFs [ 208.637836] ixgbe 0000:01:00.1: irq 50 for
> > MSI/MSI-X [ 208.637844] ixgbe 0000:01:00.1: irq 51 for MSI/MSI-X [
> > 208.637861] ixgbe 0000:01:00.1: Multiqueue Disabled: Rx Queue count =
> > 1, Tx Queue count = 1 [ 208.638023] ixgbe 0000:01:00.1: registered PHC
> > device on 0000:01:00.1 [ 208.638108] ixgbe 0000:01:00.1: (PCI
> > Express:5.0GT/s:Width x8)
> > 90:e2:ba:05:b2:d9
> > [ 208.638433] ixgbe 0000:01:00.1: MAC: 2, PHY: 1, PBA No: G18786-003 [
> > 208.640138] ixgbe 0000:01:00.1: eth1: IOV is enabled with 4 VFs [
> > 208.640144] ixgbe 0000:01:00.1: eth1: IOV: VF 0 is enabled MAC
> > 22:b1:63:44:ef:5c [ 208.640149] ixgbe 0000:01:00.1: eth1: IOV: VF 1 is
> > enabled MAC
> > 7e:43:11:07:f0:28
> > [ 208.640153] ixgbe 0000:01:00.1: eth1: IOV: VF 2 is enabled MAC
> > 92:32:09:56:66:9d [ 208.640157] ixgbe 0000:01:00.1: eth1: IOV: VF 3 is
> > enabled MAC 42:5a:36:1f:fb:5c [ 208.640189] ixgbe 0000:01:00.1:
> > Intel(R) 10 Gigabit Network Connection [ 219.361571] ixgbevf: Intel(R)
> > 10 Gigabit PCI Express Virtual Function Network Driver - version 2.6.0-*
> ***
>
> > k [ 219.361575] ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.**
> **
>
> > [ 219.361601] ixgbevf 0000:02:10.0: enabling device (0000 -> 0002) [
> > 219.362804] ixgbevf 0000:02:10.0: PF still in reset state, assigning
> > new address [ 219.362860] ixgbevf 0000:02:10.0: irq 52 for MSI/MSI-X [
> > 219.362868] ixgbevf 0000:02:10.0: irq 53 for MSI/MSI-X [ 219.363091]
> > ixgbevf 0000:02:10.2: enabling device (0000 -> 0002) [ 219.364247]
> > ixgbevf 0000:02:10.2: PF still in reset state, assigning new address [
> > 219.364290] ixgbevf 0000:02:10.2: irq 54 for MSI/MSI-X [ 219.364297]
> > ixgbevf 0000:02:10.2: irq 55 for MSI/MSI-X [ 219.364476] ixgbevf
> > 0000:02:10.4: enabling device (0000 -> 0002) [ 219.365629] ixgbevf
> > 0000:02:10.4: PF still in reset state, assigning new address [
> > 219.365669] ixgbevf 0000:02:10.4: irq 56 for MSI/MSI-X [ 219.365676]
> > ixgbevf 0000:02:10.4: irq 57 for MSI/MSI-X [ 219.365870] ixgbevf
> > 0000:02:10.6: enabling device (0000 -> 0002) [ 219.367018] ixgbevf
> > 0000:02:10.6: PF still in reset state, assigning new address [
> > 219.367070] ixgbevf 0000:02:10.6: irq 58 for MSI/MSI-X [ 219.367078]
> > ixgbevf 0000:02:10.6: irq 59 for MSI/MSI-X [ 219.367207] ixgbevf
> > 0000:02:10.1: enabling device (0000 -> 0002) [ 219.368333] ixgbevf
> > 0000:02:10.1: PF still in reset state, assigning new address [
> > 219.368351] ixgbevf 0000:02:10.1: irq 60 for MSI/MSI-X [ 219.368354]
> > ixgbevf 0000:02:10.1: irq 61 for MSI/MSI-X [ 219.368484] ixgbevf
> > 0000:02:10.3: enabling device (0000 -> 0002) [ 219.369595] ixgbevf
> > 0000:02:10.3: PF still in reset state, assigning new address [
> > 219.369613] ixgbevf 0000:02:10.3: irq 62 for MSI/MSI-X [ 219.369617]
> > ixgbevf 0000:02:10.3: irq 63 for MSI/MSI-X [ 219.369756] ixgbevf
> > 0000:02:10.5: enabling device (0000 -> 0002) [ 219.370894] ixgbevf
> > 0000:02:10.5: PF still in reset state, assigning new address [
> > 219.370919] ixgbevf 0000:02:10.5: irq 64 for MSI/MSI-X [ 219.370924]
> > ixgbevf 0000:02:10.5: irq 65 for MSI/MSI-X [ 219.371260] ixgbevf
> > 0000:02:10.7: enabling device (0000 -> 0002) [ 219.372385] ixgbevf
> > 0000:02:10.7: PF still in reset state, assigning new address [
> > 219.372412] ixgbevf 0000:02:10.7: irq 66 for MSI/MSI-X [ 219.372418]
> > ixgbevf 0000:02:10.7: irq 67 for MSI/MSI-X [ 219.436740] ixgbe
> > 0000:01:00.1: vpd r/w failed. This is likely a firmware bug on this
> > device. Contact the card vendor for a firmware update.
> > [ 219.489687] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> > firmware bug on this device. Contact the card vendor for a firmware
> > update.
> > [ 219.542646] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> > firmware bug on this device. Contact the card vendor for a firmware
> > update.
> > [ 219.595588] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> > firmware bug on this device. Contact the card vendor for a firmware
> > update.
> > [ 219.648533] ixgbe 0000:01:00.1: vpd r/w failed. This is likely a
> > firmware bug on this device. Contact the card vendor for a firmware
> > update.****
>
> ****
>
> ****
>
> ** **
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
