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
