From: kernel test robot <oliver.sang@intel.com>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Johannes Berg <johannes.berg@intel.com>,
<linux-wireless@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [wifi] 43ef5856bd: hwsim.nan_sync_srf_mac_addr_8.fail
Date: Mon, 11 May 2026 22:00:35 +0800 [thread overview]
Message-ID: <202605112140.63585f81-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "hwsim.nan_sync_srf_mac_addr_8.fail" on:
commit: 43ef5856bdab300acc90ea2c3c437f5535a5f66f ("wifi: mac80211: track the id of the NAN cluster we joined")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 17c7841d09ee7d33557fd075562d9289b6018c90]
in testcase: hwsim
version: hwsim-x86_64-d255d20c8-1_20260426
with following parameters:
test: group-30
config: x86_64-rhel-9.4-func
compiler: gcc-14
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/202605112140.63585f81-lkp@intel.com
2026-05-08 01:31:52 ./run-tests.py nan_sync_srf_mac_addr_8
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 nan_sync_srf_mac_addr_8 1/1
Test: NAN synchronized active subscribe and solicited publish with MAC address in SRF
NAN capabilities: USD NAN
NAN device starting on nan0
Setting master_pref to 10 on nan0
Setting dual_band to 0 on nan0
NAN device started on nan0
NAN capabilities: USD NAN
NAN device starting on nan1
Setting master_pref to 10 on nan1
Setting dual_band to 0 on nan1
NAN device started on nan1
Cancelling publish with ID 1 on nan0
Cancelling subscribe with ID 1 on nan1
NAN device stopping on nan1
NAN device stopped on nan1
NAN device stopping on nan0
NAN device stopped on nan0
Exception during test execution: NAN-DISCOVERY-RESULT event not seen
Traceback (most recent call last):
File "/lkp/benchmarks/hwsim/tests/hwsim/./run-tests.py", line 633, in main
t(dev, apdev, params)
~^^^^^^^^^^^^^^^^^^^^
File "/lkp/benchmarks/hwsim/tests/hwsim/test_nan.py", line 665, in test_nan_sync_srf_mac_addr_8
_nan_sync_srf(wpas2, pub, srf_include=0, srf_mac_list=srf)
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/lkp/benchmarks/hwsim/tests/hwsim/test_nan.py", line 560, in _nan_sync_srf
raise Exception("NAN-DISCOVERY-RESULT event not seen")
Exception: NAN-DISCOVERY-RESULT event not seen
FAIL nan_sync_srf_mac_addr_8 3.097871 2026-05-08 01:31:55.539483
passed 0 test case(s)
skipped 0 test case(s)
failed tests: nan_sync_srf_mac_addr_8
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260511/202605112140.63585f81-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-11 14:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605112140.63585f81-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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