Re: [E1000-devel] backporting of i210 driver

Just use the out-of-tree igb driver (found at http://e1000.sourceforge.net). It will have support for the version of I210 you have and should compile and run on that kernel without any modification of the driver source. > -Original Message- > From: Tal Lubko [mailto:tallu...@yahoo.com]

Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on Ubuntu 3.13.0-30

> -Original Message- > From: Chris J Arges [mailto:chris.j.ar...@canonical.com] > Sent: Thursday, December 11, 2014 6:35 PM > To: Allan, Bruce W; Fujinaka, Todd > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-

Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on Ubuntu 3.13.0-30

> -Original Message- > From: Chris J Arges [mailto:chris.j.ar...@canonical.com] > Sent: Thursday, December 11, 2014 4:05 PM > To: Allan, Bruce W; Fujinaka, Todd > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-

Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on Ubuntu 3.13.0-30

> -Original Message- > From: Chris J Arges [mailto:chris.j.ar...@canonical.com] > Sent: Thursday, December 11, 2014 2:45 PM > To: Allan, Bruce W; Fujinaka, Todd > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-

Re: [E1000-devel] [PATCH] Issues with compiling ixgbevf-2.15.3 on Ubuntu 3.13.0-30

> -Original Message- > From: Chris J Arges [mailto:chris.j.ar...@canonical.com] > Sent: Thursday, December 11, 2014 2:01 PM > To: 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 > > On Th

Re: [E1000-devel] depmod parameter missing

> -Original Message- > From: Jeff Kirsher [mailto:jeffrey.t.kirs...@intel.com] > Sent: Friday, April 18, 2014 5:49 PM > To: Evgeni Gechev > Cc: e1000-de...@lists.sf.net > Subject: Re: [E1000-devel] depmod parameter missing > > On Sat, 2014-04-19 at 02:47 +0300, Evgeni Gechev wrote: > > Hi!

Re: [E1000-devel] Unplugging ethernet cable causes 'e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:'

I believe there is a patch that should resolve this which is currently in our internal queue and should be pushed upstream soon. > -Original Message- > From: Ronciak, John [mailto:john.ronc...@intel.com] > Sent: Wednesday, January 22, 2014 7:19 PM > To: Marc MERLIN; e1000-devel@lists.sour

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; Kir

Re: [E1000-devel] pxe boot becomes error when e1000e driver is used for intel QM57 chipset

[mailto:shunsuke.watan...@tel.com] Sent: Thursday, October 31, 2013 7:44 PM To: Allan, Bruce W Cc: jeffrey.t.kers...@intel.com; e1000-devel@lists.sourceforge.net Subject: pxe boot becomes error when e1000e driver is used for intel QM57 chipset Hi, When pxe boot is performed hundreds times, an error occurs. error

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 (Intel 82567LM) >

Re: [E1000-devel] e1000_clean_tx_irq not reclaiming some resources

Your issue is with 82574L devices, but what is this e1000-cids kernel module that is in use?!? What distribution are you using? It appears that this is on some custom kernel based off 2.6.29 with a customized version of an old e1000 driver but the standard in-kernel e1000 driver has never supp

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 box with 3.11-rc3+ > > Hi

Re: [E1000-devel] [linux-nics] e1000e + ICH8 GbE flash lock, kernel 3.9.6

IMHO, the lock is still necessary during nominal operation because, unlike the other sectors in the NVM, the GbE region is not write protected which is a contributing factor to the device corruptions that happened a few years back. The root cause of those corruptions was due to ftrace which has

Re: [E1000-devel] [PATCH] Packet drops/loss with 82579LM - fixed

> -Original Message- > From: Allan, Bruce W [mailto:bruce.w.al...@intel.com] > Sent: Monday, June 03, 2013 4:28 PM > To: Hrvoje Habjanić; e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH] Packet drops/loss with 82579LM - fixed > > > -Origin

Re: [E1000-devel] [PATCH] Packet drops/loss with 82579LM - fixed

> -Original Message- > From: Hrvoje Habjanić [mailto:hrvoje.habja...@zg.t-com.hr] > Sent: Saturday, June 01, 2013 8:43 AM > To: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH] Packet drops/loss with 82579LM - fixed > > On 01.06.2013 17:06, Hrvoje Habjanić wrote: > >

Re: [E1000-devel] e1000e_phc_settime() not working correctly

> -Original Message- > From: Jeroen Van den Keybus > [mailto:jeroen.vandenkey...@triphase.com] > Sent: Wednesday, April 17, 2013 11:43 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] e1000e_phc_settime() not working correctly > > Hi, > > I found that I was unable to se

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

