From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [rt-devel:linux-6.2.y-rt-rebase] [printk] 5342b8e20b: hwsim.ap_ft_eap_cui.fail
Date: Mon, 30 Jan 2023 10:02:45 +0100 [thread overview]
Message-ID: <Y9eHtTgQ0Pmz2gql@linutronix.de> (raw)
In-Reply-To: <Y9R+VfUgvU1U6DEj@xsang-OptiPlex-9020>
On 2023-01-28 09:45:57 [+0800], Oliver Sang wrote:
> hi Sebastian,
Hi Oliver,
> we rebuilt the kernel for both this commit and its parent, and make sure the
> config are same for both (as attached, actually also same to the config we used
> in last tests for oiginal report), then rerun the tests more times, but the
> issue seems still persistent
>
> d144a18b3d136079 5342b8e20b15e5fb37e49de2435
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :20 100% 20:20 hwsim.ap_ft_eap_cui.fail
> :20 100% 20:20 hwsim.ap_ft_many.fail
> :20 100% 20:20 hwsim.ap_ft_pmf_bip_cmac_128.fail
>
> attached one dmesg for this commit and another for parent FYI.
| wlan0: send auth to 02:00:00:00:03:00 (try 1/3)
| +wlan0: send auth to 02:00:00:00:03:00 (try 2/3)
| +wlan0: send auth to 02:00:00:00:03:00 (try 3/3)
| wlan0: authenticated
| wlan0: associate with 02:00:00:00:03:00 (try 1/3)
| -wlan0: RX ReassocResp from 02:00:00:00:03:00 (capab=0x411 status=0 aid=1)
…
| -wlan0: associated
…
| +wlan0: RX ReassocResp from 02:00:00:00:03:00 (capab=0x411 status=55 aid=1)
| +wlan0: 02:00:00:00:03:00 denied association (code=55)
It is hard to comprehend that the printk change broke wifi/ hwsim. Let
me add John to see what he thinks.
> BTW, we noticed PREEMPT_RT is mentioned in commit message, but we didn't enable
> it in our config, not sure if this is relevant?
These printk changes are kind of staged for upstream inclusion. "kind
of" because John is reworking them. So either I broke something while
rebasing them or the timing changed and this pops up. The 6.1 series had
mostly the same printk code. This should work independent of PREEMPT_RT.
Sebastian
prev parent reply other threads:[~2023-01-30 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 13:23 [rt-devel:linux-6.2.y-rt-rebase] [printk] 5342b8e20b: hwsim.ap_ft_eap_cui.fail kernel test robot
2023-01-24 14:10 ` Sebastian Andrzej Siewior
2023-01-28 1:45 ` Oliver Sang
2023-01-30 9:02 ` Sebastian Andrzej Siewior [this message]
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=Y9eHtTgQ0Pmz2gql@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rcu@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