DescriptionDmitry Burstein
2018-06-28 01:54:05 UTC
Description of problem:
I have a 'team0' interface comprised of two on-board NICs. When booting into 4.17.2, the machine has no network connection. When booting back into 4.16.16 or earlier - there is absolutely no problem with it.
Trying to bring it up in 4.17.2 with 'nmcli' command succeeds only partially, as the network remains very slow and virtually unusable. Bringing up the individual NICs - not as parts of the team0 - gets the regular network performance back.
Version-Release number of selected component (if applicable):
kernel-4.17.2-200
How reproducible:
Every time I'm trying to boot into this kernel version.
Steps to Reproduce:
1. Choose kernel-4.17.2-200 as a boot option.
2. Wait for the machine to boot up.
3. Run 'nmcli c s' to see the network is down.
Actual results:
The network is down.
Expected results:
Working networking.
Additional info:
Unfortunately I have no idea how to make any future diagnostics, but I'm willing to perform it if instructed.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
If you experience different issues, please open a new bug report for those.