lkml; e1000-devel@lists.sourceforge.net; Allan, Bruce W > Subject: Re: e1000e + suspend, 3.9-rc2 > > >>> Ok, I can still see the hardware error message when suspending: > >> > >> And with 3.8 plus these: > >> PCI/PM: Clear state_saved during suspend > >>

Re: [E1000-devel] em1 is visible to iproute2 but not ethtool or tcpdump

> -Original Message- > From: Andy Lutomirski [mailto:l...@amacapital.net] > Sent: Thursday, March 14, 2013 3:43 PM > To: Allan, Bruce W > Cc: Network Development; e1000-devel@lists.sourceforge.net > Subject: Re: em1 is visible to iproute2 but not ethtool or tcpdump &

Re: [E1000-devel] em1 is visible to iproute2 but not ethtool or tcpdump

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev- > ow...@vger.kernel.org] On Behalf Of Andy Lutomirski > Sent: Thursday, March 14, 2013 9:54 AM > To: Network Development > Cc: e1000-devel@lists.sourceforge.net > Subject: em1 is visible to iproute2 but not ethtool or

Re: [E1000-devel] e1000e 3.9-rc1 suspend failure (was: Re: e1000e: nic does not work properly after cold power on)

> -Original Message- > From: Mihai Donțu [mailto:mihai.do...@gmail.com] > Sent: Monday, March 04, 2013 2:59 PM > To: Morten Stevens > Cc: e1000-devel@lists.sourceforge.net; net...@vger.kernel.org; linux- > ker...@vger.kernel.org; Rafael J. Wysocki; Borislav Petkov; Jiri Slaby > Subject: Re:

Re: [E1000-devel] Bug#702245: Thinkpad T410s cannot detect link

> -Original Message- > From: YunQiang Su [mailto:wzss...@gmail.com] > Sent: Monday, March 04, 2013 7:58 AM > To: Ben Hutchings > Cc: e1000-devel@lists.sourceforge.net; 702...@bugs.debian.org > Subject: Re: [E1000-devel] Bug#702245: Thinkpad T410s cannot detect link > > On Mon, Mar 4, 2013

Re: [E1000-devel] [next:akpm 16/587] drivers/net/ethernet/intel/igb/igb_main.c:6231:2: error: call to '__compiletime_assert_6235' declared with attribute error: BUILD_BUG_ON failed: SKB_WITH_OVERHEAD(

> -Original Message- > From: Andrew Morton [mailto:a...@linux-foundation.org] > Sent: Tuesday, February 19, 2013 2:27 PM > To: Wu, Fengguang > Cc: Daniel Santos; Kirsher, Jeffrey T; Brandeburg, Jesse; Allan, Bruce W; > net...@vger.kernel.org > Subject: Re: [next:akpm

Re: [E1000-devel] ixgbe out-of-tree driver won't compile on 3.7-rc8

Thanks, we are already aware of the changes needed to compile on 3.7*. Updated drivers will have the appropriate changes. > -Original Message- > From: Ben Greear [mailto:gree...@candelatech.com] > Sent: Friday, December 07, 2012 8:51 AM > To: e1000-devel list > Subject: [E1000-devel] ixg

Re: [E1000-devel] e1000e driver prevents Toshiba Z930 from shutting down when LAN cable is unplugged

r Cruz [mailto:roger.c...@citrix.com] > Sent: Thursday, November 29, 2012 1:28 PM > To: Allan, Bruce W; e1000-devel@lists.sourceforge.net > Subject: RE: [E1000-devel] e1000e driver prevents Toshiba Z930 from > shutting down when LAN cable is unplugged > > It probably does. How do I

Re: [E1000-devel] e1000e driver prevents Toshiba Z930 from shutting down when LAN cable is unplugged

Sounds to me like a possible issue with runtime power management. Is that feature enabled in your kernel and for the LAN interface? > -Original Message- > From: Roger Cruz [mailto:roger.c...@citrix.com] > Sent: Thursday, November 29, 2012 11:51 AM > To: e1000-devel@lists.sourceforge.net

Re: [E1000-devel] PATCH: PTP support for 82574 in e1000e 1.6.3 driver

> -Original Message- > From: Adrian Knoth [mailto:a...@drcomp.erfurt.thur.de] > Sent: Tuesday, November 06, 2012 8:12 AM > To: Allan, Bruce W > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] PATCH: PTP support for 82574 in e1000e 1.6.3 > driver >

Re: [E1000-devel] Intel Corporation 82579LM Gigabit Network Connection (rev 04) packet loss

> -Original Message- > From: Kai Hendry [mailto:hen...@iki.fi] > Sent: Saturday, October 27, 2012 9:31 PM > To: e1000-de...@lists.sf.net > Subject: [E1000-devel] Intel Corporation 82579LM Gigabit Network > Connection (rev 04) packet loss > > Hi there, > > I'm having wired connections issu

Re: [E1000-devel] PATCH: PTP support for 82574 in e1000e 1.6.3 driver

please let us know so we can escalate getting it enabled and thoroughly tested on that device. > -Original Message- > From: Adrian Knoth [mailto:a...@drcomp.erfurt.thur.de] > Sent: Wednesday, October 24, 2012 4:52 AM > To: Allan, Bruce W > Cc: e1000-devel@lists.sourceforge.ne

Re: [E1000-devel] [PATCH 0/7] Compiler warning clean-up

> -Original Message- > From: Chuck Lever [mailto:chuck.le...@oracle.com] > Sent: Thursday, August 30, 2012 3:32 PM > To: Allan, Bruce W > Cc: Waskiewicz Jr, Peter P; e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH 0/7] Compiler warning clean-up >

