From: Stephen Hemminger <stephen@networkplumber.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org
Subject: No address after suspend/resume with 4.18
Date: Fri, 30 Nov 2018 15:26:15 -0800 [thread overview]
Message-ID: <20181130152615.6082a4da@xeon-e3> (raw)
On my box with Debian testing, I see a new problem with suspend/resume of wired network device.
Using stock Debian kernel 4.18.0-2-amd64
After suspend/resume cycle, IP address is lost.
Device Info:
$ /sbin/ethtool -i enp12s0
driver: igb
version: 5.4.0-k
firmware-version: 0. 6-1
expansion-rom-version:
bus-info: 0000:0c:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
$ lspci -v -s 0000:0c:00.0
0c:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
Subsystem: Gigabyte Technology Co., Ltd I211 Gigabit Network Connection
Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
Memory at dfb00000 (32-bit, non-prefetchable) [size=128K]
I/O ports at c000 [size=32]
Memory at dfb20000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: igb
Kernel modules: igb
State before suspend:
$ ip addr show dev enp12s0
4: enp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 1c:1b:0d:0a:4b:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.18/24 brd 192.168.1.255 scope global enp12s0
valid_lft forever preferred_lft forever
State after resume:
$ ip addr show dev enp12s0
4: enp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 1c:1b:0d:0a:4b:0e brd ff:ff:ff:ff:ff:f
Doing ifdown/ifup which restarts the DHCP client does restore the address.
Not sure if this is a kernel issue with carrier handling, Intel driver issue, or DHCP client issue.
next reply other threads:[~2018-12-01 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:26 Stephen Hemminger [this message]
2018-11-30 23:34 ` No address after suspend/resume with 4.18 Jeff Kirsher
2018-12-03 21:19 ` Jeff Kirsher
2018-12-03 21:45 ` Stephen Hemminger
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=20181130152615.6082a4da@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).