From: kernel test robot <oliver.sang@intel.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
<netdev@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [rtnetlink] 8c6540cb2d: hwsim.mesh_sae_failure.fail
Date: Fri, 14 Jun 2024 16:48:59 +0800 [thread overview]
Message-ID: <202406141644.c05809af-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "hwsim.mesh_sae_failure.fail" on:
commit: 8c6540cb2d020c59b6f7013a2e8a13832906eee0 ("rtnetlink: print rtnl_mutex holder/waiter for debug purpose")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 6906a84c482f098d31486df8dc98cead21cce2d0]
in testcase: hwsim
version: hwsim-x86_64-07c9f183e-1_20240402
with following parameters:
test: mesh_sae_failure
compiler: gcc-13
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4790 v3 @ 3.60GHz (Haswell) with 6G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202406141644.c05809af-oliver.sang@intel.com
group: group-20, test: mesh_sae_failure
2024-06-14 04:11:22 export USER=root
2024-06-14 04:11:22 ./build.sh
Building TNC testing tools
Building wlantest
Building hs20-osu-client
Building hostapd
Building wpa_supplicant
2024-06-14 04:12:20 ./start.sh
2024-06-14 04:12:24 ./run-tests.py mesh_sae_failure
DEV: wlan0: 02:00:00:00:00:00
DEV: wlan1: 02:00:00:00:01:00
DEV: wlan2: 02:00:00:00:02:00
APDEV: wlan3
APDEV: wlan4
START mesh_sae_failure 1/1
Test: Mesh and local SAE failures
Pending failures at time of exception: 0:auth_sae_init_committed;mesh_rsn_auth_sae_sta
Test exception: Remote peer did not connect.
Traceback (most recent call last):
File "/lkp/benchmarks/hwsim/tests/hwsim/./run-tests.py", line 591, in main
t(dev, apdev)
File "/lkp/benchmarks/hwsim/tests/hwsim/test_wpas_mesh.py", line 1942, in test_mesh_sae_failure
check_mesh_connected2(dev)
File "/lkp/benchmarks/hwsim/tests/hwsim/test_wpas_mesh.py", line 136, in check_mesh_connected2
check_mesh_peer_connected(dev[1])
File "/lkp/benchmarks/hwsim/tests/hwsim/test_wpas_mesh.py", line 122, in check_mesh_peer_connected
raise Exception("Test exception: Remote peer did not connect.")
Exception: Test exception: Remote peer did not connect.
FAIL mesh_sae_failure 41.682039 2024-06-14 04:13:15.904346
passed 0 test case(s)
skipped 0 test case(s)
failed tests: mesh_sae_failure
2024-06-14 04:13:15 ./stop.sh
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240614/202406141644.c05809af-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-06-14 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 8:48 kernel test robot [this message]
2024-06-14 9:34 ` Tetsuo Handa
2024-06-17 6:12 ` Oliver Sang
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=202406141644.c05809af-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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