Re: [E1000-devel] [PATCH 0/7] Compiler warning clean-up

> -Original Message- > From: Waskiewicz Jr, Peter P [mailto:peter.p.waskiewicz...@intel.com] > Sent: Thursday, August 30, 2012 2:11 PM > To: Chuck Lever > Cc: e1000-devel@lists.sourceforge.net > Subject: Re: [E1000-devel] [PATCH 0/7] Compiler warning clean-up > > On Thu, 2012-08-30 at 14:0

Re: [E1000-devel] MAC Spoofing support

> -Original Message- > From: Jonathan Hoyland [mailto:jonathan.hoyl...@gmail.com] > Sent: Tuesday, August 14, 2012 7:44 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] MAC Spoofing support > > Hi, > > I have an Intel 82577LM adapter. I was wondering, does the e1000e >

Re: [E1000-devel] Crash in e1000e, 3.3.8+ (tainted)

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev- > ow...@vger.kernel.org] On Behalf Of Ben Greear > Sent: Tuesday, July 24, 2012 2:46 PM > To: e1000-devel list; netdev > Subject: Crash in e1000e, 3.3.8+ (tainted) > > We have a somewhat reproducible crash using a 6-

Re: [E1000-devel] [PATCH net-next 3/4] e1000e: advertise transmit time stamping

> -Original Message- > From: Richard Cochran [mailto:richardcoch...@gmail.com] > Sent: Sunday, July 22, 2012 10:16 AM > To: net...@vger.kernel.org > Cc: e1000-devel@lists.sourceforge.net; Willem de Bruijn; David Miller > Subject: [E1000-devel] [PATCH net-next 3/4] e1000e: advertise transmit

Re: [E1000-devel] Linux 3.4.2 doesn't detect Intel 82579V on Supermicro X9SCL-F

> -Original Message- > From: Denys Fedoryshchenko [mailto:de...@visp.net.lb] > Sent: Friday, July 06, 2012 9:50 PM > To: Allan, Bruce W > Cc: e1000-devel@lists.sourceforge.net > Subject: RE: Linux 3.4.2 doesn't detect Intel 82579V on Supermicro X9SCL-F > &g

Re: [E1000-devel] e1000e: only 10M full-duplex after suspend / reloading module works

> -Original Message- > From: Philipp Kern [mailto:pk...@debian.org] > Sent: Friday, June 29, 2012 9:10 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] e1000e: only 10M full-duplex after suspend / > reloading module works > > Hi, > > I'm running a Debian kernel and at l

Re: [E1000-devel] Linux 3.4.2 doesn't detect Intel 82579V on Supermicro X9SCL-F

> -Original Message- > From: Denys Fedoryshchenko [mailto:de...@visp.net.lb] > Sent: Saturday, June 23, 2012 1:05 AM > To: Kirsher, Jeffrey T; Brandeburg, Jesse; Allan, Bruce W; Wyborny, > Carolyn; Skidmore, Donald C; Rose, Gregory V; Waskiewicz Jr, Peter P; > Duyck, Al

Re: [E1000-devel] Linux 3.4.2 doesn't detect Intel 82579V on Supermicro X9SCL-F

> -Original Message- > From: Denys Fedoryshchenko [mailto:de...@visp.net.lb] > Sent: Saturday, June 23, 2012 1:05 AM > To: Kirsher, Jeffrey T; Brandeburg, Jesse; Allan, Bruce W; Wyborny, > Carolyn; Skidmore, Donald C; Rose, Gregory V; Waskiewicz Jr, Peter P; > Duyck, Al

Re: [E1000-devel] e1000e PHY ID detection broken with 82579LM

