lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 28 May 2020 17:40:10 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Petr Machata <petrm@...lanox.com>
Cc:     Amit Cohen <amitc@...lanox.com>, mlxsw <mlxsw@...lanox.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "o.rempel@...gutronix.de" <o.rempel@...gutronix.de>
Subject: Re: Link down reasons

> Andrew, pardon my ignorance in these matters, can a PHY driver in
> general determine that the issue is with the cable, even without running
> the fairly expensive cable test?

No. To diagnose a problem, you need the link to be idle. If the link
peer is sending frames, they interfere with TDR. So all the cable
testing i've seen first manipulates the auto-negotiation to make the
link peer go quiet. That takes 1 1/2 seconds. There are some
optimizations possible, e.g. if the cable is so broken it never
establishes link, you can skip this. But Ethernet tends to be robust,
it drops back to 100Mbps only using two pairs if one of the four pairs
is broken, for example.

   Andrew

Powered by blists - more mailing lists