From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: No address after suspend/resume with 4.18
Date: Fri, 30 Nov 2018 15:34:10 -0800
Message-ID: <472b642f6d248fcef91f81f07e159cadb4a9bfac.camel@intel.com>
References: <20181130152615.6082a4da@xeon-e3>
Reply-To: jeffrey.t.kirsher@intel.com
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256";
        protocol="application/pgp-signature"; boundary="=-6bvYfzAzZVC1sT7jwOZ3"
Cc: netdev@vger.kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mga05.intel.com ([192.55.52.43]:5694 "EHLO mga05.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725867AbeLAKoy (ORCPT <rfc822;netdev@vger.kernel.org>);
        Sat, 1 Dec 2018 05:44:54 -0500
In-Reply-To: <20181130152615.6082a4da@xeon-e3>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>


--=-6bvYfzAzZVC1sT7jwOZ3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2018-11-30 at 15:26 -0800, Stephen Hemminger wrote:
> 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
>=20
> After suspend/resume cycle, IP address is lost.
>=20
> Device Info:
> $ /sbin/ethtool -i enp12s0
> driver: igb
> version: 5.4.0-k
> firmware-version:  0. 6-1
> expansion-rom-version:=20
> bus-info: 0000:0c:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>=20
>=20
> $ 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=3D128K]
> 	I/O ports at c000 [size=3D32]
> 	Memory at dfb20000 (32-bit, non-prefetchable) [size=3D16K]
> 	Capabilities: <access denied>
> 	Kernel driver in use: igb
> 	Kernel modules: igb
>=20
> 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
>=20
> State after resume:
>=20
> $ 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
>=20
> Doing ifdown/ifup which restarts the DHCP client does restore the
> address.
>=20
> Not sure if this is a kernel issue with carrier handling, Intel
> driver issue, or DHCP client issue.

Thanks Stephen, I will have someone look into it.

--=-6bvYfzAzZVC1sT7jwOZ3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEiTyZWz+nnTrOJ1LZ5W/vlVpL7c4FAlwByPIACgkQ5W/vlVpL
7c7TTQ//fBTtRrCjtWBRJ5xQp0eO/2f0oCWn7O6PEStvJD+doS7816kLibAbl2gS
VAhyI4CqjABT1zqeS2pt4GHtywnt9LhoPXBfd2agOFBV3xjIO2Zy4eZbKyKroDpl
jxPMbSlJ5KqoRPG5A/WwfkwOe3i0ra2cP1OXjV27Yi55316mCXTT7THSdSZePaR2
vdW1a278mCo46IRn37SZgYI8Wt+w3Rugg7wYdes2cL8CzjiTuyHETyjE/M/zunUx
+EVaj3X9LiVUzxkZZC4GNlN+Q3DyBeXyGccoljWxq/aovpWkq7dCrFdifM48C54y
tR2TWKsRy2mIO4ldUiqOA3JgzgNR7AV+JANAeDq5exAL2Zyf5q3K8VJu/vil2mg1
CEylFkywZ8TM4gzNSF3JoFzOgkpc/jo32CvDyoAcUGJvPARISSt9Ozcsn30nvhNA
y5fNjqb7SRqj1/lRMrHWCJipOo2pFzSY1BNeQoEuotaNo/exUExCa4fXS4ZWcAGK
d0GyYJpIWVkIO5O0iG9xSscfhghY70gTlEahh/cBU7r9XYOfeOef+ogFiCt91Ism
BME0PO+g4LSF8jjUsiQ8ITqp5ju/bAsMav2mc892XRANoKXMO6LDPO0Dgp9ebv/T
XJ2jGTbtCx8YhJzWTMtRZvw0Z4NGnFDxN9HyPAAWXfXtuE2VYzA=
=Gl1A
-----END PGP SIGNATURE-----

--=-6bvYfzAzZVC1sT7jwOZ3--