netdev - Stuck TX Using Iperf

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>] [day] [month] [year] [list]

Message-ID: <CALAE=UDTbr8u0kPcEA3mLL+CMBxUOexvON8tdV2QxKyCeHFwRw@mail.gmail.com>
Date:   Wed, 16 Aug 2017 10:46:53 -0700
From:   Robert Jones <rjones@...eworks.com>
To:     netdev@...r.kernel.org, sgoutham@...ium.com, rric@...nel.org
Cc:     Tim Harvey <tharvey@...eworks.com>
Subject: Stuck TX Using Iperf

Hello Cavium Ethernet Driver Maintainers,

I'm working on a custom board using a Cavium OcteonTX CN80XX cpu
running a mainline 4.12.7 kernel and I've run into a problem where the
TX of my BGX0 configured for SGMII becomes stuck.

After boot I'm able to bring the interface up, run dhclient, and ping
a host machine with no issues. However, every time that I try to run
an iperf TCP test I get a stuck TX queue. Bringing the interface down
and then up does not resolve the problem, but physically reconnecting
the cable connected to the interface does. Also, after I reconnect the
cable I am no longer able to reproduce the stuck TX queue until
reboot. I receive no kernel driver messages of any sort during my
iperf test, it just stalls until I kill it.

Any help would be appreciated.

Regards,

Robert Jones - Software Engineer
Gateworks Corporation