Date: Mon, 10 Apr 2017 16:50:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable. Message-ID: <bug-211219-2472-kF32ljxY1i@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211219-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-211219-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211219 --- Comment #16 from Franco Fichtner <franco@opnsense.org> --- I'm not so sure. All branches received a modified patch that came up inconclusive in testing, overshadowed by the iflib conversion and multiple build and subsystem failures due to it. We circled around a minimal patch (note the attached patch reverts to the full Intel driver change), but the weirdness that is "adapter->ims" for just this one chipset code path still makes no sense in the grand scheme of things. I asked for a full revert to the working Intel state via e-mail, but that didn't happen. I don't think this is sensible for the simple reason that this was introduc= ed in stable/10, went into 10.3 unnoticed, breaking *a lot* of embedded hardwa= re with regard to e.g. CARP, then went into 11.0. It took a long time to iden= tify the commit that was responsible and unwind it (it was a batch MFC after all= ). Settling for anything other than what is attached to this ticket is risky, especially if there is nobody who can test and verify this in over one and a half years. Cheers, Franco --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211219-2472-kF32ljxY1i>