netdev - Re: [PATCH net-next v1 0/9] Ethernet Cable test support

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 linux-cve-announce 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, 30 Apr 2020 21:44:12 +0200
From:   Michael Walle <michael@...le.cc>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     cphealy@...il.com, davem@...emloft.net, f.fainelli@...il.com,
        hkallweit1@...il.com, mkubecek@...e.cz, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v1 0/9] Ethernet Cable test support

Am 2020-04-30 20:23, schrieb Andrew Lunn:
>> Ok. I do have one problem. TDR works fine for the AR8031 and the
>> BCM54140 as long as there is no link partner, i.e. open cable,
>> shorted pairs etc. But as soon as there is a link partner and a
>> link, both PHYs return garbage. As far as I understand TDR, there
>> must not be a link, correct?
> 
> Correct.
> 
> The Marvell PHY will down the link and then wait 1.5 seconds before
> starting TDR, if you set a bit. I _think_ it downs the link by turning
> off autoneg.

According to the Atheros datasheet the "CDT can be performed when
there is no link partner or when the link partner is auto-negotiating".
One could interpret that as is is only allowed _during_ autoneg. But
as far as I know there is no indication if autoneg is currently active,
is it?

> Maybe there is some hints in 802.3 clause 22?

I'm just skimming over that, but even if the link could be disabled
locally, shouldn't there still be link pulses from the peer?

-michael