RE: [Intel-wired-lan] Possible read-modify-write bug in ixgbe x550 phy setup

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On >Behalf Of Tantilov, Emil S >Sent: Thursday, February 01, 2018 4:58 PM >To: Shannon Nelson <shannon.nel...@oracle.com> >Cc: netdev@vger.kernel.org; intel-wired-...@lists

RE: [Intel-wired-lan] Possible read-modify-write bug in ixgbe x550 phy setup

>-Original Message- >From: Shannon Nelson [mailto:shannon.nel...@oracle.com] >Sent: Thursday, February 01, 2018 4:44 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: netdev@vger.kernel.org; intel-wired-...@lists.osuosl.org >Subject: Re: [Intel-wired-lan] Po

RE: [Intel-wired-lan] Possible read-modify-write bug in ixgbe x550 phy setup

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On >Behalf Of Shannon Nelson >Sent: Thursday, February 01, 2018 3:46 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: netdev@vger.kernel.org; intel-wired-...@lists.osu

RE: 4.15.0-rc6 unable to handle kernel NULL pointer dereference in ixgbe_down

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] >On Behalf Of wangyunjian >Sent: Monday, January 08, 2018 1:31 AM >To: netdev@vger.kernel.org; intel-wired-...@lists.osuosl.org >Subject: BUG: 4.15.0-rc6 unable to handle kernel NULL pointer

RE: [PATCH v3 net 2/2] net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Ding Tianhong >Sent: Thursday, August 17, 2017 11:21 PM >To: da...@davemloft.net; Kirsher, Jeffrey T ; >keesc...@chromium.org;

RE: [PATCH net v2 2/2] net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

>-Original Message- >From: Ding Tianhong [mailto:dingtianh...@huawei.com] >Sent: Thursday, August 17, 2017 5:39 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com>; da...@davemloft.net; >Kirsher, Jeffrey T <jeffrey.t.kirs...@intel.com>; keesc...@chromium.org; &g

RE: [PATCH net v2 2/2] net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

>-Original Message- >From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- >ow...@vger.kernel.org] On Behalf Of Ding Tianhong >Sent: Wednesday, August 16, 2017 8:25 PM >To: da...@davemloft.net; Kirsher, Jeffrey T ; >keesc...@chromium.org;

RE: [PATCH] PCI: Update ACS quirk for more Intel 10G NICs

>-Original Message- >From: Roland Dreier [mailto:rol...@purestorage.com] On Behalf Of Roland >Dreier >Sent: Thursday, July 20, 2017 2:41 PM >To: Bjorn Helgaas <bhelg...@google.com> >Cc: linux-...@vger.kernel.org; netdev@vger.kernel.org; Tantilov, Emil S >

RE: [net-next v2 6/6] ixgbe: Add malicious driver detection support

>-Original Message- >From: David Miller [mailto:da...@davemloft.net] >Sent: Thursday, June 29, 2017 11:28 AM >To: gerlitz...@gmail.com >Cc: Tantilov, Emil S <emil.s.tanti...@intel.com>; Kirsher, Jeffrey T ><jeffrey.t.kirs...@intel.com>; Greenwalt, Paul <p

RE: [net-next v2 6/6] ixgbe: Add malicious driver detection support

>-Original Message- >From: Or Gerlitz [mailto:gerlitz...@gmail.com] >Sent: Tuesday, June 27, 2017 2:07 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: Kirsher, Jeffrey T <jeffrey.t.kirs...@intel.com>; David Miller ><da...@davemloft.net>; Green

RE: [net-next v2 6/6] ixgbe: Add malicious driver detection support

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Or Gerlitz >Sent: Tuesday, June 27, 2017 2:08 AM >To: Kirsher, Jeffrey T >Cc: David Miller ; Greenwalt, Paul

RE: [net-next 02/11] ixgbe: add XDP support for pass and drop actions

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Jeff Kirsher >Sent: Thursday, April 20, 2017 6:50 PM >To: da...@davemloft.net >Cc: Fastabend, John R ; netdev@vger.kernel.org; >nhor...@redhat.com;

RE: [PATCH 1/1] ixgbe: add the external ixgbe fiber transceiver status

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Zhu Yanjun >Sent: Wednesday, February 08, 2017 7:03 PM >To: Kirsher, Jeffrey T ; broo...@kernel.org; >da...@davemloft.net;