> -Original Message- > From: Heikki Krogerus [mailto:heikki.kroge...@linux.intel.com] > Sent: Tuesday, June 19, 2012 6:24 AM > To: Kirsher, Jeffrey T > Cc: Allan, Bruce W; e1000-devel@lists.sourceforge.net > Subject: e1000e PHY ID detection broken with 82579LM > &g

Re: [E1000-devel] e1000e, 3.4.1, , jumbo frames are not working

> -Original Message- > From: Denys Fedoryshchenko [mailto:de...@visp.net.lb] > Sent: Friday, June 08, 2012 7:59 AM > To: Kirsher, Jeffrey T; rka...@parallels.com; sta...@vger.kernel.org; > Brandeburg, Jesse; Allan, Bruce W; Wyborny, Carolyn; Skidmore, Donald >

Re: [E1000-devel] [PATCH] e1000e: disable rxhash when try to enable jumbo frame also rxhash and rxcsum have enabled

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, June 07, 2012 6:12 PM > To: joe@oracle.com > Cc: e1000-devel@lists.sourceforge.net; guru.anbalag...@oracle.com; > Allan, Bruce W; Brandeburg, Jesse; adnan.mishe...@oracle.com; Ro

Re: [E1000-devel] [next-net PATCH] drivers/net/ethernet/intel/e1000e: fix unregistered net_device ethX name output by e1000e

> -Original Message- > From: Jeff Kirsher [mailto:jeffrey.t.kirs...@intel.com] > Sent: Wednesday, June 06, 2012 5:41 PM > To: Ethan Zhao > Cc: e1000-devel@lists.sourceforge.net; Linux NICS; LKML > Subject: Re: [E1000-devel] [next-net PATCH] > drivers/net/ethernet/intel/e1000e: fix unregiste

Re: [E1000-devel] [patch 0/1] 82571EB: fix NULL pointer deref in e1000e v1.11.3

> -Original Message- > From: hol...@eitzenberger.org [mailto:hol...@eitzenberger.org] > Sent: Tuesday, May 29, 2012 4:43 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] [patch 0/1] 82571EB: fix NULL pointer deref in > e1000e v1.11.3 > > Hi list, > > I see a NULL pointe

Re: [E1000-devel] speed and speed_hi setting in ethtool_cmd

> -Original Message- > From: Shashidhara Shamaiah [mailto:shashidhara.shama...@mphasis.com] > Sent: Tuesday, May 22, 2012 4:26 AM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] speed and speed_hi setting in ethtool_cmd > > Hi, > > > > There is a doubt with the working

Re: [E1000-devel] [Bug 43277] New: net/e1000e set mtu larger than 1500 fails

> -Original Message- > From: netdev-ow...@vger.kernel.org [mailto:netdev- > ow...@vger.kernel.org] On Behalf Of Stephen Hemminger > Sent: Tuesday, May 22, 2012 11:25 AM > To: c...@chrekh.se > Cc: net...@vger.kernel.org; e1000-de...@lists.sf.net > Subject: Re: [Bug 43277] New: net/e1000e set

Re: [E1000-devel] Who owns pch_gbe driver?

IIRC, the pch_gbe driver was derived from the Intel e1000e driver and written by (and should be maintained by) folks from Oki Semiconductor and others; apparently someone needs to update the ./MAINTAINERS file. There is no driver from Intel supporting that device that I am aware of. I recommend y

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

erbed.com] > Sent: Wednesday, April 18, 2012 5:18 PM > To: Allan, Bruce W; Kirsher, Jeffrey T; Brandeburg, Jesse; Pieper, > Jeffrey E > Cc: e1000-devel@lists.sourceforge.net; > prasanna.panchamu...@riverbed.com > Subject: [PATCH] e1000e: MSI interrupt test failed, using legacy >

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

> -Original Message- > From: Tim Pepper [mailto:lnxni...@linux.vnet.ibm.com] > Sent: Wednesday, February 15, 2012 1:19 PM > To: e1000-devel@lists.sourceforge.net > Subject: [E1000-devel] e1000_close() and concurrent reset > > I've got some systems whose nic's periodically go up and down, p

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

>-Original Message- >From: Carsten Aulbert [mailto:carsten.aulb...@aei.mpg.de] >Sent: Thursday, January 26, 2012 2:07 AM >To: e1000-de...@lists.sf.net >Cc: Henning Fehrmann >Subject: [E1000-devel] High number of rx_missed_errors when chaning from 1.0.2- >k2 to 1.2.20-k2/1.5.1-k > >Hi all >

Re: [E1000-devel] e1000e: repeated eth0: Error reading PHY register

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Andy Isaacson >Sent: Wednesday, January 25, 2012 1:21 AM >To: linux-ker...@vger.kernel.org; net...@vger.kernel.org; e1000- >de...@lists.sourceforge.net >Subject: e1000e:

