netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 203769] New: Regression: Valid network link no longer detected
Date: Sat, 1 Jun 2019 06:26:51 -0700	[thread overview]
Message-ID: <20190601062651.2d82b819@xps13> (raw)

Details are a bit scarce. 

The referenced commit is.

commit 7dc2bccab0ee37ac28096b8fcdc390a679a15841
Author: Maxim Mikityanskiy <maximmi@mellanox.com>
Date:   Tue May 21 06:40:04 2019 +0000

    Validate required parameters in inet6_validate_link_af

Begin forwarded message:

Date: Sat, 01 Jun 2019 09:53:51 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 203769] New: Regression: Valid network link no longer detected


https://bugzilla.kernel.org/show_bug.cgi?id=203769

            Bug ID: 203769
           Summary: Regression: Valid network link no longer detected
           Product: Networking
           Version: 2.5
    Kernel Version: 5.2.0-rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: gwhite@kupulau.com
        Regression: No

Commit 7dc2bccab0ee37ac28096b8fcdc390a679a15841 has broken wired networking on
two of my machines.  Drivers e1000e, igb and r8169 all fail to detect link with
this commit applied.  The drivers load and appear to initialize correctly, but
no link is ever detected.

With this commit reverted, they work perfectly.

This is on a fully updated Arch.  Happy to provide any other information that
is of use.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2019-06-01 13:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190601062651.2d82b819@xps13 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).