[e1000-devel] e1000e possible software bug (?)

Hi all, I am not sure if I'm overstepping boundaries to address this mailing list with this issue, but I have a hard time figuring out where the heart of my problem lies, and if anyone with some more experience on the topic could nudge me in the right direction, that would me more than greatly

[E1000-devel] e1000e-3.8.4 82574L udp drop data

device is 82574. install e1e.ko in imx6,create new net device eth2 but i used perf test net device eth2,has drop data and kernel not error perf info window server: iperf.exe -s -u linux client: root@myimx6ek200:~# iperf -u -c 192.168.32.38 -b 100M -d -i 1 -l 1470 ---

Re: [E1000-devel] e1000e-x.x.x.x driver update

On Thu, 2019-07-11 at 14:24 +0300, Joseph Lifshitz wrote: > Hi, > I'm an programmer working at motorola solutions ltd. > We have been working on ADLINK cPCI-6525 board and used e1000e-1.5.1 > driver > with Ubuntu 12.04 and it worked fine. Wow, super old driver with a very old OS. > We would like

[E1000-devel] e1000e-x.x.x.x driver update

Hi, I'm an programmer working at motorola solutions ltd. We have been working on ADLINK cPCI-6525 board and used e1000e-1.5.1 driver with Ubuntu 12.04 and it worked fine. We would like to move to ADLINK cPCI-6636 board which uses the Intel connection ehternet I219LM. Now the driver does not work. W

Re: [E1000-devel] [e1000e REGRESSION BISECTED] Detected Hardware Unit Hang with 5.0.7

On 16.04.2019 20:12, Alexander Duyck wrote: On Mon, Apr 15, 2019 at 11:22 AM Joseph Yasi wrote: Hello, I reported a regression that happened after upgrading from 5.0.6 to 5.0.7: https://bugzilla.kernel.org/show_bug.cgi?id=203175 This is fixed by reverting commit 7f0a3a436e88a71b96694c029f0

Re: [E1000-devel] [e1000e REGRESSION BISECTED] Detected Hardware Unit Hang with 5.0.7

On Tue, Apr 16, 2019, 1:12 PM Alexander Duyck wrote: > On Mon, Apr 15, 2019 at 11:22 AM Joseph Yasi wrote: > > > > Hello, > > I reported a regression that happened after upgrading from 5.0.6 to > 5.0.7: > > https://bugzilla.kernel.org/show_bug.cgi?id=203175 > > > > This is fixed by reverting com

Re: [E1000-devel] [e1000e REGRESSION BISECTED] Detected Hardware Unit Hang with 5.0.7

On Mon, Apr 15, 2019 at 11:22 AM Joseph Yasi wrote: > > Hello, > I reported a regression that happened after upgrading from 5.0.6 to 5.0.7: > https://bugzilla.kernel.org/show_bug.cgi?id=203175 > > This is fixed by reverting commit > 7f0a3a436e88a71b96694c029f01a9a8eade3d5d e1000e: fix cyclic reset

[E1000-devel] [e1000e REGRESSION BISECTED] Detected Hardware Unit Hang with 5.0.7

Hello, I reported a regression that happened after upgrading from 5.0.6 to 5.0.7: https://bugzilla.kernel.org/show_bug.cgi?id=203175 This is fixed by reverting commit 7f0a3a436e88a71b96694c029f01a9a8eade3d5d e1000e: fix cyclic resets at link up with active tx. A few others have reported the same h

Re: [E1000-devel] e1000e hardware unit hangs

On 1/24/2018 20:41, Ben Greear wrote: On 01/24/2018 10:38 AM, Denys Fedoryshchenko wrote: On 2018-01-24 20:31, Ben Greear wrote: On 01/24/2018 08:34 AM, Neftin, Sasha wrote: On 1/24/2018 18:11, Alexander Duyck wrote: On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: Hello, Anyone have any

Re: [E1000-devel] e1000e hardware unit hangs

On 2018-01-24 20:31, Ben Greear wrote: On 01/24/2018 08:34 AM, Neftin, Sasha wrote: On 1/24/2018 18:11, Alexander Duyck wrote: On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: Hello, Anyone have any more suggestions for making e1000e work better? This is from a 4.9.65+ kernel, with thes

Re: [E1000-devel] e1000e hardware unit hangs

On 01/24/2018 08:34 AM, Neftin, Sasha wrote: On 1/24/2018 18:11, Alexander Duyck wrote: On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: Hello, Anyone have any more suggestions for making e1000e work better? This is from a 4.9.65+ kernel, with these additional e1000e patches applied: e100