Re: [E1000-devel] problematic behaviour of e1000e

>-Original Message- >From: Barry Green [mailto:b.gr...@rhul.ac.uk] >Sent: Tuesday, December 20, 2011 4:14 AM >To: e1000-de...@lists.sf.net >Subject: [E1000-devel] problematic behaviour of e1000e > >Hello, we use the e1000e linux driver on a supermicro motherboard with >IPMI. It is necessary

Re: [E1000-devel] interface counters

>-Original Message- >From: Jesse Brandeburg [mailto:jesse.brandeb...@intel.com] >Sent: Tuesday, December 13, 2011 8:57 AM >To: Bokhan Artem >Cc: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] interface counters > >On Tue, 2011-12-13 at 04:16 -0800, Bokhan Artem wrote: >> Hell

Re: [E1000-devel] [PATCH] e1000e: Fix bug for e1000e interrupt default mode select.

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Ben Hutchings >Sent: Friday, December 02, 2011 9:55 AM >To: Kumar Gala >Cc: Kirsher, Jeffrey T; Brandeburg, Jesse; e1000-devel@lists.sourceforge.net; >net...@vger.kernel.org; Prabhaka

Re: [E1000-devel] e1000e/82579LM weird packet loss issue

>-Original Message- >From: Jim Westfall [mailto:jwestf...@surrealistic.net] >Sent: Sunday, November 27, 2011 5:27 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] e1000e/82579LM weird packet loss issue > >Hi > >I have a intel DQ67EP desktop board with the following onboard

Re: [E1000-devel] Problem with e1000e 1.6.2 driver on Intel S3000AHV + Intel PRO1000PT dual port server adapter

The only devices supported by the e1000e driver that support MSI-X are the 82574L SKUs (PCI device IDs 0x10d3 and 0x10f6). It sounds like you have 82571EB (device ID 0x105e) which does not support MSI-X in the hardware. If you require MSI-X with Intel Gigabit network adapters you will have to

Re: [E1000-devel] PATCH: PTP support for 82574 in e1000e 1.6.3 driver

>-Original Message- >From: Maxime Larocque [mailto:maxmtl2...@yahoo.ca] >Sent: Tuesday, November 01, 2011 1:03 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] PATCH: PTP support for 82574 in e1000e 1.6.3 driver > >Hi, > >This patch adds timestamping for PTP on the 82574L.

Re: [E1000-devel] About the fix "e1000e: workaround for packet drop on 82579 at 100Mbps (commit 0ed013e28fe853244f4972cf18d8e2bd62eeb8fc)"

>-Original Message- >From: Artem S. Tashkinov [mailto:t.ar...@lycos.com] >Sent: Wednesday, November 02, 2011 5:09 AM >To: Allan, Bruce W; Kirsher, Jeffrey T >Cc: linux-ker...@vger.kernel.org >Subject: About the fix "e1000e: workaround for packet drop on 82

Re: [E1000-devel] e100e: does it do unicast filtering?

Yes. At the time the IFF_UNICAST_FLT flag was added to many drivers by Jiri (added), the e1000e driver did not have the code to configure unicast addresses - it was missed somehow when the other drivers were similarly updated. We currently have a patch in test that does this and it will be pushed

Re: [E1000-devel] PTP on 82574L and 82599V

>-Original Message- >From: Adrian Knoth [mailto:a...@drcomp.erfurt.thur.de] >Sent: Tuesday, November 01, 2011 12:08 PM >To: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] PTP on 82574L and 82599V > >On 11/01/11 19:33, Allan, Bruce W wrote: > >>

Re: [E1000-devel] PTP on 82574L and 82599V

>-Original Message- >From: Adrian Knoth [mailto:a...@drcomp.erfurt.thur.de] >Sent: Tuesday, November 01, 2011 11:29 AM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] PTP on 82574L and 82599V > >Hi! > >While looking for PTP enabled Intel NICs, I came across the datasheets >fo

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

>-Original Message- >From: Jeff Kirsher [mailto:jeffrey.t.kirs...@intel.com] >Sent: Thursday, September 29, 2011 6:01 AM >To: Indira ramasamy >Cc: E1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] Regarding - Detected Tx Unit Hang > >On Thu, Sep 29, 2011 at 05:05, Indira ramasam

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

>-Original Message- >From: Carsten Aulbert [mailto:carsten.aulb...@aei.mpg.de] >Sent: Wednesday, September 28, 2011 11:42 PM >To: Brandeburg, Jesse >Cc: e1000-de...@lists.sf.net; Tejun Heo >Subject: Re: [E1000-devel] Possible to stop external IPMI/BMC access (port 623) >by bringing iface up

