Bug 25305 - systemd-networkd does NOT bring up network interfaces when run under kernel 5.2.7
Summary: systemd-networkd does NOT bring up network interfaces when run under kernel 5...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK, MGA7-32-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2019-08-14 11:30 CEST by PC LX
Modified: 2019-09-15 14:13 CEST (History)
5 users (show)

See Also:
Source RPM: systemd-241-8.1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description PC LX 2019-08-14 11:30:38 CEST
Description of problem:

systemd-networkd does NOT bring up network interfaces when run under kernel 5.2.7.

I have to manually bring up the network links (e.g. ip link set enp1s0 up) for systemd-networkd to work.

This may be the issue I'm experiencing.
https://github.com/systemd/systemd/issues/12784



Version-Release number of selected component (if applicable):

$ rpm -q systemd
systemd-241-8.1.mga7



How reproducible:

Always.



Steps to Reproduce:
1. Boot kernel 5.1.20-desktop-2.mga7
2. Use systemd-networkd to setup the network interfaces. This is system dependent.
3. Open a terminal, and as root check the network interfaces state with "ip a" and see that they are in state "UP".
4. Test networks (e.g. use ping). Should succeed.
5. Boot kernel 5.2.7-desktop-1.mga7
6. Open a terminal, and as root check the network interfaces state with "ip a" and see that they are in state "DOWN".
7. Test networks (e.g. use ping). Should FAIL.
8. In the same terminal, as root, use the command "ip link set DEV up" to bring up the devices.
9. Test networks (e.g. use ping). Should succeed.

$ journalctl -b-1 | grep -i "linux version"
ago 13 18:43:20 marte kernel: Linux version 5.2.7-desktop-1.mga7 (iurt@rabbit.mageia.org) (gcc version 8.3.1 20190524 (Mageia 8.3.1-0.20190524.1.mga7)) #1 SMP Wed Aug 7 10:32:19 UTC 2019
$ journalctl -b0 | grep -i "linux version"
ago 14 09:27:46 marte kernel: Linux version 5.1.20-desktop-2.mga7 (iurt@rabbit.mageia.org) (gcc version 8.3.1 20190524 (Mageia 8.3.1-0.20190524.1.mga7)) #1 SMP Fri Jul 26 23:04:19 UTC 2019
Comment 1 Thomas Backlund 2019-08-14 11:58:23 CEST
Most likely yes.

I've just submitted systemd-241-8.2.mga7 with fixes for that and various other fixes including memleak fixes and some documentation updates

CC: (none) => tmb

Comment 2 Lewis Smith 2019-08-14 21:02:35 CEST
Thank you PC-LX for all the helpful details you provided.
And Thomas for your immediate & encouraging response. That should filter through as a regular update.
Assigning to Base system maintainers; hope this is appropriate.

Assignee: bugsquad => basesystem

Comment 3 PC LX 2019-08-20 11:35:06 CEST
Installed the updates for systemd and kernel and the issue seems resolved.

Since it is a critical package, will wait for more testing before giving OK.


The network interfaces are automatically and properly setup and no manual action is needed.
The network devices include:
- HW Realtek ethernet device;
- macvlan devices for systemd-nspawn containers;
- sit device for IPv6 over IPv4;
- bridge for qemu/kvm virtual machines.


System: Mageia 6, x86_64, Intel CPU, Realtek ethernet device using the r8169 driver.


$ uname -a
Linux marte 5.2.9-desktop-1.mga7 #1 SMP Sat Aug 17 20:48:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -q systemd
systemd-241-8.2.mga7
$ rpm -qa | grep 241 | sort -u
lib64systemd0-241-8.2.mga7
lib64udev1-241-8.2.mga7
lib64udev-devel-241-8.2.mga7
libsystemd0-241-8.2.mga7
libudev1-241-8.2.mga7
nss-myhostname-241-8.2.mga7
systemd-241-8.2.mga7
systemd-devel-241-8.2.mga7
systemd-units-241-8.2.mga7
$ lspcidrake | grep -i ethernet
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (rev: 11)
Comment 4 Muhammad Tailounie 2019-08-22 15:16:27 CEST
I updated SystemD from testing and the bug is fixed.

Systemd version 241 release 8.2.mga7

CC: (none) => mageia

Comment 5 Julien Moragny 2019-08-30 21:12:52 CEST
I confirm the updated systemd from testing fix this bug (on x86_64 and i586). 

I'm using it for a week now without issue.

regards
julien

CC: (none) => julien.moragny

Comment 6 Levchenko Roman 2019-09-14 22:48:36 CEST
Unfortunately, I can't confirm the bug fixing.
Installed packages:
systemd-241-8.2.mga7
lib64systemd0-241-8.2.mga7
lib64udev1-241-8.2.mga7
lib64udev-devel-241-8.2.mga7
libsystemd0-241-8.2.mga7
nss-myhostname-241-8.2.mga7

Ethernet cards:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 17
        I/O ports at ee00 [size=256]
        Memory at fdbff000 (64-bit, prefetchable) [size=4K]
        Memory at fdbe0000 (64-bit, prefetchable) [size=64K]
        [virtual] Expansion ROM at fdc00000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 12-34-56-78-12-34-56-78
        Kernel driver in use: r8169
        Kernel modules: r8169
motherboard Gigabyte EP45-UD3LR with onboard Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller - it doesn't work even after module r8169 reload, so it disconnected

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
        I/O ports at de00 [size=256]
        Memory at fddff000 (32-bit, non-prefetchable) [size=256]
        [virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
        Kernel driver in use: r8169
        Kernel modules: r8169
the second card - expansion card RTL8169 PCI Gigabit Ethernet Controller, this card starts work after module r8169 reload 

So. now I have to use rc.local with rmmode-modprobe about r8169, because Ethernet Controllers don't work nominally.

Maybe I'm doing something wrong?

Thanks.

CC: (none) => rim33377

Comment 7 Thomas Backlund 2019-09-15 11:28:41 CEST
Seems I forgot to assign this to QA, but since it's confirmed fixed in comments 3, 4 and 5 and alsh has been in Cauldron for a month its very well tested.

The issue in comment 6 is not a systemd-networkd issue, it's an issue with the r8169 driver.

So assinging and validating at the same time.

Advisory, added to svn:

type: bugfix
subject: Updated systemd packages fix networkd issues with 5.2 series kernels
src:
  7:
   core:
     - systemd-241-8.2.mga7
description: |
  A change in kernel 5.2 series causes systemd-networkd to fail to bring up
  network links, instead it just failed with the error: "Could not bring up
  interface: Invalid argument". This update fixes that.
  This update also fixes some memleak issues, and adds some documentation
  updates.
references:
 - https://bugs.mageia.org/show_bug.cgi?id=25305

Whiteboard: (none) => MGA7-64-OK, MGA7-32-OK
Keywords: (none) => advisory, validated_update
Assignee: basesystem => qa-bugs
CC: (none) => sysadmin-bugs

Comment 8 Mageia Robot 2019-09-15 14:13:03 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0126.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.