Re: [E1000-devel] e1000e hardware unit hangs

On 01/24/2018 10:38 AM, Denys Fedoryshchenko wrote: On 2018-01-24 20:31, Ben Greear wrote: On 01/24/2018 08:34 AM, Neftin, Sasha wrote: On 1/24/2018 18:11, Alexander Duyck wrote: On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: Hello, Anyone have any more suggestions for making e1000e wor

Re: [E1000-devel] e1000e hardware unit hangs

On 1/24/2018 18:11, Alexander Duyck wrote: On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: Hello, Anyone have any more suggestions for making e1000e work better? This is from a 4.9.65+ kernel, with these additional e1000e patches applied: e1000e: Fix error path in link detection e1000e: F

Re: [E1000-devel] e1000e hardware unit hangs

On Tue, Jan 23, 2018 at 3:46 PM, Ben Greear wrote: > Hello, > > Anyone have any more suggestions for making e1000e work better? This is > from a 4.9.65+ kernel, > with these additional e1000e patches applied: > > e1000e: Fix error path in link detection > e1000e: Fix wrong comment related to link

[E1000-devel] e1000e 82574L down issue.

Hi, Found one issue , 82574L work with linux kernel 4.9/4.12/4.13 . when Ddos come then down ,up aways I had upgrade driver to 3.3.5.10-NAPI ,but same issue . But no down with kernel 3.18/4.4 , or 3.3.5.10 no-napi. ---

[E1000-devel] e1000e: eth0 NIC Link is Down

Hello, Hoping someone can help. Recently upgraded a server running Xen from 3.18.44-20.el6.x86_64 to 4.9.39-29.el6.x86_64 (did a yum update so other packages would have been updated to). Since rebooting, we randomly get "e1000e: eth0 NIC Link is Down", this happens for only a second, but since w

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

.@intel.com> >  > (503) 712-4565 >  > >  > >  > -Original Message- >  > From: Jarod Wilson [mailto:ja...@redhat.com <mailto:ja...@redhat.com>] >  > Sent: Friday, May 20, 2016 10:01 AM >  > To: Spencer Hall <mailto:dragon_bra...@yahoo.com>> >  >

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

o:todd.fujin...@intel.com> > > (503) 712-4565 > > > > > > -Original Message- > > From: Jarod Wilson [mailto:ja...@redhat.com <mailto:ja...@redhat.com>] > > Sent: Friday, May 20, 2016 10:01 AM > > To: Spencer Hall <mailto:drago

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

t; -Original Message- > From: Jarod Wilson [mailto:ja...@redhat.com] > Sent: Friday, May 20, 2016 10:01 AM > To: Spencer Hall > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] e1000e Compile error on Red Hat 6.8 > >> On Fri, May 20, 2016 at 05:34:22

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

ion (ND) > Intel Corporation > todd.fujin...@intel.com > (503) 712-4565 > > > -Original Message- > From: Jarod Wilson [mailto:ja...@redhat.com] > Sent: Friday, May 20, 2016 10:01 AM > To: Spencer Hall > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

m > (503) 712-4565 > > > -Original Message- > From: Jarod Wilson [mailto:ja...@redhat.com] > Sent: Friday, May 20, 2016 10:01 AM > To: Spencer Hall > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] e1000e Compile error on Red Hat 6.8 > >

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