Re: [E1000-devel] [BUG?] e1000e Detected Hardware Unit Hang

>-Original Message- >From: joeyli [mailto:j...@suse.com] >Sent: Wednesday, September 28, 2011 10:33 PM >To: Dave Young >Cc: e1000-devel@lists.sourceforge.net; linux-ker...@vger.kernel.org >Subject: Re: [E1000-devel] [BUG?] e1000e Detected Hardware Unit Hang > >於 四，2011-09-29 於 13:37 +0800，D

Re: [E1000-devel] Unexpected downshift

As far as I can tell, this issue was never resolved in any driver. If you wish us to investigate further, please file a bug tracker at http://sourceforge.net/tracker/?group_id=42302&atid=447449 and provide a full description of your environment (particularly the output from 'lspci -vvv' run as

Re: [E1000-devel] e1000e driver is making our machines hang during shutdown, please help us

>-Original Message- >From: Diego Viola [mailto:diego.vi...@gmail.com] >Sent: Thursday, June 02, 2011 11:05 PM >To: e1000-de...@lists.sf.net >Subject: [E1000-devel] e1000e driver is making our machines hang during >shutdown, please help us > >Hello, > >We are having problems with the e1000e

Re: [E1000-devel] e1000e driver and S5 WakeonLan

>-Original Message- >From: Martin Owens [mailto:docto...@gmail.com] >Sent: Tuesday, May 24, 2011 4:52 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] e1000e driver and S5 WakeonLan > >Dear developers, > >I have 10 computers in a community center lab, they are networked and

Re: [E1000-devel] Problems with e1000e network drivers HW multicast filtering

Thank you for reporting this issue. I've asked our validation folks to try to reproduce it in order for us to debug it. In the meantime, please file a bug tracker at http://e1000.sourceforge.net to track the issue. Thanks, Bruce. >-Original Message- >From: Otto Airamo [mailto:otto.air

Re: [E1000-devel] modprobe gets stuck on a e1000e driver mutex wile trying to load the it

>-Original Message- >From: Edy H. [mailto:edwardh@gmail.com] >Sent: Sunday, March 06, 2011 4:35 AM >To: e1000-devel@lists.sourceforge.net; linux-...@vger.kernel.org; >net...@vger.kernel.org >Subject: [E1000-devel] modprobe gets stuck on a e1000e driver mutex wile >trying to load the it

Re: [E1000-devel] WoL stopped working after power off with 2.6.38 (e1000e specific?)

>-Original Message- >From: Allan, Bruce W [mailto:bruce.w.al...@intel.com] >Sent: Monday, May 02, 2011 3:02 PM >To: Kamil Iskra; net...@vger.kernel.org; e1000-devel@lists.sourceforge.net >Cc: linux...@lists.linux-foundation.org >Subject: Re: [E1000-devel] WoL stopped w

Re: [E1000-devel] WoL stopped working after power off with 2.6.38 (e1000e specific?)

>-Original Message- >From: Kamil Iskra [mailto:ka...@iskra.name] >Sent: Friday, April 29, 2011 10:45 PM >To: net...@vger.kernel.org; e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] WoL stopped working after power off with 2.6.38 (e1000e >specific?) > >[ Note: I'm not on these mail

Re: [E1000-devel] Alternate MAC address support disabled for 82573 ?

t: Monday, May 02, 2011 12:56 AM >To: Allan, Bruce W; Ronciak, John; Lindsay, Morgan N; e1000- >de...@lists.sourceforge.net >Cc: Rajagopal, Ramadurai >Subject: AW: Alternate MAC address support disabled for 82573 ? > >Hello, > >we found the issue why our network devices haven

Re: [E1000-devel] Reporting error in e1000e driver for 82571 chip.

-v -s ]:]]:][][.[]]' for this device. Thanks, Bruce. From: ulrik.mikaels...@canaldigital.se [mailto:ulrik.mikaels...@canaldigital.se] Sent: Thursday, April 14, 2011 2:22 AM To: Linux NICS Cc: Kok, Auke-jan H; Allan, Bruce W Subject: Reporting error in e1000e driver for 82571 chip. Hi, I would

Re: [E1000-devel] NV memory corruption 82571EB

Please open a bug tracker issue on http://e1000.sf.net and provide the output from 'lspci -vvv' (run as root), 'ethtool -e ethX' (where ethX is the interface(s) for your 82571EB adapter(s)) and the output from dmesg after the driver has loaded (i.e. after the NVM checksum failure notice). FWIW,

Re: [E1000-devel] Alternate MAC address support disabled for 82573 ?

