Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Network bonding driver fails to enable interface, spams log #2374

Open
bgilbert opened this issue Feb 28, 2018 · 1 comment
Open

Network bonding driver fails to enable interface, spams log #2374

bgilbert opened this issue Feb 28, 2018 · 1 comment
Labels
area/stability component/kernel kind/bug platform/packet team/os

Comments

@bgilbert
Copy link
Contributor

Issue Report

Bug

Container Linux Version

$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1702.0.0
VERSION_ID=1702.0.0
BUILD_ID=2018-02-27-2252
PRETTY_NAME="Container Linux by CoreOS 1702.0.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

Packet

Expected Behavior

Working network.

Actual Behavior

On some boots, networking is unreliable. The kernel log gets a message every 2 ms:

[   25.825677] bond0: Enslaving enp0s20f1 as an active interface with a down link
[   26.019325] bond0: Enslaving enp0s20f0 as an active interface with a down link
[   26.577183] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.606606] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[   26.608367] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.610047] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.612053] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.614050] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.616050] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.618050] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.620050] bond0: link status up for interface enp0s20f0, enabling it in 0 ms
[   26.622050] bond0: link status up for interface enp0s20f0, enabling it in 0 ms

Reproduction Steps

  1. Boot Container Linux on a Packet type 1 instance.

Other Information

Related to, but seemingly not the same as, #2065.
@bgilbert bgilbert added jira Makes a copy of an issue onto a Jira card. and removed maintenance labels Jun 14, 2018
@vielmetti
Copy link

I'm seeing something related:

** 11 printk messages dropped ** [  737.350162] bond0: link status down for interface enp1s0f0, disabling it in 200 ms
** 11 printk messages dropped ** [  737.362157] bond0: link status down for interface enp1s0f0, disabling it in 200 ms
** 11 printk messages dropped ** [  737.374152] bond0: link status down for interface enp1s0f0, disabling it in 200 ms
** 13 printk messages dropped ** [  737.388148] bond0: link status down for interface enp1s0f0, disabling it in 200 ms
** 9 printk messages dropped ** [  737.398143] bond0: link status down for interface enp1s0f0, disabling it in 200 ms
** 13 printk messages dropped **

also on Packet.

@vielmetti vielmetti mentioned this issue Oct 12, 2018
Open
@dustymabe dustymabe removed the jira Makes a copy of an issue onto a Jira card. label Sep 5, 2019
pothos added a commit to flatcar/mantle that referenced this issue Mar 19, 2020
@pothos
Increase threshold for bonding check
d6db5ad 
After coreos/bugs#2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
coreos/bugs#2374.

However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
For now, just increase the threshold.
pothos added a commit to flatcar/mantle that referenced this issue Mar 19, 2020
@pothos
Increase threshold for bonding check
1cbb9e2 
After coreos/bugs#2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
coreos/bugs#2374.

However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
For now, just increase the threshold.
pothos added a commit to flatcar/mantle that referenced this issue Mar 19, 2020
@pothos
Increase threshold for bonding check
9c49a63 
After coreos/bugs#2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
coreos/bugs#2374.

However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
For now, just increase the threshold.
pothos added a commit to flatcar/mantle that referenced this issue Mar 19, 2020
@pothos
Improve bonding check and lower threshold
97b57fb 
After coreos/bugs#2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
coreos/bugs#2374.

However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
Add a second match for these messages that skips
the test. Also lower the threshold to see if the
logic works well.
@pothos pothos mentioned this issue Mar 19, 2020
Merged
pothos added a commit to flatcar/mantle that referenced this issue Mar 20, 2020
@pothos
Improve bonding check and lower threshold
20d03d7 
After coreos/bugs#2065
a test for "excessive bonding link status messages"
was introduced which also is good to keep for
coreos/bugs#2374.

However, having this message printed 10 times
does not directly relate to an error.
The test should check if something like
'bond0: Gained carrier' or
'link status definitely up for interface enp0s20f0'
is coming at the end and then continue.
Add a second match for these messages that skips
the test. Also lower the threshold to see if the
logic works well.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/stability component/kernel kind/bug platform/packet team/os
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vielmetti @bgilbert @dustymabe