a Software Application Engineer Networking Division (ND) Intel Corporation todd.fujin...@intel.com (503) 712-4565 -Original Message- From: Jarod Wilson [mailto:ja...@redhat.com] Sent: Friday, May 20, 2016 10:01 AM To: Spencer Hall Cc: e1000-devel@lists.sourceforge.net Subject: Re: [E

Re: [E1000-devel] e1000e Compile error on Red Hat 6.8

On Fri, May 20, 2016 at 05:34:22AM +, Spencer Hall wrote: > I have been compiling the e1000e module for all the Red Hat 6 kernels. With > the latest release of Red Hat 6.8 with the new kernel 2.6.32-642, when trying > to build the e1000e module it fails with the following error: > implicit d

[E1000-devel] e1000e Compile error on Red Hat 6.8

I have been compiling the e1000e module for all the Red Hat 6 kernels. With the latest release of Red Hat 6.8 with the new kernel 2.6.32-642, when trying to build the e1000e module it fails with the following error: implicit declaration of function 'vlan_tx_tag_present' A similar problem showed

[E1000-devel] e1000e - kernel 4.4.6 - e1000_power_down_phy_copper_80003es2lan hogging CPU

Hi, after upgrading to 4.4.x kernel, I noticed performance dropped considerably. while investigating using perf, I noticed e1000_power_down_phy_copper_80003es2lan seems to be suspiciously active: samples pcnt functionDSO ___ _ _

[E1000-devel] e1000e: initialization breaks IPMI support on 80003ES2LAN

Hi, We have Intel 80003ES2LAN nics on SGI Altix XE310 servers (SuperMicro Baseboard, with product name X7DGT). On those machines, one of the NIC port is bridged internally with the BMC. It seems that during the e1000e driver initialization (at boot time), the NIC is reset, which causes the BMC to

Re: [E1000-devel] [e1000e] Mismatch between coalesce settings from ethtool and effective settings?

Hi Raanan > The only way to query coalesce options is via the "ethtool -c" command. > I don't know if it helps you, but are you familiar with the driver param: > InterruptThrottleRate. > Run: "modinfo e1000e" command, and you can also look at the param.c file. Thanks for the hint. I have used th

Re: [E1000-devel] [e1000e] Mismatch between coalesce settings from ethtool and effective settings?

an -Original Message- From: Christoph Mathys [mailto:erase...@gmail.com] Sent: Tuesday, October 27, 2015 17:00 To: e1000-devel@lists.sourceforge.net Subject: [E1000-devel] [e1000e] Mismatch between coalesce settings from ethtool and effective settings? Hi there Is there some way to read

[E1000-devel] [e1000e] Mismatch between coalesce settings from ethtool and effective settings?

Hi there Is there some way to read the actual values for the coalesce options back from the NIC? To be specific, I'm interested in the value of ITR on a 82574L chip. I suspect it does not match with the value that I get from "ethtool -c". Reading back from userspace, without compiling a lot of stu

Re: [E1000-devel] e1000e 3.1.0.2 divide error

> On May 11, 2015, at 2:03 PM, Keller, Jacob E wrote: > > Hi, > > On Mon, 2015-05-11 at 10:49 +0800, kendo wrote: >> In the e1000e_cyclecounter_read function, if incvalue is 0, causes a divide >> error.Need to add a check? >> >> >>incvalue = er32(TIMINCA) & E1000_TIMINCA_INCV

Re: [E1000-devel] e1000e 3.1.0.2 divide error

Hi, On Mon, 2015-05-11 at 10:49 +0800, kendo wrote: > In the e1000e_cyclecounter_read function, if incvalue is 0, causes a divide > error.Need to add a check? > > > incvalue = er32(TIMINCA) & E1000_TIMINCA_INCVALUE_MASK; > //2015-05-11.fix by kendo >

[E1000-devel] e1000e 3.1.0.2 divide error

In the e1000e_cyclecounter_read function, if incvalue is 0, causes a divide error.Need to add a check? incvalue = er32(TIMINCA) & E1000_TIMINCA_INCVALUE_MASK; //2015-05-11.fix by kendo if(incvalue){ for (i = 0; i < E1000_MAX

Re: [E1000-devel] e1000e of linux kernel 3.19.3 and 4.0.0-rc7 got kernel oops in vmware ws 11

OK, the attached file is not accepted in this mailing list. Therefore here you are for booting with linux kernel 4.0.0-04rc7-generic: == [1.643414] Modules linked in: psmouse mptsas(+) e1000e(+) ptp pps_core mptscsih mptbase scsi_transport_sas e1000

[E1000-devel] e1000e of linux kernel 3.19.3 and 4.0.0-rc7 got kernel oops in vmware ws 11

Dear e1000 driver maintainer, I am using e1000e driver for VMWare workstation virtual machine. It's VMware Workstation 11.1.0 for Linux with MS Windows 8.1 client, therefore the chipset for ethernet is "e1000e" shown in the *.vmx file: ethernet1.virtualDev = "e1000e" I installed Ubuntu 15.04 de

Re: [E1000-devel] e1000e

@gmail.com] Sent: Tuesday, November 04, 2014 1:15 AM To: e1000-devel@lists.sourceforge.net Subject: [E1000-devel] e1000e can anybody tell me these codes means? "drivers/net/e1000e/phy.c" /* AHT reset limit to 1 */ e1e_wphy(hw, 0x1F76, 0xC0FF); /* Set AHT master delay to 127 msec */

