On Thu, 14 May 2020 12:57:16 +0300 Igor Russkikh wrote: > FastLinQ devices as a complex systems may observe various hardware > level error conditions, both severe and recoverable. > > Driver is able to detect and report this, but so far it only did > trace/dmesg based reporting. > > Here we implement an extended hw error detection, service task > handler captures a dump for the later analysis. > > I also resubmit a patch from Denis Bolotin on tx timeout handler, > addressing David's comment regarding recovery procedure as an extra > reaction on this event. > > v2: > > Removing the patch with ethtool dump and udev magic. Its quite isolated, > I'm working on devlink based logic for this separately. > > v1: > > https://patchwork.ozlabs.org/project/netdev/cover/cover.1588758463.git.irussk...@marvell.com/
I'm not 100% happy that the debug data gets reported to the management FW before the devlink health code is in place. For the Linux community, I think, having standard Linux interfaces implemented first is the priority.
