netdev - Marvell 88E1512 cable test tdr timeout

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <ea3dcffe-d7a9-48d2-975c-75b7b20ee3d4@seoss.co.uk>
Date: Thu, 21 Nov 2024 16:33:11 +0000
From: Tim Small <tim@...ss.co.uk>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org
Subject: Marvell 88E1512 cable test tdr timeout

Hi Andrew,

Thanks for contributing your work on cable test to the kernel.

I'm trying to use the TDR cable test functionality using the Marvell 
88E1512 PHY which is included in a wifi access point.

When I run:

ethtool --cable-test-tdr eth1

I get no results, and the kernel log includes:

Marvell 88E1510 mdio.1:01: Timeout while waiting for cable test to finish

The wifi access point is running OpenWrt snapshot v6.6.61
  (Huawei AP5030DN) and has a MIPS 74Kc V5.0 based SoC.

Since support for this device is not in the mainline kernel, I cannot 
easily run mainline, but I've diffed the OpenWrt tree against 
net-next/main and can't see any changes to drivers/net/phy/marvell.c 
which which look like they would have changed the tdr test path, and 
could attempt to run mainline if that would be useful.

The markings on the physical chip are:

88E1512-NNP2
NNR3880.5JW
1442 A0P
TW

I can't find the programming manual online (I assume it's NDAed?) so I 
can't check to see if there are any differences between the 88E1512 and 
the 88E1510, or errata etc.

I tried increasing the hard-coded poll number in 
marvell_vct5_wait_complete(), but I just get a watchdog reset in that case.

Any hints or tips gratefully received.

Cheers,

Tim.