[E1000-devel] e1000e and ixgbe drivers do not use ioatdma

Hi, I am testing crystal beach dma on x86_64 Intel xeon board. I want to test both e1000e and ixgbe drivers with crystal beach dma. Kernel I am using is 2.6.32.431 I have patched ioatdma driver(pci.c and hw.h files ) for crystal beach dma. Now I am facing issue that both drivers do not use thi

Re: [E1000-devel] e1000e

why 127 msec？ can i reset it？ how can i reset it？ 2014-11-04 17:14 GMT+08:00 SUN Catalpa : > can anybody tell me these codes means? > "drivers/net/e1000e/phy.c" > > /* AHT reset limit to 1 */ > e1e_wphy(hw, 0x1F76, 0xC0FF); > /* Set AHT master delay to 127 msec */ > e1e_wphy(hw, 0x1F77, 0x1DEC

[E1000-devel] e1000e

can anybody tell me these codes means? "drivers/net/e1000e/phy.c" /* AHT reset limit to 1 */ e1e_wphy(hw, 0x1F76, 0xC0FF); /* Set AHT master delay to 127 msec */ e1e_wphy(hw, 0x1F77, 0x1DEC); /* Set scan bits for AHT */ e1e_wphy(hw, 0x1F78, 0xF9EF); /* Set AHT Preset bits */ e1e_wphy(hw, 0x

Re: [E1000-devel] "e1000e: probe of 0000:00:19.0 failed with error -3" during cold boot

Sorry for the 2nd mail. I was not sure if my contact info was complete within the header of my previous message, and the info in the signature got cropped felix.a.sala...@gmail.com Thanks, - *Félix Salazar* felix.a.sala...@gmail.com - On Mon, Aug

[E1000-devel] "e1000e: probe of 0000:00:19.0 failed with error -3" during cold boot

Hello guys, Since my last general update (kernel and all packages), I started having an issue with my network interface. The network is down after a cold boot, and only a reboot will fix it. This issue is somewhat similar to the one reported in this thread

[E1000-devel] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:

Hi guys, again a hardware hang, this time on my workstation with 3.15-rc6: It happened during a suspend-to-disk attempt doing: echo 3 > /proc/sys/vm/drop_caches echo "shutdown" > /sys/power/disk echo "disk" > /sys/power/state The box came right back up and dmesg said: [ 294.132711] hib.sh (22

Re: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

:00 AM > To: e1000-devel@lists.sourceforge.net > Cc: net...@vger.kernel.org; lkml > Subject: [E1000-devel] e1000e :00:19.0 eth0: Hardware Error > > Hi guys, > > I started getting those sporadic > > [133178.640890] e1000e :00:19.0 eth0: Hardware Error > [13

Re: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

Hi guys, let me answer to all of you here: On Thu, Apr 10, 2014 at 03:45:41PM +, Ertman, DavidX M wrote: > Could you also provide some information about the configuration > of the system when this happens? AFAIR, this happens when I stick the network cable in. I'll pay attention to the exact

Re: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

> -Original Message- > From: Fujinaka, Todd [mailto:todd.fujin...@intel.com] > Sent: Thursday, April 10, 2014 7:59 AM > To: Borislav Petkov; e1000-devel@lists.sourceforge.net > Cc: net...@vger.kernel.org; lkml > Subject: Re: [E1000-devel] e1000e :00:19.0 eth0: Hard

Re: [E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

etkov [mailto:b...@alien8.de] Sent: Thursday, April 10, 2014 5:00 AM To: e1000-devel@lists.sourceforge.net Cc: net...@vger.kernel.org; lkml Subject: [E1000-devel] e1000e :00:19.0 eth0: Hardware Error Hi guys, I started getting those sporadic [133178.640890] e1000e :00:19.0 eth0: Hardware Error

[E1000-devel] e1000e 0000:00:19.0 eth0: Hardware Error

Hi guys, I started getting those sporadic [133178.640890] e1000e :00:19.0 eth0: Hardware Error [133179.293148] e1000e :00:19.0: irq 45 for MSI/MSI-X [133179.394226] e1000e :00:19.0: irq 45 for MSI/MSI-X [133179.397200] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [133181.338258]

[E1000-devel] e1000e: skb_over_panic on skb_put at e1000_clean_rx_irq

Hello all, Linux (stable) 3.10.27 built from the git sources crashes right at boot with a "skb_over_panic" error. This only happens during boot (probably related to the sysvinit sequence), it does not happen when I modprobe the driver. It seems to be some race condition because sometimes I do not

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On Fri, 2013-12-20 at 17:20 +, Fujinaka, Todd wrote: > I'm having a bit of trouble following this. Is there a bug opened on > sourceforge for this? If not, can I request that, as well as an "lspci -vvv" > and full dmesg and /var/log/message output (as attachments to the bug, not > inline)?

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On Wed, 2013-12-18 at 11:48 +, Morten Østergaard wrote: > On Wed, 2013-12-18 at 14:14 +0400, Eugene Shatokhin wrote: > > Could you also add a call to dump_stack() in your patch so as to get the > > call trace in the system log when that strange event happens, not only > > the warning? > I add

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On Wed, 2013-12-18 at 16:58 +0400, Eugene Shatokhin wrote: > On 12/18/2013 03:48 PM, Morten Østergaard wrote: > > Maybe this can help? > > Well, at least, it shows that the suspicious event happens exactly at > the same place as the first time as shown in that picture you posted > before. Not mu

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On 12/18/2013 03:48 PM, Morten Østergaard wrote: > Maybe this can help? Well, at least, it shows that the suspicious event happens exactly at the same place as the first time as shown in that picture you posted before. Not much, but still. I suppose, the patch I sent is not applied there? Also

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On Wed, 2013-12-18 at 14:14 +0400, Eugene Shatokhin wrote: > Interesting. > > Could you also add a call to dump_stack() in your patch so as to get the > call trace in the system log when that strange event happens, not only > the warning? > > It may help to see what actually happens. > Hi aga

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On 12/18/2013 01:21 PM, Morten Østergaard wrote: > Furthermore I have tested your patch, and unfortunately it doesn't seem > have any impact on the issue experienced, I still end up in the same > situation where skb->tail > skb->end, which either triggers BUG() or > generates the warning above, if

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On Mon, 2013-12-16 at 18:54 +0400, Eugene Shatokhin wrote: > On 12/10/2013 02:42 PM, Morten Østergaard wrote: > > Hi > > > > We are experiencing a recurrent Linux kernel panic with the e1000e > > driver on a Kontron mSP1 COM Express "mini" CPU module and other similar > > COM Express modules. > > >

Re: [E1000-devel] e1000e: git commit da1e204 introduced a bug with the Intel I217-V

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So I did indeed forget to do the final bisect, however, it turns the da1e204 commit is still the culprit. After some testing, I've determined the second part of the patch, is guilty for causing this faulty behavior. @@ -4034,6 +4027,12 @@ void e1000

Re: [E1000-devel] e1000e: git commit da1e204 introduced a bug with the Intel I217-V

Bruce, thanks for pointing me in the right direction. I think I may have forgot to do the final git bisect. I will do this as soon as I get home tonight. Sorry, Matthew On 2013-12-16 12:37, Allan, Bruce W wrote: > Since I am not currently focused on e1000e, adding the appropriate > mailing list

Re: [E1000-devel] e1000e: git commit da1e204 introduced a bug with the Intel I217-V

Since I am not currently focused on e1000e, adding the appropriate mailing list, e1000-de...@lists.sf.net. > -Original Message- > From: Matthew Gyurgyik [mailto:matt...@pyther.net] > Sent: Sunday, December 15, 2013 1:28 PM > To: Allan, Bruce W > Cc: Brown, Aaron F; Kirsher, Jeffrey T > Su

Re: [E1000-devel] e1000e: build failure with 2.5.4 and suspend/resume

into the queue for testing and submission to the net-next tree. Dave Ertman > -Original Message- > From: Holger Eitzenberger [mailto:hol...@eitzenberger.org] > Sent: Monday, December 16, 2013 1:04 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] e1000e

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

On 12/10/2013 02:42 PM, Morten Østergaard wrote: > Hi > > We are experiencing a recurrent Linux kernel panic with the e1000e > driver on a Kontron mSP1 COM Express "mini" CPU module and other similar > COM Express modules. > > Unfortunately I am currently not able to save a kernel dump on the > mac

[E1000-devel] e1000e: build failure with 2.5.4 and suspend/resume

Hi, I see a build failure when building against kernel v3.8 on a 32bit system: src/netdev.c:7948: error: 'e1000e_pm_suspend' undeclared here (not in a function) src/netdev.c:7949: error: 'e1000e_pm_resume' undeclared here (not in a function) And I see that the definition of e1000e_pm_suspend

Re: [E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

Hi, On 12/10/2013 02:42 PM, Morten Østergaard wrote: > Hi > > We are experiencing a recurrent Linux kernel panic with the e1000e > driver on a Kontron mSP1 COM Express "mini" CPU module and other similar > COM Express modules. > > Unfortunately I am currently not able to save a kernel dump on the

[E1000-devel] e1000e Linux kernel panic, e1000_clean_rx_irq, e1000_poll

Hi We are experiencing a recurrent Linux kernel panic with the e1000e driver on a Kontron mSP1 COM Express "mini" CPU module and other similar COM Express modules. Unfortunately I am currently not able to save a kernel dump on the machines, but please see the attached jpeg image. The problem occ

Re: [E1000-devel] e1000e, kernel 3.12.3, packetloss and periodic Detected Hardware Unit Hang

On Sat, 2013-12-07 at 08:32 +0200, Denys Fedoryshchenko wrote: > Hi > > On one of clients got new hardware and i started to get periodic > watchdog/hang messages in dmesg and packetloss on e1000e driver, while > load on device is relatively low. > > Here is lspci, ifconfig, ethtool and dmesg in

[E1000-devel] e1000e, kernel 3.12.3, packetloss and periodic Detected Hardware Unit Hang

Hi On one of clients got new hardware and i started to get periodic watchdog/hang messages in dmesg and packetloss on e1000e driver, while load on device is relatively low. Here is lspci, ifconfig, ethtool and dmesg information 00:19.0 Ethernet controller: Intel Corporation Device 1503 (rev 0

Re: [E1000-devel] e1000e: build failure when building without BQL

> > netdev_reset_queue(adapter->netdev); > > > > As netdev_reset_queue() has been added for BQL specifically I have now > > solved that by #ifdef'ing this call. See attached patchlet. > The correct fix would be to remove the #ifdef wrapping around the declaration > of adapter (as should of

Re: [E1000-devel] e1000e: build failure when building without BQL

> -Original Message- > From: Holger Eitzenberger [mailto:hol...@eitzenberger.org] > Sent: Thursday, December 05, 2013 2:04 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] e1000e: build failure when building without BQL > > Hi, > > I am g

Re: [E1000-devel] 'e1000e: fix overrun of PHY RAR array' breaks my network

Hey Dave, Thanks for your reply. As for your questions, >Bare metal vs. virtual system Bare metal > Kernel config attached to this mail > Are you using LAA MAC addresses No. > How many addresses are you configuring to this device Just one. > Are there any messages/warnings generated in your syste

[E1000-devel] e1000e: build failure when building without BQL

Hi, I am getting a build failure when buidling v2.5.4 without BQL: src/netdev.c: In function 'e1000_clean_tx_ring': src/netdev.c:2607: error: 'adapter' undeclared (first use in this function) src/netdev.c:2607: error: (Each undeclared identifier is reported only once) src/netdev.c:2607: error

Re: [E1000-devel] 'e1000e: fix overrun of PHY RAR array' breaks my network

Could you please provide some further information on your system setup? Bare metal vs. virtual system Kernel config Are you using LAA MAC addresses How many addresses are you configuring to this device Are there any messages/warnings generated in your system log Anything else that might be releva

[E1000-devel] 'e1000e: fix overrun of PHY RAR array' breaks my network

Hi, The commit 'e1000e: fix overrun of PHY RAR array' (c3a0dce35af02846bdaa1df437493e2fd547ec2f) breaks my Ethernet connectivity. By that I mean that my NIC doesn't get assigned an IP address via DHCP and ethtool reports the link down. Reverting the mentioned patch restores network connectivity.

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

82567LM does not support EEE > -Original Message- > From: Ertman, DavidX M [mailto:davidx.m.ert...@intel.com] > Sent: Monday, October 21, 2013 10:21 AM > To: Petar Bogdanovic; e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] e1000e, link negotiation problem

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

> -Original Message- > From: Petar Bogdanovic [mailto:pe...@smokva.net] > Sent: Saturday, October 19, 2013 4:51 PM > To: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM) > > On Sat, Oct 19, 2013 at 11:27:0

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sun, Oct 20, 2013 at 12:28:48AM +, Waskiewicz Jr, Peter P wrote: > > That question I will defer to Bruce Allan, who's the maintainer for the > e1000e driver. I did the initial SmartSpeed design and implementation > for 10GbE devices, so Bruce would be the best resource for how it's > integ

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sun, 2013-10-20 at 01:50 +0200, Petar Bogdanovic wrote: > On Sat, Oct 19, 2013 at 11:27:02PM +, Waskiewicz Jr, Peter P wrote: > > > > Disabling SmartSpeed will cause the link negotiation to rely on the > > physical layer to negotiate the link properties. This isn't necessarily > > a bad th

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sat, Oct 19, 2013 at 11:27:02PM +, Waskiewicz Jr, Peter P wrote: > > Disabling SmartSpeed will cause the link negotiation to rely on the > physical layer to negotiate the link properties. This isn't necessarily > a bad thing, because link negotiation on 1GbE devices should be solid. > > H

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sun, 2013-10-20 at 01:15 +0200, Petar Bogdanovic wrote: > On Sat, Oct 19, 2013 at 10:52:07PM +, Waskiewicz Jr, Peter P wrote: > > > > The quick history behind it is we implemented it on 10GbE first, where > > no spec existed for auto-negotiation for 10GbE-1GbE with fiber. We had > > optics

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sat, Oct 19, 2013 at 10:52:07PM +, Waskiewicz Jr, Peter P wrote: > > The quick history behind it is we implemented it on 10GbE first, where > no spec existed for auto-negotiation for 10GbE-1GbE with fiber. We had > optics modules that could do either 10 or 1 GbE, but no link-layer > mechan

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sun, 2013-10-20 at 00:32 +0200, Petar Bogdanovic wrote: > On Sat, Oct 19, 2013 at 10:34:18PM +0200, Petar Bogdanovic wrote: > > > > I managed to build and run the most recent e1000e kernel module (and > > experimented with its module options) but it didn't make any difference. > > I forgot the

Re: [E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

On Sat, Oct 19, 2013 at 10:34:18PM +0200, Petar Bogdanovic wrote: > > I managed to build and run the most recent e1000e kernel module (and > experimented with its module options) but it didn't make any difference. I forgot the crucial part (the testing above happened a while ago): "Link

[E1000-devel] e1000e, link negotiation problem (Intel 82567LM)

Hi, my Dell Latitude E4300 runs Linux 2.6.37 and whenever its onboard Intel 82567LM Gigabit controller is connected to a [1]Netgear GS108, it falls back to 100Mb/s after (what seems to be) negotiating for quite a while. I managed to build and run the most recent e1000e kernel module (and experime

Re: [E1000-devel] e1000e: HW Unit hang on 3.7.10+ kernel.

On 09/04/2013 07:56 AM, Ertman, DavidX M wrote: > There was recently a fix implemented for a hang issue that seems to be the > same thing you are experiencing. The hang was sporadic and hard to > reproduce, but specific bridging configurations were prone to causing the > hang to be more common

Re: [E1000-devel] e1000e: HW Unit hang on 3.7.10+ kernel.

> -Original Message- > From: Ben Greear [mailto:gree...@candelatech.com] > Sent: Tuesday, September 03, 2013 3:18 PM > To: e1000-devel list > Subject: [E1000-devel] e1000e: HW Unit hang on 3.7.10+ kernel. > > I'm helping another company debug some network issu

[E1000-devel] e1000e: HW Unit hang on 3.7.10+ kernel.

I'm helping another company debug some network issues. They are seeing a hang on a 3.7.10+ kernel. It only happens on a few systems, so the suspicion is that is really is a hardware/driver issue, but of course it could be something else. The kernel is patched with some hacks to the bridging code

Re: [E1000-devel] e1000e suspend-to-disk reboots box with 3.11-rc3+

> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Wednesday, July 31, 2013 1:41 PM > To: e1000-devel@lists.sourceforge.net > Cc: net...@vger.kernel.org; linux-ker...@vger.kernel.org > Subject: [E1000-devel] e1000e suspend-to-disk reboots

[E1000-devel] e1000e suspend-to-disk reboots box with 3.11-rc3+

Hi, I'm experiencing the strange observation that when I hibernate my x230 with Linus HEAD from today + tip/master (3.11-rc3+), the box doesn't remain off but reboots immediately. Since I have a similar bug where an e1000e box reboots when "Wake on LAN from S4/S5" is enabled in the BIOS (https://

[E1000-devel] e1000e NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out

Recently, I started experiencing what seems to be watchdog events with the e1000e driver due to a "transmit queue time out". Each time this occurs, the e1000e adapter resets a bunch of times. I was running the 3.4.4 kernel and don't recall this issue. Now I am running the 3.6.3 kernel and am exp

Re: [E1000-devel] e1000e + suspend, 3.9-rc2

Any ideas on this? On 07/05/2013 10:24 PM, Jiri Slaby wrote: > On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote: >> Jiri Slaby wrote: >>> On 04/15/2013 05:29 PM, Jiri Slaby wrote: On 03/29/2013 07:04 PM, Allan, Bruce W wrote: >> -Original Message- >> From: Jiri Slaby [mailt

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

Hi! > > 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 > > e1000e tries to generate an interrupt

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

(503) 712-4565 -Original Message- From: Jesse Brandeburg [mailto:jesse.brandeb...@intel.com] Sent: Tuesday, July 09, 2013 2:41 PM To: Pavel Machek Cc: e1000-devel@lists.sourceforge.net; Allan, Bruce W; Brandeburg, Jesse; Ronciak, John; net...@vger.kernel.org Subject: Re: [E1000-devel]

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

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] e1000e on thinkpad x60: interrupt problem

So are you saying the HW isn't generating an interrupt? Clearly it is as the driver is taking action on it. I went and looked at the first mail I saw (the one I first responded to) but maybe you are talking about another email that I (we) didn't get. I don't see any of what you point to in th

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

On Tue 2013-07-09 17:15:48, Waskiewicz Jr, Peter P wrote: > On Tue, 2013-07-09 at 19:02 +0200, Pavel Machek wrote: > > Hi! > > > > > Nothing appears to be wrong. If the system is seeing ping packets > > >at all means that device is generating interrupts and that they are > > >being processed. If

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

On Tue, 2013-07-09 at 19:02 +0200, Pavel Machek wrote: > Hi! > > > Nothing appears to be wrong. If the system is seeing ping packets > >at all means that device is generating interrupts and that they are > >being processed. If you are looking at performance then sharing > > No, that's not true.

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

Hi! > Nothing appears to be wrong. If the system is seeing ping packets >at all means that device is generating interrupts and that they are >being processed. If you are looking at performance then sharing No, that's not true. There is other interrupt load, and e1000e has big enough buffers; th

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

Nothing appears to be wrong. If the system is seeing ping packets at all means that device is generating interrupts and that they are being processed. If you are looking at performance then sharing interrupts is probably not a good idea. Since you are on a laptop it may not be easy to separat

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

Hi! I'm using 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller on thinkpad x60. Kernel is 3.10. # CONFIG_E100 is not set # CONFIG_E1000 is not set CONFIG_E1000E=y Interrupts are like this: pavel@amd:/data/l/linux-good$ cat /proc/interrupts CPU0

Re: [E1000-devel] e1000e + suspend, 3.9-rc2

On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote: > Jiri Slaby wrote: >> On 04/15/2013 05:29 PM, Jiri Slaby wrote: >>> On 03/29/2013 07:04 PM, Allan, Bruce W wrote: > -Original Message- > From: Jiri Slaby [mailto:jirisl...@gmail.com] On Behalf Of Jiri Slaby > Sent: Tuesday, M

[E1000-devel] e1000e + ICH8 GbE flash lock, kernel 3.9.6

Dear linux nics, Is the e1000e GbE flash sector write protect still necessary (e1000e_write_protect_nvm_ich8lan)? I had some issues with booting the Linux kernel and afterwards update the system BIOS after a warm reboot. The system BIOS update does three steps: 1. save GbE NVM sector via EEUPD

Re: [E1000-devel] e1000e + suspend, 3.9-rc2

On 06/12/2013 11:29 PM, Konstantin Khlebnikov wrote: > Jiri Slaby wrote: >>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2 >>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2 >>> pci_pm_suspend(): e1000_suspend+0x0/0x10 [e1000e] returns -2 >>> pci_pm_suspend(): e1000_sus

Re: [E1000-devel] e1000e + suspend, 3.9-rc2

Jiri Slaby wrote: > On 04/15/2013 05:29 PM, Jiri Slaby wrote: >> On 03/29/2013 07:04 PM, Allan, Bruce W wrote: -Original Message- From: Jiri Slaby [mailto:jirisl...@gmail.com] On Behalf Of Jiri Slaby Sent: Tuesday, March 19, 2013 5:23 AM To: Konstantin Khlebnikov Cc

  1   2   3   4   5   >