Re: [e1000-devel] No versions for igb driver available on "modinfo igb" for SLE15-SP4

2024-01-18 Thread Jesse Brandeburg
On 1/11/2024 4:21 AM, kumar.mo...@swisscom.com wrote: > Hi, > > Unlike the previous releases for the drivers, we don’t see the column for > version anymore for the Intel(R) Gigabit Ethernet Network Driver in SUSE > Linux (SLE15-SP4) when doing modinfo igb. > > Is this something expected and if

Re: [e1000-devel] Intel E810 100Gb goes down sporadically

2023-12-05 Thread Jesse Brandeburg
On 12/3/2023 1:26 AM, Assaf Albo via E1000-devel wrote: > Hello guys, > > We are having constant network issues in production in that the link goes > down, waits *exactly* 7-8 seconds, and goes up again. > This can happen zero to a few times a day on all our servers; they are not > in the same loc

Re: [e1000-devel] idg driver compilation error on Ubuntu

2023-11-07 Thread Jesse Brandeburg
On 10/30/2023 3:27 AM, adelio ALVES wrote: Thanks for your report! Something happened to the content of your message when I released it to the mailing list. Please use the driver included in your kernel (igb.ko.xz or the like) and let us know if you have any problems. Was there a reason you wan

Re: [e1000-devel] Stablish uni-directional ethernet link

2023-07-28 Thread Jesse Brandeburg
On 7/28/2023 6:26 AM, Alireza Sadeghpour wrote: > Hi, I am trying to establish a uni-directional Ethernet link where a > singular fiber is used to transmit data to the receiver where both sides > use ixgbe as driver. The Rx of the transmit side and the Tx of the receive > side are not physically co

Re: [e1000-devel] Issue with Intel Corporation 82546EB dual port card on Ubuntu 22.04

2023-05-12 Thread Jesse Brandeburg
On 5/11/2023 9:54 PM, Igor Cicimov wrote: > Hi, > > I have a problem with my 8086:1010 Intel Corporation 82546EB Gigabit > Ethernet Controller (Copper) dual port ethernet card and Ubuntu 22.04.2 LTS > using e1000 driver: This card is from 2003! :-) Nice that it's still running! Did you fil

Re: [e1000-devel] error in e1000e driver under ubuntu20.04 HWE with kernel 5.15.0-67

