Hi, I noticed this warning on 5.16, recompiled to 5.19 and still saw it. Its happening on a UML kernel running many tests if that makes a difference. It will happen several times during a full test run, warn many times >60, then stop for a bit and repeat. [ 1413.940000] ------------[ cut here ]------------ [ 1413.940000] WARNING: CPU: 0 PID: 1706 at include/net/cfg80211.h:608 ieee80211_build_preq_ies+0x766/0x84d [ 1413.940000] Modules linked in: [ 1413.940000] CPU: 0 PID: 1706 Comm: kworker/u2:2 Tainted: G W 5.19.0 #1 [ 1413.940000] Workqueue: rad2 ieee80211_scan_work [ 1413.940000] Stack: [ 1413.940000] 605d0943 60256c96 60035421 00000001 [ 1413.940000] 6052cddd 60450efa 65d61dd9 60454c00 [ 1413.940000] 00000000 00000000 00000009 6003e77d [ 1413.940000] Call Trace: [ 1413.940000] [<60256c96>] ? dump_stack_print_info+0xe1/0xef [ 1413.940000] [<60035421>] ? um_set_signals+0x0/0x3c [ 1413.940000] [<60450efa>] ? _printk+0x0/0x9f [ 1413.940000] [<60454c00>] ? dump_stack_lvl+0x47/0x52 [ 1413.940000] [<6003e77d>] ? __warn+0xf2/0x123 [ 1413.940000] [<604501bb>] ? warn_slowpath_fmt+0xd6/0xe2 [ 1413.940000] [<60066c8c>] ? __wake_up_common+0x9e/0x121 [ 1413.940000] [<604500e5>] ? warn_slowpath_fmt+0x0/0xe2 [ 1413.940000] [<603d3bc5>] ? ieee80211_ie_split_ric+0xe4/0xfe [ 1413.940000] [<60035421>] ? um_set_signals+0x0/0x3c [ 1413.940000] [<604341ac>] ? ieee80211_vif_type_p2p+0x0/0x26 [ 1413.940000] [<6043aeb5>] ? ieee80211_build_preq_ies+0x766/0x84d [ 1413.940000] [<60035449>] ? um_set_signals+0x28/0x3c [ 1413.940000] [<602c6e4b>] ? skb_queue_tail+0x43/0x47 [ 1413.940000] [<60429f6c>] ? skb_put_zero+0x2c/0x34 [ 1413.940000] [<60429f40>] ? skb_put_zero+0x0/0x34 [ 1413.940000] [<6043b095>] ? ieee80211_build_probe_req+0xf9/0x161 [ 1413.940000] [<6040c2ed>] ? ieee80211_scan_state_send_probe+0xaf/0x14c [ 1413.940000] [<60051181>] ? queue_delayed_work_on+0x67/0x72 [ 1413.940000] [<6040d1b0>] ? ieee80211_scan_work+0x40b/0x503 [ 1413.940000] [<600529de>] ? process_one_work+0x1b0/0x2b1 [ 1413.940000] [<6004f829>] ? move_linked_works+0x0/0x57 [ 1413.940000] [<60053086>] ? worker_thread+0x270/0x39b [ 1413.940000] [<6004f909>] ? set_pf_worker+0x0/0x5f [ 1413.940000] [<60057231>] ? arch_local_irq_save+0x0/0x26 [ 1413.940000] [<60035449>] ? um_set_signals+0x28/0x3c [ 1413.940000] [<60052e16>] ? worker_thread+0x0/0x39b [ 1413.940000] [<600588ef>] ? kthread_exit+0x0/0x37 [ 1413.940000] [<60052e16>] ? worker_thread+0x0/0x39b [ 1413.940000] [<60058a6d>] ? kthread+0x11f/0x124 [ 1413.940000] [<60035377>] ? unblock_signals+0x36/0xe0 [ 1413.940000] [<60021f95>] ? new_thread_handler+0x86/0xbb [ 1413.940000] ---[ end trace 0000000000000000 ]--- [ 1414.230000] ------------[ cut here ]------------ Probably a separate issue, but I also noticed this print on 5.19: [ 1054.390000] wlan107: authenticate with 02:00:00:00:f1:00 [ 1054.390000] wlan107: bad VHT capabilities, disabling VHT [ 1054.390000] wlan107: Invalid HE elem, Disable HE [ 1054.390000] wlan107: 80 MHz not supported, disabling VHT I don't think its related since I don't see this on 5.16, but still see the crash. Thanks, James