installed on? What is its architecture? Thanks, Bruce. >-Original Message- >From: Mangard Martin [mailto:martin.mang...@automationx.com] >Sent: Friday, April 08, 2011 7:56 AM >To: Ronciak, John; Allan, Bruce W; Lindsay, Morgan N; e1000- >de...@lists.sourceforge.net

Re: [E1000-devel] Alternate MAC address support disabled for 82573 ?

Also, when checking the state of ASPM you need to look at the output for the 82573 device, not the PCI bridge...just to be sure. >-Original Message- >From: Ronciak, John >Sent: Tuesday, April 05, 2011 8:37 AM >To: Mangard Martin; Allan, Bruce W; Lindsay, Morgan N

Re: [E1000-devel] Alternate MAC address support disabled for 82573 ?

here never supposed to be supported on 82573 and it was a bug in the driver that allowed it before ca. 2.6.35. >-Original Message- >From: Mangard Martin [mailto:martin.mang...@automationx.com] >Sent: Monday, April 04, 2011 4:00 AM >To: Lindsay, Morgan N; Allan, Bruce W; e1000-devel

Re: [E1000-devel] Alternate MAC address support disabled for 82573 ?

AFAIK, alternate MAC addresses are not supported on 82573; with the Linux e1000e driver they are only supported on 80003ES2LAN and 82571 LOMs and a couple 82571 mezzanine cards. Adding Morgan and Ram for confirmation of support on 82573. Thanks, Bruce. >-Original Message- >From: Mangar

Re: [E1000-devel] transmit hang under load 82574L

>-Original Message- >From: Stephen Hemminger [mailto:shemmin...@vyatta.com] >Sent: Thursday, March 17, 2011 10:22 AM >To: Allan, Bruce W >Cc: Kirsher, Jeffrey T; Jesse Brandeburg; e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] transmit hang under load 82574

Re: [E1000-devel] transmit hang under load 82574L

>-Original Message- >From: Stephen Hemminger [mailto:shemmin...@vyatta.com] >Sent: Thursday, March 17, 2011 9:45 AM >To: Kirsher, Jeffrey T; Jesse Brandeburg >Cc: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] transmit hang under load 82574L > >Running Intel n450 development boar

Re: [E1000-devel] Corrupted NVM on 82574

>From where/whom did you get these EEPROM images (or profiles)? >-Original Message- >From: Eldon Hiebert [mailto:hieb...@selex-si-us.com] >Sent: Friday, March 11, 2011 7:00 AM >To: E1000-devel@lists.sourceforge.net >Subject: [E1000-devel] Corrupted NVM on 82574 > >HELP! > >I have a cus

Re: [E1000-devel] Wake on ARP not working

The short answer is the driver should never have suggested (via ethtool) that it supports Wake-on-ARP because it does not; i.e. it does not populate the appropriate address tables in hardware, nor is there a way to do that yet. I'll be submitting a patch that removes that option. Wake-on-ARP m

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

OK, that's great news! I'll check into why ASPM is not getting set correctly by the kernel. >-Original Message- >From: Nix [mailto:n...@esperi.org.uk] >Sent: Wednesday, February 09, 2011 12:24 PM >To: Allan, Bruce W >Cc: Jesse Brandeburg; e1000-devel@lists.sou

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

>-Original Message- >From: Jesse Brandeburg [mailto:jesse.brandeb...@gmail.com] >Sent: Monday, January 31, 2011 11:48 PM >To: Nix >Cc: Allan, Bruce W; e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue >

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

>-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 continue >in >2.6.37 > >On 31

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

>-Original Message- >From: Nix [mailto:n...@esperi.org.uk] >Sent: Monday, January 31, 2011 3:24 PM >To: Allan, Bruce W >Cc: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue >in >2.6.37 > >On 31

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

>-Original Message- >From: Allan, Bruce W [mailto:bruce.w.al...@intel.com] >Sent: Monday, January 31, 2011 3:06 PM >To: Nix >Cc: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue >in >2.6.37 > >

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

>-Original Message- >From: Nix [mailto:n...@esperi.org.uk] >Sent: Monday, January 31, 2011 2:43 PM >To: Allan, Bruce W >Cc: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue >in >2.6.37 > >On 3

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

>-Original Message- >From: Nix [mailto:n...@esperi.org.uk] >Sent: Saturday, January 29, 2011 3:44 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] 82754L spontaneous freeze networking woes continue in >2.6.37 > >Way back in November, in >

Re: [E1000-devel] Small patch e1000e

NAK. While this is indeed a trivial patch to enable a device that is not currently supported in e1000e, this device requires special handling to get the bypass functionality to work properly and as such this patch is insufficient. To get support for this device either: • contact the company