2023-03-28 Thread Jesse Brandeburg
On 3/27/2023 12:32 AM, ST Cai wrote: > OS:Ubuntu Server 20.04 HWE > Kernel:5.15.0-67-generic > Adapter:Intel(6)I219-V;Vendor:0x8086;Product:0x15be; > Drivers :e1000e-3.8.4/e1000e-3.8.4; > > make install Error: > > ethtool.c:2838:19: error: initialization of ‘int (*)(struct net_device *, > struct

Re: [e1000-devel] missing symbols ice and i40e for irdma modules

2023-03-13 Thread Jesse Brandeburg
On 3/10/2023 12:25 AM, Dmitry Kravkov wrote: > after loading ice 1.11.14 module which compiled for 6.1.8 > irdma modules is not able to load due to missing symbols: > [1000969.082365] irdma: Unknown symbol ice_del_rdma_qset (err -2) > [1000969.082599] irdma: Unknown symbol ice_add_rdma_qset (err -2

Re: [e1000-devel] [ice] Intel E810-C one queue after reboot

2023-01-24 Thread Jesse Brandeburg
On 1/21/2023 6:17 AM, Highload Admin wrote: Hello! FYI, general spam filter guidance is to ignore mails from admin@ mails, so our list rejects your subscription. I'd change it but we get a lot of mails from bogus admin@ accounts. I have a problem with ice driver (I tried 1.10.1.2 an1.10.1

Re: [e1000-devel] i40e: Intel XL710: Linux Debian 11: rx/tx-vlan-offload seems to be broken since 2.18.9

2023-01-03 Thread Jesse Brandeburg
On 12/30/2022 11:15 AM, Andrey Kulikov wrote: Hello, I've got an Intel Fortville XL710-based Ethernet controller with 4 x 10GbE SFP+ ports. Platform is based on Intel Xeon CPU E5-2697 v4 Platform running Debian 11.6, kernel 5.10.0 # uname -a Linux 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-1

Re: [E1000-devel] Driver issue 5.4.0-1064 Kernel

2022-11-04 Thread Jesse Brandeburg
On 11/3/2022 9:05 AM, Trey Hughes via E1000-devel wrote: Good morning, I'm having an issue with installing the e1000e driver version 3.8.4 on Ubuntu 18.04 with Kernel 5.4.0-1064. When I go to make install per the readme instructions, I get an error stating the UTS_UBUNTU_RELEASE_ABI is too larg

Re: [E1000-devel] Citrix Hypervisor (XenServer) - very poor performance with X710

2022-03-14 Thread Jesse Brandeburg
On 3/14/2022 8:28 AM, Kevin Bowling wrote: Fortville (700) has always been a bit of a disaster (https://cdrdv2.intel.com/v1/dl/getContent/331430?explicitVersion=true), I'd see if you can press your Intel reps into getting you the 550s or the 800-series NICs for the unnecessary troubles it's a muc

Re: [E1000-devel] errors on link xl 710

2021-11-23 Thread Jesse Brandeburg
On 11/22/2021 9:43 PM, Jakub Osuch wrote: I have errors on link between nexus N3K-C3064PQ-10GX and LREC9902BF-2QSFP+. driver: i40e version: 2.17.4 Take a look: shorturl.at/crCNQ Hi Jakub, please file a bug at https://sourceforge.net/p/e1000/bugs/ Which will allow you to attach relevant infor

Re: [E1000-devel] [Intel-wired-lan] Not able to create VFs on PF passthrough of ethernet interface to VM

2019-05-13 Thread Jesse Brandeburg
On Mon, 13 May 2019 07:36:41 + Periyasamy wrote: > Hi, > > I’m trying to achieve PF passthrough of 40/10G ethernet interface (i40e) into > guest VM running on qemu/kvm hypervisor and then create VFs on the PF inside > the VM. > This is to have a flexibility and better manageability of VFs in

Re: [E1000-devel] Some X710 NIC settings, need your help.

2017-04-06 Thread Jesse Brandeburg
On Thu, 6 Apr 2017 07:05:14 + Jonny Shuai4 Zhao wrote: > Hello, > When I use ixgbevf on x520 NIC, I can set "options ixgbevf > InterruptThrottleRate=***" > in /etc/modprobe.d/ixgbevf.confixgbevf.conf file. Now I use X710 > with the newest i40evf version in VM , I want to set the > InterruptT

Re: [E1000-devel] jitter / latency reduction

2017-03-29 Thread Jesse Brandeburg
On Mon, 6 Mar 2017 08:09:42 -0800 Mahmood Qazen wrote: > greetings Leonardo > this is the slide / pdf I found and towards the end it asks if we > could help. > enjoy > Mahmood - Hi developers, thanks for your interest, we’d love to have help, but the good/bad news is that this is implemented alr

Re: [E1000-devel] ixgbe port missing, "PCI INT B: failed to register GSI"

2016-12-07 Thread Jesse Brandeburg
On Tue, 6 Dec 2016 17:24:18 -0800 Ben Greear wrote: > On 12/06/2016 05:15 PM, Fujinaka, Todd wrote: > > Attachments don't work here. You'll have to file a bug on sourceforge, or > > file an IPS for factory support (and tell me the number so it doesn't sit). > > > > Ok, here it is inline then

Re: [E1000-devel] i40e: xl710 chipset in 4.8 kernel

2016-11-21 Thread Jesse Brandeburg
On Sat, 19 Nov 2016 23:05:57 +0300 Yavuz Selim Komur wrote: > Hi, > > i40e drops all UDP traffic when upgrade to 4.8 from 4.7 linux kernel. > > all DHCP, DNS traffic stop. i40e not forwards any UDP. > > is this possible Hi Yavuz, please be more specific, as there may be some reason for your i

Re: [E1000-devel] [Intel-wired-lan] i40e card Tx resets

2016-03-18 Thread Jesse Brandeburg
On Thu, 17 Mar 2016 14:56:14 -0400 Sowmini Varadhan wrote: > On (03/17/16 10:20), zhuyj wrote: > > 1. modprobe NET_PKTGEN > > > > 2. download the tar file and uncompress to any directory. > > This tar file is from kernel. It is in samples/pktgen/ > > > > 3. cd pktgen > > > > 4. pktgen_sample02

Re: [E1000-devel] 82574l GB network controller for WinCE 5.0

2015-08-26 Thread Jesse Brandeburg
On Tue, 25 Aug 2015 11:33:40 +0300 Eli Kedem wrote: > I am developing an NDIS (v5.1) miniport device driver for the 82574l GB > network controller for WinCE 5.0. The main problem is that the BSP is > very deficient and KITL does not work and the board does not have JTAG > interface either. I hav

Re: [E1000-devel] i40e - Unqualified modules was detected

2015-08-21 Thread Jesse Brandeburg
On Fri, 21 Aug 2015 20:44:06 + John McDowall wrote: > Hi, > > I am trying to get a dual 10G X7100 interface up and on boot I am seeing the > following message: > > > i40e :04:00.0 p1p1: the driver failed to link because an unqualified > module was detected. > > [5.092641] IPv6:

Re: [E1000-devel] [net-next 8/9] i40e/i40evf: Bump i40e/i40evf version

2015-04-01 Thread Jesse Brandeburg
On Wed, 1 Apr 2015 11:52:37 +0200 Ronald van der Pol wrote: > On Thu, Mar 26, 2015 at 23:01:46 -0700, Jeff Kirsher wrote: > > > netdev is not the right mailing list for this question. > > Adding e1000-devel mailing list... > > Sorry about that. I still have problems with getting the Intel X4DAC

Re: [E1000-devel] i40e: trivial fixes

2014-12-02 Thread Jesse Brandeburg
On Tue, 2 Dec 2014 16:01:07 +0300 Dan Carpenter wrote: > Hello Jesse Brandeburg, > > The patch 895106a577c4: "i40e: trivial fixes" from Nov 26, 2013, > leads to the following static checker warning: > > drivers/net/ethernet/intel/i40e/i40e_hmc.c

Re: [E1000-devel] [patch net-next] i40e: remove dead fdb code

2014-11-20 Thread Jesse Brandeburg
On Thu, 20 Nov 2014 14:10:29 +0100 Jiri Pirko wrote: > This code is not used now and also it contains some weird ifdefs. So > remove it for now. It can be added when needed. > First, thanks for looking at our code. but, NAK, the code just needs to have the #ifdefs removed. In addition the fdb

Re: [E1000-devel] HW behavior when RA is partially written

2013-12-10 Thread Jesse Brandeburg
On Tue, 26 Nov 2013 13:55:56 -0500 Vlad Yasevich wrote: > > > > Thank for taking a look. I saw the AV bit in RAH as well. That's > > what got me asking the question. The data sheet says AV gets turns off > > on resets only. So if the address is changing from one value to > > another AV is sti

Re: [E1000-devel] HW behavior when RA is partially written

2013-11-15 Thread Jesse Brandeburg
On Thu, 14 Nov 2013 16:10:13 -0500 Vlad Yasevich wrote: > Hi all > > I was wondering what does HW do when the receive address register > is only partially written? The reason I am wondering is that > it looks like most drivers have to program the receive address > register in 2 writes. What ha

Re: [E1000-devel] [net-next v5 8/8] i40e: include i40e in kernel proper

2013-09-06 Thread Jesse Brandeburg
On Fri, 6 Sep 2013 14:01:41 -0400 David Miller wrote: > Please rename this Kbuild file to the normal Makefile instead of > trying to be different from every single other driver in the > networking for the sake of an issue that is your, and your problem > alone. Thanks Dave, will do, I'm preparing

Re: [E1000-devel] [PATCH net-next] drivers:net: Convert dma_alloc_coherent(...__GFP_ZERO) to dma_zalloc_coherent

2013-08-27 Thread Jesse Brandeburg
Remove memset from the static inline dma_zalloc_coherent > and add just one use of __GFP_ZERO instead. > > Trivially reduces the size of the existing uses of > dma_zalloc_coherent. > > Realign arguments as appropriate. > > Signed-off-by: Joe Perches e1000

Re: [E1000-devel] e1000e on thinkpad x60: interrupt problem

2013-07-09 Thread Jesse Brandeburg
On Tue, 9 Jul 2013 22:48:54 +0200 Pavel Machek wrote: > Yeah, of course you need to ask e1000e if it generated the > interrupt. That part works. The part that actually generates the > interrupt does not. Take a look at original mail... > > packet comes > e1000e sets E1000_ICR_INT_ASSERTED bit >

Re: [E1000-devel] [RFC 0/7] Fixing dma mask setting in various network drivers

2013-06-11 Thread Jesse Brandeburg
On Tue, 11 Jun 2013 13:35:05 -0700 Russell King - ARM Linux wrote: > As part of my review of all this stuff, I'm wondering whether a helper > to set both masks makes sense. Something like: > > static inline int dma_set_masks(struct device *dev, u64 mask) it doesn't need to be inline, it is neve

Re: [E1000-devel] [RFC 0/7] Fixing dma mask setting in various network drivers

2013-06-11 Thread Jesse Brandeburg
On Tue, 11 Jun 2013 00:08:49 +0100 Russell King - ARM Linux wrote: > While looking at the way coherent DMA masks are handled (and the > fact many drivers write directly to the mask) I stumbled across > this set of oddities in various network drivers, which looks like > it's been cut'n'pasted. >

Re: [E1000-devel] Memory Corruption with e1000

2013-06-06 Thread Jesse Brandeburg
On Thu, 6 Jun 2013 09:38:50 -0700 Peter LaDow wrote: > On Thu, Jun 6, 2013 at 12:30 AM, Peter P Waskiewicz Jr > wrote: > > What about the pre-emption behavior of the kernel? Namely Processor type > > and Features -> Preemption Model. Are you using no preemption, or forced > > preemption? > >

Re: [E1000-devel] Higher throughput at 100Mbps than 1Gbps

2013-05-21 Thread Jesse Brandeburg
On Tue, 21 May 2013 19:24:24 +0100 Sam Crawford wrote: > To be clear, this doesn't just affect this one hosting provider - it seems > to be common to all of our boxes. The issue only occurs when the sender is > connected at 1Gbps, the RTT is reasonably high (> ~60ms), and we use TCP. > > By posti

Re: [E1000-devel] [PATCH v2 net-next 0/4] net: low latency Ethernet device polling

2013-05-20 Thread Jesse Brandeburg
On Mon, May 20, 2013 at 1:09 PM, Jeff Kirsher wrote: > On Sun, 2013-05-19 at 22:20 +0300, Eliezer Tamir wrote: > > On 19/05/2013 22:06, Or Gerlitz wrote: > > > On Sun, May 19, 2013 at 1:25 PM, Eliezer Tamir > > > wrote: > > >> This is an updated version of the code we posted on February. > > > >

Re: [E1000-devel] pci probe of 82574 fails

2013-01-29 Thread Jesse Brandeburg
On Tue, 29 Jan 2013 13:49:17 -0800 akepner wrote: > On Fri, Jan 25, 2013 at 08:25:17PM +, Ronciak, John wrote: > > This could be BIOS configuration as well. Check the BIOS version as Tushar > > says but also look at how you have the device/slot configured in the BIOS. > > > > The "probe o

Re: [E1000-devel] e1000e: ethtool -t fails when i/f is up

2012-11-16 Thread Jesse Brandeburg
On Fri, 16 Nov 2012 14:58:13 -0800 akepner wrote: > With e1000e (versions 1.2.20, and 2.1.4) we've noticed that the > ethtool selftest fails with a miscompare when the interface is > up, but succeeds when it's down: Which hardware are you using? # lspci -nn what shows from: # ethtool lan0_0

Re: [E1000-devel] [PATCH net] e1000e: Change wthresh to 1 to avoid possible Tx stalls.

2012-10-09 Thread Jesse Brandeburg
> > > Jesse did not share any performance numbers with me, I am sure he can > > > give some background tomorrow when he is back online. > > > > > > I am working on an alternative patch now and should have something to > > > share tomorrow. > > Please allow me to ask if there's any progess here? >

Re: [E1000-devel] 100+ ms latency when 82599EB put under moderate load

2012-09-12 Thread Jesse Brandeburg
On Wed, 12 Sep 2012 22:47:55 +0200 Dick Snippe wrote: > On Wed, Sep 12, 2012 at 04:05:02PM +, Brandeburg, Jesse wrote: > > > Hi Dick, we need to know exactly what you are expecting to happen > > here. > > I'm surprised by the large increase in latency (from <1ms to >100ms). > In our product

Re: [E1000-devel] Intel 82546GB chip does not work with OpenVSwitch

2012-09-07 Thread Jesse Brandeburg
On Fri, 7 Sep 2012 12:37:04 +0200 Timm Essigke wrote: > I hope you can understand the cause of the problem from the ethregs > output included in the files. > > Thank you very much! looks like the attachment(s) either wasn't included or didn't make it through the list filters, can you upload to

Re: [E1000-devel] Intel 82546GB chip does not work with OpenVSwitch

2012-09-05 Thread Jesse Brandeburg
On Wed, 5 Sep 2012 17:13:52 +0200 Timm Essigke wrote: > First, I asked on the openvswitch mailing list and they consider it as a > driver problem. > > My system is: > Ubuntu 12.04 > Supermicro: Kernel 3.2.0-29-generic, 64-bit > Fujitsu: Kernel 3.2.0-29-generic-pae, 32-bit > Openvswitch 1.4.0-1ub

Re: [E1000-devel] Disable NAPI

2012-07-24 Thread Jesse Brandeburg
On Tue, 24 Jul 2012 10:24:05 -0700 Stephen Hemminger wrote: > On Tue, 24 Jul 2012 19:16:43 +0200 > Sandy Herman wrote: > > > Hello, > > > > I have a 8 core x86_64 machine that has 2 Intel 82574L NICs using > > the e1000 driver. > > > > Problem: > > During a spoofed SYN flooding attack (800 Mb

Re: [E1000-devel] igb 82576 dropping multicast packets

2012-06-14 Thread Jesse Brandeburg
On Wed, 13 Jun 2012 12:45:19 -0400 "Andrew J. Schorr" wrote: > Hi, > > On Tue, Jun 12, 2012 at 03:49:32PM -0400, Andrew J. Schorr wrote: > > Hi Jesse, > > > > On Tue, Jun 12, 2012 at 07:26:18PM +, Brandeburg, Jesse wrote: > > > Andrew, sorry for the top post my other email client is not wor

Re: [E1000-devel] igb 82576 dropping multicast packets

2012-06-13 Thread Jesse Brandeburg
On Wed, 13 Jun 2012 15:23:18 -0400 "Andrew J. Schorr" wrote: > Hi Jesse, > > On Wed, Jun 13, 2012 at 10:51:09AM -0700, Jesse Brandeburg wrote: > > Hi Andrew, thanks for sticking with us while figuring out a solution. > > You're welcome, but it'

Re: [E1000-devel] Strange latency spikes/TX network stalls on Sun Fire X4150(x86) and e1000e

2012-06-06 Thread Jesse Brandeburg
On Wed, 6 Jun 2012 Hiroaki SHIMODA wrote: > Sorry for long delay. I'll post. > (I have no idea how to fix this problem as keeping TXDCTL.WTHRESH to 5) I don't like changing WTHRESH wholesale because making the global change to WTHRESH on e1000e just to fix this one bug (likely specific to a parti

Re: [E1000-devel] Proper way to turn off VLAN tag stripping for 82599 (ixgbe 3.9.15 driver)?

2012-05-25 Thread Jesse Brandeburg
On Thu, 24 May 2012 11:08:02 -0700 Maniquis Angelo wrote: > What is the proper way to disable VLAN stripping while in promiscuous > mode?  Is it as simple as a modprobe ixgbe option that I'm missing or > something else? Can't you just disable using ethtool? ethtool -K|--offload DEVNAME

Re: [E1000-devel] ioatdma 0000:00:0a.1: Channel halted, chanerr = 2

2012-04-30 Thread Jesse Brandeburg
On Mon, 30 Apr 2012 22:31:26 + John Adams wrote: > Dear e1000-devel, > > I'm wondering what kernel versions people are happily using in > production with the ixgbe driver? > > I'm having network stability and performance issues with a 2.6.32-131 > modified Red Hat el6 on a quad core Xeon Ja

Re: [E1000-devel] [PATCH RFC 0/2] e1000e: 82574 also needs ASPM L1 completely disabled

2012-04-23 Thread Jesse Brandeburg
On Mon, 23 Apr 2012 22:29:36 +0100 Chris Boot wrote: > Please note I haven't as-yet tested this code at all, but I do know that > disabling ASPM L1 on these NICs (using setpci) fixes the hangs that I > have been seeing on my Supermicro servers with X9SCL-F boards. I hope to > get the chance to ins

Re: [E1000-devel] [PATCH] e1000e: MSI interrupt test failed, using legacy interrupt

2012-04-19 Thread Jesse Brandeburg
On Thu, 19 Apr 2012 10:59:47 -0700 Prasanna Panchamukhi wrote: > On 04/19/2012 08:54 AM, Allan, Bruce W wrote: > > We have not seen a report of this issue before. Please provide details on > > the NIC or LOM and system/chipset on which the problem occurs and how the > > additional 50ms was det

Re: [E1000-devel] Ixgbe, tcp_offloading and MTU

2012-04-12 Thread Jesse Brandeburg
On Thu, 12 Apr 2012 13:44:35 +0200 Walter Zimmer wrote: > Hello! > > We just got a nice file server with an Intel 82599EB 10GB Ethernet adapter, > and are trying various things for optimal performance. > > That tcp-segmentation-offload is working really great, and I can see 64k > packets going

Re: [E1000-devel] can't enable Flow Control for e1000e / 82572EI

2012-04-10 Thread Jesse Brandeburg
On Tue, 10 Apr 2012 14:54:02 +0200 Marko Kobal wrote: > Hi, > > I have a "Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) (rev > 06)" in my CentOS 5.7 (2.6.18-274.7.1.el5 x86_64) box. > > I have installed the latest drivers (e1000e-1.10.6.tar.gz) but can't enable > Flow Control

Re: [E1000-devel] Intel 82574L rx_short_length_errors

2012-04-03 Thread Jesse Brandeburg
On Tue, 3 Apr 2012 17:49:25 +0300 Aleksey Chudov wrote: > I have few identical low end servers with the following integrated NICs: > 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connection > 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connecti

Re: [E1000-devel] Fw: Enable VF only on 2nd 82576 port

2012-03-30 Thread Jesse Brandeburg
Try modprobe igb max_vfs=-1,1 -- Spelling via autocorrect, please fogrive me On Mar 30, 2012, at 3:10 AM, Jemma Jones wrote: > > > If I load the driver with > > modprobe igb max_vfs=0,1 > > which would mean 0 VFs in PF 0 and 1 VF on PF 1 then I get an error saying > "0,1" invalid for par

Re: [E1000-devel] Intel e1000e crashes on high throughput

2012-03-05 Thread Jesse Brandeburg
please use e1000-devel@lists.sourceforge.net on all future replies. On Sun, 2012-03-04 at 23:42 -0500, Marcelo Pereira wrote: > Hello, > > > I have been struggling to use a NIC Intel e1000e, without success, for > days!! > > > I'm using the latest version of the driver (1.9.5), the kernel or

Re: [E1000-devel] e1000_close() and concurrent reset

2012-02-21 Thread Jesse Brandeburg
On Fri, 2012-02-17 at 15:35 -0800, Tim Pepper wrote: > On Wed 15 Feb at 23:29:17 + bruce.w.al...@intel.com said: > > > From: Tim Pepper [mailto:lnxni...@linux.vnet.ibm.com] > > > > > > A very similar bug report is here: > > > http://lists.openwall.net/netdev/2011/11/14/127 > > > and notes two

Re: [E1000-devel] rx_csum_offload_errors counter questions

2012-02-10 Thread Jesse Brandeburg
On Sat, 2012-02-11 at 01:24 +0700, Bokhan Artem wrote: > 11.02.2012 0:23, Jesse Brandeburg пишет: > > > Thanks! you're welcome! > > >> Does it count L2 or L3 errors? > > This counter is mostly for L3 or L4 errors (IP checksum, TCP checksum) > > >

Re: [E1000-devel] rx_csum_offload_errors counter questions

2012-02-10 Thread Jesse Brandeburg
On Fri, 2012-02-10 at 19:25 +0700, Bokhan Artem wrote: > Any thoughts? May be somebody can point to description? > > On 09.02.2012 16:49, Bokhan Artem wrote: > > Hello. > > > > I have several questions about rx_csum_offload_errors counter for igb and > > ixgbe > > drivers: > > > > What type of er

Re: [E1000-devel] High number of rx_missed_errors when chaning from 1.0.2-k2 to 1.2.20-k2/1.5.1-k

2012-01-26 Thread Jesse Brandeburg
On Thu, 2012-01-26 at 02:06 -0800, Carsten Aulbert wrote: > with 1.0.2-k2 and default options (except crcstripping=0) we get close to 120 > MB/s and no dropped packets. > > rebooting the system to a kernel with a newer driver yields only 150-250kB/s > throughput and a packet drop-rate close to

Re: [E1000-devel] ixgbe: Unsupported SFP+ modules on 10Gbit/s X520-DA2 NIC?

2012-01-18 Thread Jesse Brandeburg
On Wed, 18 Jan 2012 03:30:58 -0800 Jesper Dangaard Brouer wrote: > I just bought three 10Gbit/s X520-DA2 NICs (82599 based) for > production usage, but I cannot get them to accept any of my 10Gbit/s > SFP+ modules (4 different tried). According to the documentation I can > find, the X520-DA2 NIC s

Re: [E1000-devel] [PATCH net-next 2/2] igb: offer a PTP Hardware Clock instead of the timecompare method

2011-12-14 Thread Jesse Brandeburg
On Mon, 2011-12-12 at 19:00 -0800, Richard Cochran wrote: > This commit removes the legacy timecompare code from the igb driver and > offers a tunable PHC instead. > > Signed-off-by: Richard Cochran Richard, first, thanks for this work, I have some feedback and request you make a V2. > -

Re: [E1000-devel] interface counters

2011-12-13 Thread Jesse Brandeburg
On Tue, 2011-12-13 at 04:16 -0800, Bokhan Artem wrote: > Hello! > > Is it possible to update interface counters more often then every 2 secs? > Probably with some changes of source. yes it is possible and in fact several drivers do update a small set of stats in real time, or when called via the

Re: [E1000-devel] WARNING: at net/core/dev.c:1904 skb_gso_segment+0x146/0x298()

2011-12-05 Thread Jesse Brandeburg
cc: e1000-devel On Wed, 23 Nov 2011 16:30:34 -0800 Paweł Staszewski wrote: > After upgrade from 2.6.38.2 to 3.1.2 i have this im dmesg: > [ 600.266497] WARNING: at net/core/dev.c:1904 skb_gso_segment+0x146/0x298() > [ 600.266500] Hardware name: X8DTU-6+ > [ 600.266503] 802.1Q VLAN Support: cap

Re: [E1000-devel] [BUG] e1000: possible deadlock scenario caught by lockdep

2011-11-18 Thread Jesse Brandeburg
On Fri, 18 Nov 2011 08:57:37 -0800 Jesse Brandeburg wrote: > CC'd netdev, and e1000-devel > > On Thu, 17 Nov 2011 17:27:00 -0800 > Steven Rostedt wrote: > > Here you see that we are calling > > cancel_delayed_work_sync(&adapter->watchdog_task);

Re: [E1000-devel] [BUG] e1000: possible deadlock scenario caught by lockdep

2011-11-18 Thread Jesse Brandeburg
or_sti+0x5/0x6 > [] ? time_hardirqs_off+0x2a/0x2f > [] ? trace_hardirqs_on_thunk+0x3a/0x3f > [] ? retint_swapgs+0x13/0x1b > [] ? retint_swapgs+0x13/0x1b > [] ? trace_hardirqs_on_caller+0x12d/0x164 > [] ? audit_syscall_entry+0x11c/0x148 > [] ? trace_hardirqs_on_thunk+0x3a/0x3f > [] system_call_fastpat

Re: [E1000-devel] [PATCH] e1000e : Avoid wrong check on TX hang

2011-11-18 Thread Jesse Brandeburg
x27;m okay with the patch functionality because you're implementing (effectively, if not a little indirectly) the fix our hardware engineer suggested which was two writes to the FPD bit. We can test the patch in our

Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang

2011-10-25 Thread Jesse Brandeburg
On Mon, 24 Oct 2011 23:29:34 -0700 Michael Wang wrote: > May be you can just search macro > "E1000_TXDCTL_DMA_BURST_ENABLE" > in "drivers/net/e1000e/e1000.h", change it to: > > #define E1000_TXDCTL_DMA_BURST_ENABLE \ > (E1000_TXDCTL_GRAN | /* set descriptor granularity */ \ > E1000_TXDCTL_COUNT_D

Re: [E1000-devel] Problem with ixgbe and TX locked on one cpu

2011-10-18 Thread Jesse Brandeburg
CC: e1000-devel 2011/10/14 Paweł Staszewski : > Hello > > I have weird problem with ixgbe and irq affinity / rx-tx queue assignment what application are you running, how are you using ixgbe? looks like a router. is something changing the skb->rx_queue entry (like netfilter) or is there a layered

Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang

2011-10-17 Thread Jesse Brandeburg
seems to be related to the symptoms seen above: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3a3b75860527a11ba5035c6aa576079245d09e2a > > From: Jesse Brandeburg > Date: Wed, 29 Sep 2010 21:38:49 + (+) > Subject: e1000e: use hardw

Re: [E1000-devel] Possible to stop external IPMI/BMC access (port 623) by bringing iface up?

2011-09-28 Thread Jesse Brandeburg
On Wed, 28 Sep 2011 11:23:50 -0700 Carsten Aulbert wrote: > But now we reinstalled several machines with Debian Squeeze and > suddenly we can only query the BMC when eth0 is down. The kernel we > use is exactly the same (2.6.32.28 or 2.6.32.46 currently), i.e. same > binary .deb package, same conf

Re: [E1000-devel] 82574 DMA Burst Mode Enablement

2011-09-28 Thread Jesse Brandeburg
On Wed, 28 Sep 2011 11:39:54 -0700 Denis Radovanovic wrote: > We are currently testing small packet performance on 82574, comparing > it to 82571. Initial pktgen measurements have shown a significant > difference in performance that is the most visible when running > bidirectional traffic with 256

Re: [E1000-devel] [PATCH net-next-2.6] e1000: don't enable dma receives until after dma address has been setup

2011-09-15 Thread Jesse Brandeburg
On Wed, 14 Sep 2011 17:31:38 -0700 Dean Nelson wrote: > Doing an 'ifconfig ethN down' followed by an 'ifconfig ethN up' on a > qemu-kvm guest system configured with two e1000 NICs can result in an > 'unable to handle kernel paging request at 0001' or 'bad > page map in process ...' or

Re: [E1000-devel] e1000e: NIC not working (after resume?)

2011-09-09 Thread Jesse Brandeburg
On Fri, Sep 9, 2011 at 6:43 AM, Frederik Himpe wrote: > [Crossposting to e1000 mailing list] > > I have a Dell Latitude E6400 which has a network card supported by the > e1000e driver. Often (I think after a suspend/resume cycle), the network > card does not work at all: the NIC is correctly seen

Re: [E1000-devel] vlan steering

2011-09-08 Thread Jesse Brandeburg
On Tue, 6 Sep 2011 02:19:44 -0700 bill4carson wrote: > Hi, guys > > > Just a quick question about vlan steering, does 82599 support this > feature? > I didn't see any description about it in the 82576/82599 specification I think what you're looking for is the VMDQ mode of the hardware, where

Re: [E1000-devel] e1000e check_mng_mode issue

2011-08-24 Thread Jesse Brandeburg
ard-coded zero (allowing those > functions to occur), which would require the user to ensure that IPMI > LAN had been disabled before exercising this. > > Would you like me to take a stab at implementing option 1, or do you > have a better idea? > > Andy > > -Origin

Re: [E1000-devel] e1000e check_mng_mode issue

2011-08-24 Thread Jesse Brandeburg
On Tue, 23 Aug 2011 14:38:18 -0700 Andy Cress wrote: > Tushar, > > Thanks for running this down. So that means that the current driver > implementation would never allow a NIC which has a BMC sideband > connection physically to ever power off the PHY. > > That doesn't seem like the right appro

Re: [E1000-devel] Spam

2011-08-03 Thread Jesse Brandeburg
2011/8/1 CLOSE Dave : > I've tried asking privately to the "owner" of this list but have seen no > response. Is there some reason why we can't filter this crap? Does > anyone "manage" the list and remove offenders? Hi Dave, yeah, sorry about the spam to this list, but we don't want to make it a cl

Re: [E1000-devel] non_eop_descs

2011-08-02 Thread Jesse Brandeburg
On Tue, Aug 2, 2011 at 6:12 PM, Richard Scobie wrote: > I have a NAS box set up with bridged interfaces, a couple of which are > 82598EB AF. > > The host boxes direct attached to these are performing more or less > identical tasks, but one interface shows no non_eop_descs and the other > many. >

Re: [E1000-devel] Getting information from Users

2011-06-23 Thread Jesse Brandeburg
On Thu, Jun 16, 2011 at 12:21 PM, Martin Owens wrote: > Hey devels, > > I'm updating my bug report with requested information and thought I > might as well make a script to automatically pull all the information > together. This is awesome, thank you, I think that it needs some minor tweaks howev

Re: [E1000-devel] Question on net_stats->rx_dropped setting to "0"

2011-05-29 Thread Jesse Brandeburg
You have to overrun the fifo on the hardware to see rx_dropped error from hardware. Currently your cpu is fast enough to keep up with the packet load. On Wed, May 25, 2011 at 7:32 PM, Filo FeFi wrote: > Ah! > > I've been looking for it in kernel version 2.6.18 which doesn't seem > to have the fu

Re: [E1000-devel] [PATCH] e1000: Allow the driver to be used on PA RISC C8000 workstation

2011-03-02 Thread Jesse Brandeburg
On Mon, Feb 28, 2011 at 5:40 AM, Guy Martin wrote: > > Hi Jeff, > > Any luck getting this into mainline ? Hi Guy, sorry for the delay, We haven't been able to get our contacts in HP to give us a decent response so far, we are following up with them to see whats up. We have not lost the patch an

Re: [E1000-devel] e1000: fix Tx hangs by disabling 64-bit DMA

2011-02-24 Thread Jesse Brandeburg
RxDescriptors:Number of receive descriptors (array of int) > > parm: Speed:Speed setting (array of int) > > parm: Duplex:Duplex setting (array of int) > > parm: AutoNeg:Advertised auto-negotiation setting (array of int) > > parm: FlowControl:Flow Control setting (arra

Re: [E1000-devel] 82754L spontaneous freeze networking woes continue in 2.6.37

2011-01-31 Thread Jesse Brandeburg
On 1/31/2011 4:06 PM, Allan, Bruce W wrote: >> -Original Message- >> From: Nix [mailto:n...@esperi.org.uk] >> Sent: Monday, January 31, 2011 3:31 PM >> To: Allan, Bruce W >> Cc: e1000-devel@lists.sourceforge.net >> Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes >> con

Re: [E1000-devel] NAPI in e1000e

2010-11-10 Thread Jesse Brandeburg
2010/11/1 xiaolin : > In e1000 driver, there is ew32(IMC, ~0) in the function of e1000_intr before > scheduling adapter->napi. > > However, there is no such kind operation in e1000e. > > My question is whether NIC hardware irq is disabled during the NAPI/ksoftirqd > processing? yes, it is disabl

Re: [E1000-devel] tx unit hang fc11

2010-10-23 Thread Jesse Brandeburg
On Fri, Oct 22, 2010 at 6:17 PM, wrote: > Quoting "Brandeburg, Jesse" : > >> >> >> On Thu, 21 Oct 2010, j...@destar.net wrote: >> >>> I am still having this issue but it seems to only be on x86_64. I used >>> a Knoppix disk to boot with and the card worked with no issues using a >>> 32bit kernel.

Re: [E1000-devel] [PATCH] e1000e: Intel 82571EB: Don't wait for MNG cycle on unmanaged chips

2010-08-30 Thread Jesse Brandeburg
On Fri, Aug 27, 2010 at 12:10 PM, Kyle Moffett wrote: > The Intel 82571EB chipset can be used in an unmanaged configuration as a > fast dual-port Gig-E controller.  Unfortunately a board constructed that > way would fail to correctly come up because the driver polls for the > completion of a manag

Re: [E1000-devel] bridge not functional with 10Gbe Intel 82599EB and recent kernels

2010-05-28 Thread Jesse Brandeburg
On Fri, May 28, 2010 at 11:30 AM, Jean-François Landry wrote: > Hello, we are attempting to build a 10 gigabit transparent bridging > firewall on Linux using an Intel X520-DA2 NIC and the bridge will simply > not pass any traffic when using the two 10Gbe interfaces on a recent > kernel. > > We are

Re: [E1000-devel] carrier detection issues at 10GB on XAUI with ixgbe driver on 2.6.27 x86 board

2010-05-18 Thread Jesse Brandeburg
lane sync status), and > finally 100ms later we lose signal detect on 3 of the 4 lanes. Does the link eventually come up? We may need to get an eeprom dump from the 82599 part you're working on as well. ethtool -e ethX should suffice. -- Jesse Brandeburg This email sent via Evolution,

Re: [E1000-devel] Missing VLAN Header

2010-03-22 Thread Jesse Brandeburg
On Mon, Mar 22, 2010 at 7:57 AM, Andreas Grau wrote: > Hi, > > We are currently experimenting with vlan on a 10GE i82599 nic. Linux 2.6.18 > with ixgbe version 2.0.62.4-NAPI is used on top of XEN 3.1.2. > > For the experiments we are using the following scenario: > >  -    ---    

Re: [E1000-devel] Intel 2598EB 10-Gigabit AT dropped rx packet

2010-03-19 Thread Jesse Brandeburg
t;>>>>> rx_queue_5_bytes: 1452 > >>>>>>>> rx_queue_6_packets: 7 > >>>>>>>> rx_queue_6_bytes: 726 > >>>>>>>>

Re: [E1000-devel] recent e100 fixes cause kernel panic?

2010-03-19 Thread Jesse Brandeburg
eport of this issue I have heard so far, so something must be a little unique to your system or workload such that the driver works mostly. I'm looking more closely into the panic trace now, maybe I can figure it out from there. -- Jesse Brandeburg This email sent via Evolution, powered by

Re: [E1000-devel] e1000_clean_tx_irq: Detected Tx Unit Hang

2010-03-04 Thread Jesse Brandeburg
On Thu, Mar 4, 2010 at 3:19 AM, Metal Thrashing Mad wrote: > Just read the mail from Nikita, about fixeep-82573-dspd.sh. I didn't see that mail. That script is only for 82573. > Running the script returns - > No appropriate hardware found for this fixup. > > Knowing full well that doing the fol

Re: [E1000-devel] e1000_clean_tx_irq: Detected Tx Unit Hang

2010-03-03 Thread Jesse Brandeburg
On Mon, Mar 1, 2010 at 3:37 AM, Thrash Dude wrote: > Seems to be a rather common issue with the e1000 module. I searched the > archives back to 2005. Plenty of reports, no solutions. There are some solutions, one of which is to try loading the driver with TxDescriptorStep=4 TxDescriptors=1024 >

Re: [E1000-devel] New thread: page allocation failure with E1000 (seems to be reproducible)

2010-03-01 Thread Jesse Brandeburg
in the future please copy net...@vger.kernel.org on networking issues. On Mon, Mar 1, 2010 at 9:34 AM, Richard Hartmann wrote: > Hi Jesse, > >> the memory allocation (order:0), while unexpected, are not fatal, and >> the e1000 driver is written to handle the failures during allocation. >> >> Does

Re: [E1000-devel] New thread: page allocation failure with E1000 (seems to be reproducible)

2010-02-26 Thread Jesse Brandeburg
Hi Richard, On Fri, Feb 26, 2010 at 2:42 AM, Richard Hartmann wrote: > Hi all, > > this is a re-send of my original email to e1000-de...@lists.sf.net. It > includes all information at once and is sent to LKML as well. I am > CC'ing Andrew Pochinsky because http://lkml.org/lkml/2008/6/10/3 is > re

Re: [E1000-devel] igb 2.1.1 increased ping times on 82575EB

2010-02-22 Thread Jesse Brandeburg
On Mon, Feb 22, 2010 at 10:32 AM, Alexander Duyck wrote: > either the CPU or PCIe link.  One thing you may want to do is make sure > that ASPM power states and CPU Cx states are disabled in the BIOS while > conducting your testing. FYI with 2.6.32 you can boot with kernel options appended: pcie_a

Re: [E1000-devel] e1000e-1.1.2 Compile errors with 2.4.37 and gcc 2.95.3

2010-02-09 Thread Jesse Brandeburg
removed netdev, On Tue, Feb 9, 2010 at 3:21 AM, Ben Hutchings wrote: > On Tue, 2010-02-09 at 10:58 +0100, Marco Schwarz wrote: >> Hi, >> >> I get the following output when trying to compile e1000e-1.1.2 with Linux >> Kernel 2.4.37 and gcc 2.95.3 (e1000-8.0.16 compiles fine): > [...] > > netdev o

Re: [E1000-devel] 2.6.33-rc5: (e1000): transmit queue 0 timed out

2010-01-26 Thread Jesse Brandeburg
I also just noticed something else. On Sat, Jan 23, 2010 at 12:04 PM, Alexander Beregalov wrote: >>> Pid: 5, comm: events/0 Tainted: G        W  2.6.33-rc5 #1 >>> NF7-S/NF7,NF7-V (nVidia-nForce2)/ >>> EIP: 0060:[] EFLAGS: 00010282 CPU: 0 >>> EIP is at put_page+0x11/0x120 >>> EAX: 2e8ca4f3 EBX: 2e

Re: [E1000-devel] [Bugme-new] [Bug 14748] New: e1000e NIC not working after reboot

2010-01-26 Thread Jesse Brandeburg
On Mon, Dec 7, 2009 at 2:01 PM, Brandeburg, Jesse wrote: > On Mon, 7 Dec 2009, Andrew Morton wrote: >> > When I power up my system the NIC is working properly. >> > After every reboot the NIC is not working. I mean the eth0 is created, but >> > neither dhcpcd gets IP nor static setup helps > > We

Re: [E1000-devel] Ixgbe and VLAN filtering

2010-01-26 Thread Jesse Brandeburg
he Linux (in the > ixgbe driver or in the Linux network stack)? > > Thanks, > Gyorgy Szaniszlo > Ericsson Hungary Ltd. > > > > > > Yes, when using vconfig, the ixgbe driver is given the vlan > information and sets the appropriate bits in the HW to do the filtering in > the hardware. >

Re: [E1000-devel] 82567V-3 PXE boot

2010-01-11 Thread Jesse Brandeburg
boot? Thanks!! > > BTW, e1000e.ko is made from . Did you force the module to be loaded with --preload in the initrd creation? in redhat the mkinitrd has a --preload=e1000e option to force a module to be loaded out of the initrd. Also may need --with=e1000e -- Jesse Brandeburg This

Re: [E1000-devel] Excessive frame dropping on 82574L

2009-12-22 Thread Jesse Brandeburg
rate using ethtool -C ethX rx-usecs 125 (8000 interrupts per second) because you're not doing a latency sensitive workload Please also provide /proc/interrupts and ethtool -e ethX, and if you are feeling gung-ho, the output of the ethregs utility available at sourceforge (you'll have to b

Re: [E1000-devel] LRO botch with 82598EB 2.0.44.14-NAPI

2009-11-12 Thread Jesse Brandeburg
gt; 39426, win 382, length 0 > 17:21:52.484305 IP (tos 0x0, ttl 64, id 56747, offset 0, flags [DF], proto > TCP (6), length 1500) > nh1-eth2.55716 > nh2-eth2.44115: Flags [.], ack 39426, win 382, length > 1460 > 17:21:52.4843

  1   2   >