Thread (52 messages) 52 messages, 6 authors, 2016-01-29

Re: [PATCH 1/1] bonding: restrict up state in 802.3ad mode

From: Michal Kubecek <hidden>
Date: 2016-01-07 07:59:55

On Thu, Jan 07, 2016 at 03:37:26PM +0800, zhuyj wrote:
quoted
If I read this right, whenever this state (link up but speed/duplex
unknown) is entered, you'll keep writing this message into kernel log
every miimon milliseconds until something changes. I'm not sure how long
a NIC can stay in such state but it might get quite annoying (even more
if something really goes wrong and NIC stays that way which can't be
completely ruled out, IMHO).
Sure, Thanks a lot. I want to confirm link_up without link_speed. It
is not usual. So I think this only lasts for several seconds.
It is very important to us since it can help us to find the root cause.
For debugging purposes it's fine, of course. But this looked like an
officially submitted patch so I didn't like the idea of log spamming
(even one second could result in 10-100 messages and admins certainly
would hate that).

                                                       Michal Kubecek
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help