Re: [E1000-devel] ARP-based WoL?

>-Original Message- >From: Matthew Garrett [mailto:mj...@srcf.ucam.org] >Sent: Tuesday, January 04, 2011 11:43 AM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] ARP-based WoL? > >e1000e claims to support WAKE_ARP, but I can't see any way that this can >work at present. Somet

Re: [E1000-devel] 2.6.36.1 e1000e - Detected Tx Unit Hang

Sorry to hear about your problem, and the lack of a response in so long. Have you filed a bug tracker at http://sourceforge.net/tracker/?group_id=42302&atid=447449 with this same information? If not, I suggest you do so your issue does not fall through the cracks again. Thanks, Bruce. >

Re: [E1000-devel] [PATCH] e1000e: workaround missing power down mii control bit on 82571

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Arthur Jones >Sent: Monday, December 20, 2010 7:33 AM >To: Allan, Bruce W >Cc: Ben Hutchings; Kirsher, Jeffrey T; net...@vger.kernel.org >Subject: Re: [PATC

Re: [E1000-devel] 82577 PHY_ID1 reading 0xffff [phy.c]

Fixed in ich8lan.c >-Original Message- >From: Mandar Jog [mailto:mandar...@gmail.com] >Sent: Wednesday, December 15, 2010 9:41 AM >To: Allan, Bruce W >Cc: e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82577 PHY_ID1 reading 0x [phy.c] > >Looki

Re: [E1000-devel] 82574L link negotitian issue wih Cisco 877 ADSL Router.

>-Original Message- >From: Nishit Shah [mailto:nis...@elitecore.com] >Sent: Wednesday, December 15, 2010 2:24 AM >To: e1000-de...@lists.sf.net >Subject: [E1000-devel] 82574L link negotitian issue wih Cisco 877 ADSL Router. > >Hi, > > > >We are facing issue of link negotiation of Intel 82574

Re: [E1000-devel] 82577 PHY_ID1 reading 0xffff [phy.c]

>-Original Message- >From: Mandar Jog [mailto:mandar...@gmail.com] >Sent: Tuesday, December 14, 2010 6:24 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] 82577 PHY_ID1 reading 0x [phy.c] > >Hi, >I am PXE booting my thinking X201 with a 82577LM Gigabit Ethernet card. >

Re: [E1000-devel] Intel 82562V Driver

Yes it is a 10/100 device, but it is actually supported by the e1000e driver. >-Original Message- >From: Ronciak, John [mailto:john.ronc...@intel.com] >Sent: Thursday, December 09, 2010 8:02 AM >To: Andreas Geisler; e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] Intel 82562V

Re: [E1000-devel] System crash - 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)

. What exactly is the message displayed when kdb started, and what does a backtrace (bt) command in kdb show? >-Original Message- >From: S, Manu (Manu) [mailto:man...@alcatel-lucent.com] >Sent: Wednesday, November 24, 2010 12:08 AM >To: S, Manu (Manu); Allan, Bruce W; R

Re: [E1000-devel] System crash - 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)

Any word on when the system log will be provided? -Original Message- From: S, Manu (Manu) [mailto:man...@alcatel-lucent.com] Sent: Sunday, November 21, 2010 8:55 PM To: Ronciak, John; Allan, Bruce W; RAGHAVENDRA, PRAVIN (PRAVIN)** CTR **; 'e1000-de...@lists.sf.net' Cc: L

Re: [E1000-devel] System crash - 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)

? Thanks, Bruce. -Original Message- From: S, Manu (Manu) [mailto:man...@alcatel-lucent.com] Sent: Thursday, November 18, 2010 2:55 AM To: Allan, Bruce W; RAGHAVENDRA, PRAVIN (PRAVIN)** CTR **; 'e1000-de...@lists.sf.net' Cc: K, Richard (Richard); LAMP-KERNEL-SUPPORT Subject:

Re: [E1000-devel] System crash - 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)

Please provide the oops message from the system log (usually /var/log/messages). >From where did you get the e1000e-1.2.10-1.x86_64.rpm package? What version of Open SuSE are you using? What is the exact kernel version number (stating just "2.6.30" could mean the vanilla 2.6.30 kernel from ker

Re: [E1000-devel] 82574L + ASPM now fixed?

On Thursday, September 30, 2010 10:09 AM, Jeremy Fitzhardinge wrote: > Does change 0531e961fc58bd6c3956c300fe71dee7e771953c "e1000e: > 82577/82578 PHY register access issues" (in stable-2.6.32) fix the bug > http://sourceforge.net/tracker/index.php?func=detail&aid=2908463&group_id=42302&atid=44744

  1   2   >