From: Keith Busch <keith.busch@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
linux-kernel@vger.kernel.org
Subject: [BUG] cc5b114dcf bpf, i40e: add meta data support
Date: Tue, 12 Jun 2018 10:17:39 -0600 [thread overview]
Message-ID: <20180612161739.GA3303@localhost.localdomain> (raw)
My server's i40e no longer obtains an IP address on linux
mainline. Bisected to the following:
commit cc5b114dcf986bfd8e4c37bf65d1b7b1e5290ac6
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon May 28 11:07:20 2018 +0200
bpf, i40e: add meta data support
Reverting on mainline resolves the issue.
Is there something wrong with my i40e adapter, or is the patch possibly
doing something wrong? Or any other information I can get to help
understand why it's stopped working with this feature?
An excert from "journalctl -xe" on on the failing network adapter
is below.
Thanks,
Keith
---
Jun 12 10:04:35 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 7 (xid=0x3b301712)
Jun 12 10:04:42 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 14 (xid=0x3b301712)
Jun 12 10:04:56 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 21 (xid=0x3b301712)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn> [1528819503.2274] dhcp4 (eno1): request timed out
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2275] dhcp4 (eno1): state changed unknown -> timeout
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2440] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 2632
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2441] dhcp4 (eno1): state changed timeout -> done
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2445] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2448] manager: NetworkManager state is now DISCONNECTED
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn> [1528819503.2452] device (eno1): Activation: failed for connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2460] device (eno1): state change: failed -> disconnected (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2498] policy: auto-activating connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2517] device (eno1): Activation: starting connection 'Wired connection 1' (16a13ab5-c51e-361b-90bc-b6fc6f84cbe9)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2520] device (eno1): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2523] manager: NetworkManager state is now CONNECTING
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2529] device (eno1): state change: prepare -> config (reason 'none', internal state 'managed')
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
linux-kernel@vger.kernel.org
Subject: [BUG] cc5b114dcf bpf, i40e: add meta data support
Date: Tue, 12 Jun 2018 10:17:39 -0600 [thread overview]
Message-ID: <20180612161739.GA3303@localhost.localdomain> (raw)
My server's i40e no longer obtains an IP address on linux
mainline. Bisected to the following:
commit cc5b114dcf986bfd8e4c37bf65d1b7b1e5290ac6
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon May 28 11:07:20 2018 +0200
bpf, i40e: add meta data support
Reverting on mainline resolves the issue.
Is there something wrong with my i40e adapter, or is the patch possibly
doing something wrong? Or any other information I can get to help
understand why it's stopped working with this feature?
An excert from "journalctl -xe" on on the failing network adapter
is below.
Thanks,
Keith
---
Jun 12 10:04:35 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 7 (xid=0x3b301712)
Jun 12 10:04:42 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 14 (xid=0x3b301712)
Jun 12 10:04:56 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 21 (xid=0x3b301712)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn> [1528819503.2274] dhcp4 (eno1): request timed out
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2275] dhcp4 (eno1): state changed unknown -> timeout
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2440] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 2632
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2441] dhcp4 (eno1): state changed timeout -> done
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2445] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2448] manager: NetworkManager state is now DISCONNECTED
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn> [1528819503.2452] device (eno1): Activation: failed for connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2460] device (eno1): state change: failed -> disconnected (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2498] policy: auto-activating connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2517] device (eno1): Activation: starting connection 'Wired connection 1' (16a13ab5-c51e-361b-90bc-b6fc6f84cbe9)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2520] device (eno1): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2523] manager: NetworkManager state is now CONNECTING
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info> [1528819503.2529] device (eno1): state change: prepare -> config (reason 'none', internal state 'managed')
next reply other threads:[~2018-06-12 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 16:17 Keith Busch [this message]
2018-06-12 16:17 ` [BUG] cc5b114dcf bpf, i40e: add meta data support Keith Busch
2018-06-12 20:24 ` Daniel Borkmann
2018-06-25 12:24 ` [Intel-wired-lan] [Intel-gfx] " Jani Nikula
2018-06-25 12:24 ` Jani Nikula
2018-06-14 14:17 ` ✗ Fi.CI.BAT: failure for " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180612161739.GA3303@localhost.localdomain \
--to=keith.busch@linux.intel.com \
--cc=daniel@iogearbox.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.