Challa [mailto:hcha...@cct.co.uk]
Sent: Monday, April 13, 2015 10:05 AM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] ARM support for igb driver
Hi Todd,
Yes, I will contact the hardware designer, mean while I was going through the
platform errata sheet
ff ff ff ff
Thanks
Hari
shiv prakash Agarwal chhotu.shiv at gmail.com writes:
Thanks,
Yes it is a NIC. How to get dump of its EEPROM?
On Mon, Jun 2, 2014 at 9:35 PM, Fujinaka, Todd todd.fujinaka at
intel.com wrote:
There is no hardware bug. The PCIe spec allows VDMs. Note
to contact them.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Hari Challa [mailto:hcha...@cct.co.uk]
Sent: Monday, April 13, 2015 8:22 AM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
[mailto:dhd...@apm.com]
Sent: Thursday, April 09, 2015 11:58 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [linux-nics] Arm64 kernel crashes with e1000e driver
Hi Fujinaka,
As e1000e product family is nearly end of life. Does Intel have alternative
options for 1Gb NIC
Unfortunately I think the only suggestion I have is to stick to stable kernels.
We don't have any ARM hardware available so we can't test this locally.
I'm also deleting the laundry-list of cc's because I think I'm the only one on
82574L support on Linux at this time.
Todd Fujinaka
Software
* and try again a number of times.
**/
Regards,
Duc Dang.
On Mon, Apr 6, 2015 at 12:42 PM, Fujinaka, Todd todd.fujin...@intel.com wrote:
Unfortunately I think the only suggestion I have is to stick to stable
kernels. We don't have any ARM hardware available so we can't test this
locally
I have a fix for this already, if Dan doesn't mind.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Wyborny, Carolyn
Sent: Tuesday, March 31, 2015 11:07 AM
To: Fujinaka, Todd; Kirsher
...@intel.com
(503) 712-4565
-Original Message-
From: jacob jacob [mailto:opstk...@gmail.com]
Sent: Friday, March 20, 2015 1:16 PM
To: Fujinaka, Todd
Cc: Nelson, Shannon; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Fwd: PCI passthrough of 40G ethernet interface
(Openstack
[mailto:opstk...@gmail.com]
Sent: Thursday, March 19, 2015 3:24 PM
To: Fujinaka, Todd
Cc: Nelson, Shannon; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Fwd: PCI passthrough of 40G ethernet interface
(Openstack/KVM)
How is this different for devices passed through to VM
To: Fujinaka, Todd
Cc: Nelson, Shannon; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Fwd: PCI passthrough of 40G ethernet interface
(Openstack/KVM)
I have updated to latest firmware and still no luck.
]# ethtool -i eth1
driver: i40e
version: 1.2.37
firmware-version: f4.33.31377 a1.2
I'm looking into this and while the code fix is correct, I'm not sure the
underlying code is correct.
Unfortunately, the person who knows the most about this is out for spring
break. Can we hold off on this patch?
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel
: Roman Bogorodskiy [mailto:bogorods...@gmail.com]
Sent: Wednesday, March 18, 2015 11:18 PM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Controlling MAC address filtering on the host side
Fujinaka, Todd wrote:
From my understanding the mac address assigned
]
Sent: Wednesday, March 18, 2015 3:45 PM
To: Fujinaka, Todd
Cc: Nelson, Shannon; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Fwd: PCI passthrough of 40G ethernet interface
(Openstack/KVM)
As mentioned int he previous email have already tried the latest available
drivers:
Have tried
At the very least you should definitely be using a newer driver and firmware.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: jacob jacob [mailto:opstk...@gmail.com]
Sent: Wednesday,
-
From: Fujinaka, Todd
Sent: Wednesday, March 18, 2015 3:47 PM
To: 'jacob jacob'
Cc: Nelson, Shannon; e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] Fwd: PCI passthrough of 40G ethernet interface
(Openstack/KVM)
You've purposely ignored both Shannon and my recommendations that you
...@intel.com
(503) 712-4565
-Original Message-
From: Roman Bogorodskiy [mailto:bogorods...@gmail.com]
Sent: Wednesday, March 18, 2015 9:13 PM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Controlling MAC address filtering on the host side
Fujinaka, Todd wrote
We don't allow more than one MAC address for a VF.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Roman Bogorodskiy [mailto:bogorods...@gmail.com]
Sent: Wednesday, March 18, 2015 6:11
These cards don't have firmware. They're just configuration settings. You can
download the OpenSDM on the files section to decode the differences, but mostly
it's identification information.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
The most likely answer is because you're using a development kernel. Can you
try the latest stable kernel?
The only recent change to e1000 should only be hit if you're changing the MTU.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
I think this may be fixed with a newer NVM image. In any case, the newer NVM
images will help with other issues including performance. Go to
downloadcenter.intel.com and search for xl710 and you should find an updater
and instructions.
Todd Fujinaka
Software Application Engineer
Networking
There are multiple errors in the system log that are usually related to a
mismatch in the DCB version of the switch and host.
Syslog reports the following:
Feb 18 15:03:54 h6 fcoemon: fcm_process_ieee_msg: Unexpected command type 9 Feb
18 15:03:54 h6 fcoemon: fcm_process_ieee_msg:
We have a fix for this in our local tree. On inspection, this looks like it
only fixes things for Ubuntu 14.04 but not for anything else.
We're not supporting Ubuntu directly quite yet. One of the things we were
waiting for is a kernel ABI version that Canonical added in the middle of the
Usually this isn't an issue in the driver but in the kernel. Have you tried the
latest stable or the latest in 3.14 (which is 3.14.29?)
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From:
-
From: Matyas Koszik [mailto:kos...@atw.hu]
Sent: Thursday, January 15, 2015 8:10 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] ixgbe: All RX packets go to rx_missed_errors (fwd)
Hi,
Yes I understand the workings of this list and that's fine, and I'm
Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Matyas Koszik [mailto:kos...@atw.hu]
Sent: Thursday, January 15, 2015 7:27 AM
To: Fujinaka, Todd
Subject: RE: [E1000-devel] ixgbe: All RX packets go to rx_missed_errors (fwd)
Hi,
I'm sorry
Battersby [mailto:to...@cybernetics.com]
Sent: Wednesday, January 07, 2015 3:02 PM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] igb: fix Tx Unit Hang on 82576 with RSS 1
Actually igb_cache_ring_register *did* change between igb-5.2.5.tar.gz and
igb
PM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] igb: fix Tx Unit Hang on 82576 with RSS 1
Actually igb_cache_ring_register *did* change between igb-5.2.5.tar.gz and
igb-5.2.9.2.tar.gz. My first patch did nothing more than revert that change to
make
) 712-4565
-Original Message-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent: Wednesday, January 07, 2015 3:23 PM
To: Tony Battersby; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] igb: fix Tx Unit Hang on 82576 with RSS 1
I just downloaded igb-5.2.5
this mistake being made again but the fix may not be
released for some time.
Thanks for finding that bug.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd
Sent: Wednesday, January
Message-
From: Tony Battersby [mailto:to...@cybernetics.com]
Sent: Wednesday, January 07, 2015 11:06 AM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] igb: fix Tx Unit Hang on 82576 with RSS 1
I had igb_cache_ring_register() print out the relevant values
I think we'll need more details. Statistics from ethtool and any relevant
messages from dmesg and /var/log/messages would be good. What's the hardware
and OS?
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
NACK. The fix is incorrect and just invalidates the case statement in general.
The TX hang message really doesn't tell you anything and it would be more
useful to see the full logs. We'll need a lot more information to debug this
issue. I would suggest filing the issue on sourceforge with all
Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Tony Battersby [mailto:to...@cybernetics.com]
Sent: Wednesday, January 07, 2015 9:28 AM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] igb: fix Tx Unit
(503) 712-4565
-Original Message-
From: Steffen Persvold [mailto:s...@numascale.com]
Sent: Friday, December 26, 2014 11:14 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net; Daniel J Blueman
Subject: Re: [E1000-devel] Sporadic packet loss observed with newer in-kernel
drivers
I would check with the netconsole people on this one. I'm not sure netconsole
is well supported and some of the things it does to queue up data before the
interface is ready can cause issues with our driver. We tried fixing our driver
but the kernel community, IIRC, said netconsole should be
...@zte.com.cn]
Sent: Tuesday, December 23, 2014 7:08 PM
To: Fujinaka, Todd
Cc: e1000-de...@lists.sf.net
Subject: 答复: RE: [E1000-devel] i installed igb drivers on sles11sp3 os，then
lscpican't be excuted, duplicate entry.
versions: igb-5.1.2, igb-5.2.9.4
Everytime, i can reproduce this error on sles11sp3 os
What version of igb, and what steps did you use?
You could probably work around this by running the update-pciids script if
you have it (it's in /usr/sbin on my Fedora 21 box).
If you can reproduce this, I'll submit this as a bug.
Todd Fujinaka
Software Application Engineer
Networking
Hello.
Thanks for the patches, but you submitted them to the out-of-tree driver and I
doubt that we will incorporate changes into our driver without a clear business
need. Currently our focus is limited to stability fixes on igb.
I would suggest submitting the changes to the kernel for
Message-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent: Wednesday, December 17, 2014 4:06 PM
To: Allan, Bruce W; Chris J Arges
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on
Ubuntu 3.13.0-30
Never mind. I found
The in-kernel and out-of-tree driver aren't exactly the same and there could be
differences enforced by the community that create that difference. For example
- and I'm just making this up - there could be a difference in the dropping or
passing of packets with bad checksums.
More likely are
) 712-4565
-Original Message-
From: Steffen Persvold [mailto:s...@numascale.com]
Sent: Friday, December 19, 2014 9:14 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net; Daniel J Blueman
Subject: Re: [E1000-devel] Sporadic packet loss observed with newer in-kernel
drivers (5.2.15
) 712-4565
-Original Message-
From: Allan, Bruce W
Sent: Friday, December 12, 2014 8:15 AM
To: Chris J Arges; Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on
Ubuntu 3.13.0-30
-Original Message-
From
Never mind. I found 3.13.0-43 on 14.04LTS.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd
Sent: Wednesday, December 17, 2014 3:43 PM
To: Fujinaka, Todd; Allan, Bruce W
Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Matyas Koszik [mailto:kos...@atw.hu]
Sent: Tuesday, December 16, 2014 1:35 AM
To: Fujinaka, Todd
Cc: e1000-de...@lists.sf.net
Subject: RE: [E1000-devel] X710 issues
Hi,
The chattyness doesn't really concern me
I'm not sure why you installed an old driver (from 6/13) with a newer kernel
(looks like 9/14). Can you either try the in-kernel driver or update to the
latest igb-5.2.15 first?
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
Perhaps a network diagram would help. It sounds like you're the router, with
multiple flows coming in and one going out. If this is the case, the rx/tx
would be paired and all on one queue.
Can you please clarify?
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel
as the
schedule is still pending.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Matyas Koszik [mailto:kos...@atw.hu]
Sent: Monday, December 15, 2014 2:54 AM
To: Fujinaka, Todd
Cc
Thanks for looking into this. At this time we are not sure when we can have
someone look into your issues, so please send us patches so that we may test
those. Some of the code execution paths may not be applicable and we will
ACK/NAK the patches as necessary.
Please make sure to test your
The latest driver for i40e is 1.1.23 and has been available since early
November on e1000.sourceforge.net and downloadcenter.intel.com. That will fix
the chattiness of the driver.
We don't directly support CentOS, so you'll have to reproduce on Red Hat
Enterprise Linux for most issues, but I
This is a known issue. Should be lots of hits in the archives.
TL;DR - should be fixed soon and there's minimal need to upgrade to 3.22.3 for
most users.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original
Ugh. I need coffee.
Minimal need to upgrade to 3.22.3 for most users of RHEL 6.6.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent
First, thanks for the patch. You'll have to include it in the text of the
message because it gets stripped here.
Unfortunately, we may not be able to take it (depending on what you did, the
attachment gets stripped) because you guys don't put any identifiers for your
kernel (like a define that
at
it. The easiest way to do that is to file a bug on e1000.sourceforge.net.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd
Sent: Monday, December 01, 2014 8:38 AM
I would say try the newest driver. Remember to do ethtool -i ethX to make
sure the new driver is actually being used.
If you still have problems we'll need a lot more information including logs
(dmesg and, if it exists, /var/log/messages and don't edit them) ethtool -i,
ethtool -s, lspci -vvv
After discussing this locally, I'd like to NAK it because this could cause
regressions to parts that are still in use but we don't have access to. Also,
the assignment was necessary in the past for some versions of gcc and since
this may be used in embedded systems using older compilers, we
I think you need to download install and run it to compile iqvlinux.tar.gz
The file install is a shell script.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Muharrem SARI
I'm not sure there's much need to actually change the value. It's been the same
since 2007 when the log message says, Removed FIXME comment.
I think someone forgot to remove the second FIXME comment. I'll send a patch.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel
I don't think the 82574L uses the igp3 PHY so you shouldn't have to worry about
any of this.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: SUN Catalpa [mailto:sunzihang...@gmail.com]
) of Fedora 21,
though it has some issues as well.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent: Wednesday, October 15, 2014 9:11 AM
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Madhur Sethi [mailto:mad...@attivonetworks.com]
Sent: Monday, October 20, 2014 11:27 AM
To: Fujinaka, Todd; 'e1000-devel@lists.sourceforge.net'
Subject: RE: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged
packets when
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
From: 蒙奇D小碗豆 [mailto:wenx05124...@163.com]
Sent: Wednesday, October 15, 2014 7:16 PM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re:RE: [E1000-devel] igb driver irq affnity
Yes. You can only set affinity of an interrupt line to one core.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: 蒙奇D小碗豆 [mailto:wenx05124...@163.com]
Sent: Wednesday, October 15, 2014
Can you send us the output of lspci -vvv (run as root) and ethtool -s?
I'm guessing that you're trying to use memory on remote NUMA nodes. You can try
running:
https://software.intel.com/en-us/articles/intel-performance-counter-monitor-a-better-way-to-measure-cpu-utilization
While it sounds
...@intel.com
(503) 712-4565
-Original Message-
From: Madhur Sethi [mailto:mad...@attivonetworks.com]
Sent: Wednesday, October 15, 2014 6:02 AM
To: Fujinaka, Todd; 'e1000-devel@lists.sourceforge.net'
Subject: RE: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged
packets when
-Original Message-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent: Monday, October 06, 2014 10:31 AM
To: Madhur Sethi; 'e1000-devel@lists.sourceforge.net'
Subject: Re: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged
packets when using with openvswitch
I've submitted
todd.fujin...@intel.com
(503) 712-4565
From: Madhur Sethi [mailto:mad...@attivonetworks.com]
Sent: Friday, October 03, 2014 10:44 PM
To: Fujinaka, Todd; 'e1000-devel@lists.sourceforge.net'
Subject: RE: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged
packets when using with openvswitch
Hi
There aren't enough details here. Can you tell us the exact steps you used for
configuring the VLANs on the host and guest?
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From:
To: Fujinaka, Todd; 'e1000-devel@lists.sourceforge.net'
Subject: RE: [E1000-devel] igb 5.0.3-k driver doesnt pick up vlan tagged
packets when using with openvswitch
Hi Todd,
Please find below the details of the configuration.
openVSwitch config:
[root@XXX ~]# ovs-vsctl show
3c55434d-c453-49e9-884d
[mailto:pankajc...@gmail.com]
Sent: Monday, September 29, 2014 11:18 PM
To: Fujinaka, Todd
Subject: Re: how to read eeprom dump for e1000e, igb and ixgbe?
hi Todd,
Sorry for the late answer. It is not an customer issue, so I am not sure if
filling a bug will help here. I have a local setup for 82599
I think you need to update the NICs. Please contact your factory support. We
won't be able to provide that level of support on this mailing list.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original
We have already answered this question through formal means.
We don't support 32-bit drivers for i40e at this time.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Santosh Jodh
Please contact your factory representative. This is not a request that can be
met on an open mailing list.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Schwandt, Daniel
Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Deepa G [mailto:gde...@identiv.com]
Sent: Monday, September 22, 2014 10:11 PM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd
Sent: Monday, September 22, 2014 9:22 AM
To: Deepa G; e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] i211 not working
There will be a default MAC address and device ID and the default device ID
Please contact your factory representative (whoever you bought the parts from)
for support and tools to program your NVM. The kernel you have should have
support for the i211.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503)
I would suggest reading the PCIe specification.
We also have Errata on several of our parts regarding ASPM. Please refer to the
Specification Update for the specific part.
If you're looking for NDA data, please contact us through your factory rep (or
directly, if you can).
Todd Fujinaka
Which OS are you using? Is it Debian (where we've been having troubles lately)?
We support RHEL7 and RHEL 6, and SLES 11 SP3 and SLES10 SP4, and upstream
kernels. Sometimes we have issues with other kernels because of inaccurate or
unexpected version strings in the kernel.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Steven Nelson [mailto:snel...@futurehealthsoftware.com]
Sent: Tuesday, September 02, 2014 3:12 PM
To: Fujinaka, Todd; e1000-devel@lists.sourceforge.net
-4565
-Original Message-
From: Wyborny, Carolyn
Sent: Tuesday, August 26, 2014 8:18 AM
To: William Dauchy; Williams, Mitch A; Fujinaka, Todd
Cc: net...@vger.kernel.org; e1000-devel; Kirsher, Jeffrey T
Subject: RE: igbvf warning on 3.14.x
Adding Todd Fujinaka, who is customer support
Looking at your patches on netdev, it appears that there are flags set in the
skb that should never be set for the 82572EI as that part doesn't have hardware
timestamping. This points to a bug in the ptpd code.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel
You don't have the right kernel headers. Look at the running kernel from uname:
Linux gfs-5 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC
and it's not the same as the headers you have installed:
kernel-headers-2.6.32-431.20.5.el6.x86_64
Thanks.
Todd Fujinaka
Software
Have you gone back and forth between the kernels? What is on the other end of
the link? Have you checked your cabling?
If you're from Arista, I'd suggest filing this through more formal means
(through your factory contacts) so this can be tracked more carefully.
Thanks.
Todd Fujinaka
Software
-
From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
Sent: Thursday, July 10, 2014 6:17 PM
To: yl-tencent; e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] NET: Change NVM page size from 128 bytes per
page to 64 bytes per page for Intel 82576
nvm-page_size doesn't appear to have
nvm-page_size doesn't appear to be referring to the NVM page size. It's just
using the same name.
I'm looking into this to see exactly what we're referring to; I should have an
answer by tomorrow.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
nvm-page_size doesn't appear to have any correlation to the page size of the
NVM. I'll have to look into it further but I think the name is misleading.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
To: Fujinaka, Todd; e1000-de...@lists.sf.net
Subject: RE: igb Detected Tx Unit Hang during network load
I have created a support ticket (https://sourceforge.net/p/e1000/bugs/424/). I
am currently trying to test what effect the receiving machine has, and will
post on the ticket when I have some
If this is a critical issue, please submit it through your factory rep and get
it into IPS directly. As far as I know, there's no direct SLA on this mailing
list.
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503)
Oh, and it looks like I did reply to the bug and there's no response there. I
think the ball is in your court.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Fujinaka, Todd
Just to be pedantic, I'm going to say a couple of things that you may know
already. The e1000 driver does not support the i210. You need to just refer to
the igb driver. Wake-up is a term used for Wake-on-LAN.
That being out of the way, we did notice a problem with the in-kernel driver
with
The answer is the same for all the drivers: we have identified a fix for the
current Ubuntu. However, currently Ubuntu doesn't have a unique identifier that
allows us to create general workarounds.
The next driver release should have a build fix for Ubuntu. However, this leads
to another
Yes, but it's limited. For more details on how to test loopback please file
this issue through your factory representative.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From:
Unfortunately that's the result of an actual fix. The I2C code, to be robust
(and, if I recall correctly, to be correct) takes a while to time out. More
empty ports means a longer time to confirm that the ports are empty.
We are expecting the standard use case to not have four empty ports.
It's hard to tell what hardware you're running. Can you send the output of
lspci | grep Ethernet?
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Dilip Kumar Uppugandla
...@intel.com
(503) 712-4565
From: Dilip Uppugandla [mailto:di...@purestorage.com]
Sent: Friday, June 13, 2014 12:34 PM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] igb rx lockup with high rx_fifo_errors
lspci | grep Ethernet output:
01:00.0 Ethernet controller
...@intel.com
(503) 712-4565
-Original Message-
From: David Goodenough [mailto:david.goodeno...@linkchoose.co.uk]
Sent: Tuesday, June 10, 2014 4:25 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] 82551QM problem
I tried google, but it found me nothing
: Tuesday, June 10, 2014 8:24 AM
To: Fujinaka, Todd
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] 82551QM problem
On Tuesday 10 June 2014 15:20:40 Fujinaka, Todd wrote:
The first google entry for me brought up BVM-store.com. We don't make
the card, so you'll have to contact
Unfortunately that part was EOLed several years ago so I think google is your
best resort.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: David Goodenough
Depends entirely on the system. It's possible, but not likely.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: nirmoy das [mailto:nirmoy.ai...@gmail.com]
Sent: Sunday, June 08, 2014
...@lists.infradead.org; Duyck, Alexander H; Thomas Petazzoni;
e1000-devel@lists.sourceforge.net; Jason Gunthorpe; Fujinaka, Todd; Lucas Stach
Subject: Re: [E1000-devel] ARM support for igb driver
Yes its hardware bug. I need to know whether we can disable it from device
side? If yes, how?
On Sun
Petazzoni; e1000-devel@lists.sourceforge.net; Fujinaka, Todd; Lucas Stach
Subject: Re: [E1000-devel] ARM support for igb driver
Notsure about root port, Can't it be disabled by Intel device?
On Sat, May 31, 2014 at 1:26 AM, Arnd Bergmann a...@arndb.de wrote:
On Saturday 31 May 2014 01:05:29 shiv prakash
201 - 300 of 372 matches
Mail list logo