RE: [Intel-wired-lan] [PATCH v2] PCI: lock each enable/disable num_vfs operation in sysfs

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of Greg >Sent: Friday, January 06, 2017 3:18 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: linux-...@vger.kernel.org; intel-wired-...@lists

RE: [PATCH 2/2] PCI: lock each enable/disable num_vfs operation in sysfs

>-Original Message- >From: Gavin Shan [mailto:gws...@linux.vnet.ibm.com] >Sent: Wednesday, January 04, 2017 3:12 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: Gavin Shan <gws...@linux.vnet.ibm.com>; linux-...@vger.kernel.org; >intel-wired-...@list

RE: [PATCH 2/2] PCI: lock each enable/disable num_vfs operation in sysfs

>-Original Message- >From: Gavin Shan [mailto:gws...@linux.vnet.ibm.com] >Sent: Tuesday, January 03, 2017 6:16 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: linux-...@vger.kernel.org; intel-wired-...@lists.osuosl.org; Duyck, >Alexander H <alexander

RE: [PATCH 1/1] ixgbe: replace defined with IS_ENABLED

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of zyjzyj2...@gmail.com >Sent: Wednesday, September 14, 2016 8:27 AM >To: netdev@vger.kernel.org; intel-wired-...@lists.osuosl.org; Kirsher, >Jeffrey T ;

RE: [PATCH] ixgbe: mark symbols static where possible

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of Baoyou Xie >Sent: Sunday, September 18, 2016 1:48 AM >To: Kirsher, Jeffrey T ; intel-wired- >l...@lists.osuosl.org >Cc: netdev@vger.kernel.org;

RE: [Intel-wired-lan] [PATCH -next] ixgbe: Fix non static symbol warnings

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of Wei Yongjun >Sent: Tuesday, August 23, 2016 8:07 AM >To: Kirsher, Jeffrey T >Cc: intel-wired-...@lists.osuosl.org; Wei Yongjun ;

RE: [Intel-wired-lan] [PATCH] ixgbe: always initialize setup_fc

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of Patrick McLean >Sent: Friday, July 01, 2016 6:31 PM >To: Kirsher, Jeffrey T >Cc: netdev@vger.kernel.org; intel-wired-...@lists.osuosl.org >Subject:

RE: [Intel-wired-lan] [PATCH] (resend) ixgbe: always initialize setup_fc

>-Original Message- >From: Patrick McLean [mailto:patri...@gaikai.com] >Sent: Friday, July 08, 2016 9:45 AM >To: zhuyj <zyjzyj2...@gmail.com> >Cc: Tantilov, Emil S <emil.s.tanti...@intel.com>; Rustad, Mark D ><mark.d.rus...@intel.com>; netdev <n

RE: [Intel-wired-lan] [PATCH] (resend) ixgbe: always initialize setup_fc

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of Rustad, Mark D >Sent: Wednesday, July 06, 2016 4:01 PM >To: Patrick McLean >Cc: netdev ; intel-wired-lan l...@lists.osuosl.org> >Subject:

RE: [linux-nics] e1000e: initialization breaks IPMI support on 80003ES2LAN

>-Original Message- >From: linux-nics-boun...@isotope.jf.intel.com [mailto:linux-nics- >boun...@isotope.jf.intel.com] On Behalf Of Lucas Nussbaum >Sent: Friday, February 12, 2016 7:59 AM >To: Linux Kernel Network Developers >Cc: Linux NICS

RE: bonding reports interface up with 0 Mbps

>-Original Message- >From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com] >Sent: Thursday, February 04, 2016 4:37 PM >To: Tantilov, Emil S <emil.s.tanti...@intel.com> >Cc: netdev@vger.kernel.org; go...@cumulusnetworks.com; zhuyj ><zyjzyj2...@gmail.com>;

RE: bonding reports interface up with 0 Mbps

>-Original Message- >From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com] >Sent: Thursday, February 04, 2016 4:37 PM >To: Tantilov, Emil S >Cc: netdev@vger.kernel.org; go...@cumulusnetworks.com; zhuyj; >j...@mellanox.com >Subject: Re: bonding reports interface

RE: bonding reports interface up with 0 Mbps

>-Original Message- >From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com] >Sent: Thursday, February 04, 2016 4:37 PM >To: Tantilov, Emil S >Cc: netdev@vger.kernel.org; go...@cumulusnetworks.com; zhuyj; >j...@mellanox.com >Subject: Re: bonding reports interface

