Realtek ethernet not functional on 4.15.0-29.31

[Wajuz Donny]

When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere.

This issue only shows up in 4.15.0-29.31. I tried the following versions without issue:
1) 4.18.0-041800rc7
2) 4.16.0-041600
3) 4.15.0-23
4) 4.15.0-20

No issue on wifi (Intel 7260 iwlwifi), USB ethernet (Dell D3100 Dock) and USB ethernet (generic adapter using r8152 driver).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: daniel 1771 F.... pulseaudio
 /dev/snd/controlC0: daniel 1771 F.... pulseaudio
CurrentDesktop: MATE
Date: Tue Jul 31 14:42:31 2018
HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6
InstallationDate: Installed on 2018-07-08 (22 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron 7537
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 07PF9F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: Shark Bay ULT
dmi.product.name: Inspiron 7537
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7

[Wajuz Donny (wajuzdonny)]

This issue only happens in 4.15.0-29.31. No issue on prior versions (i.e. 4.15.0-23 and 4.15.0-20). No issue on latest upstream kernel 4.18.0-041800rc7. No issue on 4.16.0-041600.

[Steve Dodd (anarchetic)]

Is this even from a cold boot? Similar issues being discussed at bug #1779817 and bug #1752772 but that is only after suspension.

[Wajuz Donny (wajuzdonny)]

Yes, from a cold boot.

[Wajuz Donny (wajuzdonny)]

I tried 4.15.0-24.26, but no login screen.

[Kai-Heng Feng (kaihengfeng)]

Please try this kernel:
https://people.canonical.com/~khfeng/bionic-r8169-backport/

[Wajuz Donny (wajuzdonny)]

Just tried the kernel. Ethernet (r8169) and USB ethernet (r8152) are not shown in ifconfig. With ubuntu kernel, ethernet at least shows up there and USB ethernet is functional.
wifi is functional in both ubuntu and khfeng kernel.

[Léon Hagenaars-Keus (hagenaarsdotnu)]

Issue still exists in 4.15.0-30.32

[Kai-Heng Feng (kaihengfeng)]

Please try this one instead:
https://people.canonical.com/~khfeng/bionic-r8169-backport2/

[Wajuz Donny (wajuzdonny)]

Thanks. This issue is resolved on that kernel.

[Wajuz Donny (wajuzdonny)]

I've been using https://people.canonical.com/~khfeng/bionic-r8169-backport2/ for a week now, no issue so far.

[Léon Hagenaars-Keus (hagenaarsdotnu)]

Issue seems to be resolved in 4.15.0-33.36.
Thanks to everyone involved.