From: kernel test robot <oliver.sang@intel.com>
To: Deepanshu Kartikey <kartikey406@gmail.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] dd40677999: hwsim.pmksa_cache_preauth_vlan_used.fail
Date: Fri, 31 Jul 2026 21:15:36 +0800 [thread overview]
Message-ID: <202607311514.d263d952-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "hwsim.pmksa_cache_preauth_vlan_used.fail" on:
commit: dd406779999fa2065ec6b7c4f80906b727041d2c ("wifi: mac80211: don't encrypt pre-auth (ETH_P_PREAUTH) frames")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 3652b49adac266a3d27cb41cdfdb7d8790fc3633]
in testcase: hwsim
version: hwsim-x86_64-890d573a1-1_20260621
with following parameters:
test: group-31
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G 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/202607311514.d263d952-lkp@intel.com
2026-07-29 04:48:06 ./run-tests.py pmksa_cache_preauth_vlan_used
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 pmksa_cache_preauth_vlan_used 1/1
Test: RSN pre-authentication to generate PMKSA cache entry (station with VLAN set)
Starting AP wlan3
Connect STA wlan0 to AP
Starting AP wlan4
Exception during test execution: No PMKSA cache entry created from pre-authentication
Traceback (most recent call last):
File "/lkp/benchmarks/hwsim/tests/hwsim/./run-tests.py", line 635, in main
t(dev, apdev)
~^^^^^^^^^^^^
File "/lkp/benchmarks/hwsim/tests/hwsim/test_pmksa_cache.py", line 592, in test_pmksa_cache_preauth_vlan_used
run_pmksa_cache_preauth_vlan_used(dev, apdev, None, force_disconnect=True)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/lkp/benchmarks/hwsim/tests/hwsim/test_pmksa_cache.py", line 605, in run_pmksa_cache_preauth_vlan_used
generic_pmksa_cache_preauth(dev, apdev, extraparams,
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
"vlan1", "brvlan1",
^^^^^^^^^^^^^^^^^^^
force_disconnect=force_disconnect)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/lkp/benchmarks/hwsim/tests/hwsim/test_pmksa_cache.py", line 518, in generic_pmksa_cache_preauth
raise Exception("No PMKSA cache entry created from pre-authentication")
Exception: No PMKSA cache entry created from pre-authentication
FAIL pmksa_cache_preauth_vlan_used 5.838044 2026-07-29 04:48:12.967860
passed 0 test case(s)
skipped 0 test case(s)
failed tests: pmksa_cache_preauth_vlan_used
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260731/202607311514.d263d952-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-31 13:15 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=202607311514.d263d952-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=johannes.berg@intel.com \
--cc=kartikey406@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@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