netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Yunshui Jiang <jiangyunshui@kylinos.cn>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Lukasz Majewski <lukma@denx.de>,
	Geliang Tang <geliang@kernel.org>
Subject: [HSR] hsr_ping test failed
Date: Fri, 12 Sep 2025 03:04:36 +0000	[thread overview]
Message-ID: <aMONxDXkzBZZRfE5@fedora> (raw)

Hi, Sebastian, Yunshui,

I tried to run hsr_ping recently on x86_64 arch (build via vng --build
--config tools/testing/selftests/net/hsr/config, latest net branch,
iproute2-6.15.0) and the test always failed due to error
"Expect to send and receive 10 packets and no duplicates."

I checked the normal ping test and found it also has duplicates.
e.g.

PING 100.64.0.3 (100.64.0.3) 56(84) bytes of data.

--- 100.64.0.3 ping statistics ---
2 packets transmitted, 2 received, +3 duplicates, 0% packet loss, time 1012ms

I'm not sure if I missed some configurations or anything else. How do we make
sure there is not duplicates?

Another issue during my testing is that the test checks

        while [ ${WAIT} -gt 0 ]
        do
                grep 00:00:00:00:00:00 /sys/kernel/debug/hsr/hsr*/node_table
                if [ $? -ne 0 ]
                then
                        break
                fi
                sleep 1
                let "WAIT = WAIT - 1"
        done

While in my testing the debug log shows 00:00:00:00:00:00 for mac B address
during the whole 5 seconds.

/sys/kernel/debug/hsr/hsr1/node_table:00:11:22:00:02:01 00:00:00:00:00:00  10026a200,  100265ef5,              0,     1
/sys/kernel/debug/hsr/hsr1/node_table:00:11:22:00:02:02 00:00:00:00:00:00  100265ef5,  100269800,              0,     1
/sys/kernel/debug/hsr/hsr1/node_table:00:11:22:00:03:01 00:00:00:00:00:00  100266140,  10026a200,              0,     1
/sys/kernel/debug/hsr/hsr1/node_table:00:11:22:00:03:02 00:00:00:00:00:00  100269000,  100266140,              0,     1
/sys/kernel/debug/hsr/hsr2/node_table:00:11:22:00:01:01 00:00:00:00:00:00  100269000,  100265ef5,              0,     1
/sys/kernel/debug/hsr/hsr2/node_table:00:11:22:00:01:02 00:00:00:00:00:00  100265ef5,  100269000,              0,     1
/sys/kernel/debug/hsr/hsr2/node_table:00:11:22:00:03:02 00:00:00:00:00:00  100266140,  10026a200,              0,     1
/sys/kernel/debug/hsr/hsr2/node_table:00:11:22:00:03:01 00:00:00:00:00:00  10026a200,  100266140,              0,     1
/sys/kernel/debug/hsr/hsr3/node_table:00:11:22:00:01:02 00:00:00:00:00:00  100269000,  100265ef5,              0,     1
/sys/kernel/debug/hsr/hsr3/node_table:00:11:22:00:01:01 00:00:00:00:00:00  100265ef5,  100269000,              0,     1
/sys/kernel/debug/hsr/hsr3/node_table:00:11:22:00:02:02 00:00:00:00:00:00  100265ef5,  10026a200,              0,     1
/sys/kernel/debug/hsr/hsr3/node_table:00:11:22:00:02:01 00:00:00:00:00:00  10026a200,  100265f98,              0,     1

Thanks
Hangbin

             reply	other threads:[~2025-09-12  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12  3:04 Hangbin Liu [this message]
2025-09-21 19:33 ` [HSR] hsr_ping test failed Sebastian Andrzej Siewior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aMONxDXkzBZZRfE5@fedora \
    --to=liuhangbin@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=geliang@kernel.org \
    --cc=jiangyunshui@kylinos.cn \
    --cc=kuba@kernel.org \
    --cc=lukma@denx.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).