RE: bonding reports interface up with 0 Mbps

>-Original Message- >From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com] >Sent: Wednesday, February 03, 2016 9:57 PM >To: Tantilov, Emil S >Cc: netdev@vger.kernel.org; go...@cumulusnetworks.com; zhuyj; >j...@mellanox.com >Subject: Re: bonding reports interface up wi

bonding reports interface up with 0 Mbps

We are seeing an occasional issue where the bonding driver may report interface up with 0 Mbps: bond0: link status definitely up for interface eth0, 0 Mbps full duplex So far in all the failed traces I have collected this happens on NETDEV_CHANGELOWERSTATE event: <...>-20533 [000]

RE: [PATCH 1/1] ixgbe: get link speed as a slave nic unrelated with link up

>-Original Message- >From: zyjzyj2...@gmail.com [mailto:zyjzyj2...@gmail.com] >Sent: Sunday, January 31, 2016 11:28 PM >To: zyjzyj2...@gmail.com; Tantilov, Emil S; Schmitt, Phillip J; Kirsher, >Jeffrey T; netdev@vger.kernel.org; e1000-de...@lists.sourceforge.net; >Shtei

RE: ixgbe: get link speed as a slave nic unrelated with link

>-Original Message- >From: zyjzyj2...@gmail.com [mailto:zyjzyj2...@gmail.com] >Sent: Sunday, January 31, 2016 11:28 PM >To: zyjzyj2...@gmail.com; Tantilov, Emil S; Schmitt, Phillip J; Kirsher, >Jeffrey T; netdev@vger.kernel.org; e1000-de...@lists.sourceforge.net; >Shtei

RE: [PATCH 1/1] bonding: Use notifiers for slave link state detection

>-Original Message- >From: Jay Vosburgh [mailto:jay.vosbu...@canonical.com] >Sent: Monday, January 25, 2016 10:01 PM >To: zhuyj >Cc: mkube...@suse.cz; vfal...@gmail.com; go...@cumulusnetworks.com; >netdev@vger.kernel.org; Shteinbock, Boris (Wind River); Tantilov, E

RE: [PATCH 1/1] bonding: Use notifiers for slave link state detection

;River); jay.vosbu...@canonical.com; Tantilov, Emil S >Subject: [PATCH 1/1] bonding: Use notifiers for slave link state detection > >From: Zhu Yanjun <zyjzyj2...@gmail.com> > >Bonding will utilize notifier callbacks to detect slave >link state changes. It is intended to be used with

RE: [PATCH 1/1] bonding: Use notifiers for slave link state detection

;River); jay.vosbu...@canonical.com; Tantilov, Emil S >Subject: [PATCH 1/1] bonding: Use notifiers for slave link state detection > > >Hi, Jay && Emil > >Thanks for your hard work. I forget to send this patch to you. Please help >to review. Thanks a lot. > >I think the simila

RE: [PATCH 1/1] bonding: Use notifiers for slave link state detection

>-Original Message- >From: David Miller [mailto:da...@davemloft.net] >Sent: Monday, January 25, 2016 10:00 AM >To: Tantilov, Emil S >Cc: zyjzyj2...@gmail.com; mkube...@suse.cz; vfal...@gmail.com; >go...@cumulusnetworks.com; netdev@vger.kernel.org; Shteinbock, Boris (Wind

RE: [Intel-wired-lan] [PATCH 2/2] ixgbe: restrict synchronization of link_up and speed

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Tuesday, January 05, 2016 9:42 PM >To: Tantilov, Emil S; Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, >Shannon; Wyborny, Carolyn; Skidmore, Donald C; Allan, Bruce W; Ronciak, >John; Williams, Mi

RE: [PATCH 1/1] bonding: restrict up state in 802.3ad mode

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Wednesday, January 06, 2016 7:34 PM >To: Tantilov, Emil S; Michal Kubecek; Jay Vosburgh >Cc: vfal...@gmail.com; go...@cumulusnetworks.com; netdev@vger.kernel.org; >Shteinbock, Boris (Wind River) >Su

RE: [PATCH 1/1] bonding: restrict up state in 802.3ad mode

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Tuesday, January 05, 2016 7:05 PM >To: Tantilov, Emil S; Michal Kubecek; Jay Vosburgh >Cc: vfal...@gmail.com; go...@cumulusnetworks.com; netdev@vger.kernel.org; >Shteinbock, Boris (Wind River) >Su

RE: [PATCH 1/1] bonding: restrict up state in 802.3ad mode

>-Original Message- >From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] On >Behalf Of zhuyj >Sent: Monday, December 28, 2015 1:19 AM >To: Michal Kubecek; Jay Vosburgh >Cc: vfal...@gmail.com; go...@cumulusnetworks.com; netdev@vger.kernel.org; >Shteinbock, Boris (Wind

RE: [Intel-wired-lan] [PATCH 2/2] ixgbe: restrict synchronization of link_up and speed

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Wednesday, December 30, 2015 12:20 AM >To: Tantilov, Emil S; Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, >Shannon; Wyborny, Carolyn; Skidmore, Donald C; Allan, Bruce W; Ronciak, >John; Williams, Mi

RE: [Intel-wired-lan] [PATCH 2/2] ixgbe: restrict synchronization of link_up and speed

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of zyjzyj2...@gmail.com >Sent: Monday, December 28, 2015 6:32 PM >To: Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, Shannon; Wyborny, >Carolyn; Skidmore, Donald C; Allan, Bruce W;

RE: [Intel-wired-lan] [PATCH 2/2] ixgbe: restrict synchronization of link_up and speed

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Tuesday, December 29, 2015 6:49 PM >To: Tantilov, Emil S; Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, >Shannon; Wyborny, Carolyn; Skidmore, Donald C; Allan, Bruce W; Ronciak, >John; Williams, Mi

RE: [net-next 8/9] ixgbe: fix write to VLVFB in ixgbe_clear_vf_vlans()

>-Original Message- >From: Kirsher, Jeffrey T >Sent: Thursday, December 24, 2015 9:30 PM >To: da...@davemloft.net >Cc: Tantilov, Emil S; netdev@vger.kernel.org; nhor...@redhat.com; >sassm...@redhat.com; jogre...@redhat.com; Kirsher, Jeffrey T >Subject: [net-next

RE: [Intel-wired-lan] [PATCH 1/1] ixgbe: force to synchronize reporting "link on" and getting speed and duplex

>-Original Message- >From: zhuyj [mailto:zyjzyj2...@gmail.com] >Sent: Wednesday, December 23, 2015 6:28 PM >To: Tantilov, Emil S; Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, >Shannon; Wyborny, Carolyn; Skidmore, Donald C; Allan, Bruce W; Ronciak, >John; Williams, Mi

RE: [Intel-wired-lan] [V2 PATCH 1/1] ixgbe: force to synchronize reporting "link on" and

>-Original Message- >From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On >Behalf Of zhuyj >Sent: Wednesday, December 23, 2015 9:11 PM >To: Kirsher, Jeffrey T; Brandeburg, Jesse; Nelson, Shannon; Wyborny, >Carolyn; Skidmore, Donald C; Allan, Bruce W; Ronciak, John;

RE: regression in ixgbe SFP detection patch

>-Original Message- >From: William Dauchy [mailto:will...@gandi.net] >Sent: Wednesday, November 11, 2015 9:35 AM >To: Kirsher, Jeffrey T; Tantilov, Emil S >Cc: da...@davemloft.net; netdev@vger.kernel.org; Schmitt, Phillip J; intel- >wired-...@lists.osuosl.org >Subject

RE: e1000 driver and samba

I ran a test here in the lab and was not able to reproduce the issue you're describing. My setup is with 2 systems connected through a 100Mbit switch. Client runs Windows XP and the server is Linux RHEL5 with updated samba 3.0.26a (latest I could download from samba.org). I was able to copy 1GB

RE: 2.6.21rc7 e1000 media-detect oddness.

Dave Jones wrote: I booted up 2.6.21rc7 without an ethernet cable plugged in, and noticed this.. e1000: :02:00.0: e1000_probe: The EEPROM Checksum Is Not Valid e1000: probe of :02:00.0 failed with error -5 I plugged a cable in, did rmmod e1000;modprobe e1000, and got this..

RE: pci-e e1000 not responding to ARPs sometimes?

Sorry for the top post. I believe this is a known issue and it was fixed in the kernel driver as well (maybe it didn't make it into FC5 kernel?). See the following: http://article.gmane.org/gmane.linux.network/52168/match=e1000+factps+mn gcg If I'm not mistaken, the part relevant to your