Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-1552

tcpdump(IPv4 TSO): captured 0 packets

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ovs-dpdk
    • None
    • tcpdump(IPv4 TSO): captured 0 packets
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      ( ) The epics work is available in a downstream build (nightly/Async or other)

      ( ) All cards under the epic have been moved to Done

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. ( ) The epics work is available in a downstream build (nightly/Async or other) ( ) All cards under the epic have been moved to Done
    • rhel-9
    • rhel-net-ovs-dpdk
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the bug described below.

       Problem Description: Clearly explain the issue.

      TSO failed on OVS 3.1 on RHEL9.2 for 25.D
      Job URL:
      https://beaker.engineering.redhat.com/jobs/11395911

      rtt min/avg/max/mdev = 0.422/0.484/0.626/0.073 ms
TCP4 trial 0
iperf3: error - unable to send control message: Bad file descriptor
TCP4 trial 1
iperf3: error - unable to send control message: Bad file descriptor
TCP4 trial 2
iperf3: error - unable to send control message: Bad file descriptor
TCP4 trial 3
iperf3: error - unable to send control message: Bad file descriptor
TCP4 trial 4
iperf3: error - unable to send control message: Bad file descriptor
TCP4 rate=0 Gbps, baseline=8
FAIL: iperf3 -c 192.168.123.2 -p 11111
cat: /sys/class/net/ens2f0/speed: No such file or directory
UDP4 trial 0
iperf3: error - unable to send control message: Bad file descriptor
UDP4 trial 1
iperf3: error - unable to send control message: Bad file descriptor
UDP4 trial 2
iperf3: error - unable to send control message: Bad file descriptor
UDP4 trial 3
iperf3: error - unable to send control message: Bad file descriptor
UDP4 trial 4
iperf3: error - unable to send control message: Bad file descriptor
UDP4 rate=0 Gbps, baseline=1
FAIL: iperf3 -u -b M -c 192.168.123.2 -p 11111
tcpdump(IPv4 TSO): captured 0 packets

       Impact Assessment: Describe the severity and impact (e.g., network down,availability of a workaround, etc.).

       

       Software Versions: Specify the exact versions in use (e.g.,openvswitch3.1-3.1.0-147.el8fdp).

       

        Issue Type: Indicate whether this is a new issue or a regression (if a regression, state the last known working version).

      ovs_version: "3.1.8-157.el9fdp"
       

       Reproducibility: Confirm if the issue can be reproduced consistently. If not, describe how often it occurs.

       Yes, tried running 2 times

       Reproduction Steps: Provide detailed steps or scripts to replicate the issue.

      Run TSO test
       

       Expected Behavior: Describe what should happen under normal circumstances.

       Should not fail

       Observed Behavior: Explain what actually happens.

       

       Troubleshooting Actions: Outline the steps taken to diagnose or resolve the issue so far.

       

       Logs: If you collected logs please provide them (e.g. sos report, /var/log/openvswitch/* , testpmd console)

              ovsdpdk-bot ovsdpdk bot
              rhn-support-arbansal Arun Bansal
              Arun Bansal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: