removing Luca On Wed, 2022-04-20 at 11:49 +0200, Toke Høiland-Jørgensen wrote: <snip> > > > > > > > So you do get a SAP connection. Weird. > > Checking with the CSME guys. > > Can you get dynamic debug prints for iwlmei module? > > Best would be tracing with -e iwlmei_sap_cmd > > Sure! Recorded these while doing a suspend-restore, then restarting iwd: > > kworker/u16:34-34555 [004] 46452.506238: iwlmei_sap_cmd: sap_cmd Tx: type 1010 len 8 seq > 11 > kworker/u16:34-34555 [004] 46452.506243: iwlmei_me_msg: ME message: Tx: type 3 seq 8 > kworker/u16:34-34555 [004] 46452.559407: iwlmei_sap_cmd: sap_cmd Tx: type 1001 len 4 seq > 12 > kworker/u16:14-33311 [004] 46452.573077: iwlmei_sap_cmd: sap_cmd Tx: type 1006 len 0 seq > 13 > kworker/u16:14-33311 [004] 46452.573078: iwlmei_me_msg: ME message: Tx: type 3 seq 10 > kworker/4:0-34305 [004] 46452.706737: iwlmei_me_msg: ME message: Tx: type 3 seq 11 > kworker/u16:8-34462 [000] 46457.939453: iwlmei_me_msg: ME message: Tx: type 1 seq 1 > kworker/4:2-32196 [004] 46457.940910: iwlmei_me_msg: ME message: Rx: type 2 seq 81 > kworker/4:2-32196 [004] 46457.940912: iwlmei_sap_cmd: sap_cmd Tx: type 1013 len 0 seq 1 > kworker/4:2-32196 [004] 46457.940913: iwlmei_me_msg: ME message: Tx: type 3 seq 2 > kworker/4:2-32196 [004] 46457.942056: iwlmei_me_msg: ME message: Rx: type 3 seq 82 > kworker/4:2-32196 [004] 46457.942060: iwlmei_sap_cmd: sap_cmd Rx: type 502 len 4 seq 1 > kworker/4:2-32196 [004] 46458.042205: iwlmei_me_msg: ME message: Rx: type 3 seq 83 > kworker/4:2-32196 [004] 46458.042208: iwlmei_sap_cmd: sap_cmd Rx: type 500 len 1896 seq > 2 > kworker/4:2-32196 [004] 46458.042209: iwlmei_sap_cmd: sap_cmd Rx: type 512 len 64 seq 3 > kworker/4:2-32196 [004] 46458.042214: iwlmei_sap_cmd: sap_cmd Rx: type 502 len 4 seq 4 > iwd-35396 [003] 46467.085642: iwlmei_sap_cmd: sap_cmd Tx: type 1008 len 8 seq 2 > iwd-35396 [003] 46467.085645: iwlmei_me_msg: ME message: Tx: type 3 seq 3 > iwd-35396 [003] 46467.102818: iwlmei_sap_cmd: sap_cmd Tx: type 1008 len 8 seq 3 > iwd-35396 [003] 46467.103369: iwlmei_sap_cmd: sap_cmd Tx: type 1016 len 20 seq > 4 > iwd-35396 [003] 46467.103842: iwlmei_sap_cmd: sap_cmd Tx: type 1001 len 4 seq 5 > iwd-35396 [003] 46467.104689: iwlmei_sap_cmd: sap_cmd Tx: type 1002 len 12 seq > 6 can you please send the content of tracing unparsed? There is more binary data that I can use. I definitely need to talk to the CSME guys, I can see that CSME is alive even if you have AMT disabled. Problem: it's holiday season here. Thanks. > > The dmesg log looked like this (back to -19 in the error): > > [46452.483343] wlan0: deauthenticating from 4c:60:de:ea:b8:5a by local choice (Reason: > 3=DEAUTH_LEAVING) > [46452.689465] iwlmei 0000:00:16.0-13280904-7792-4fcb-a1aa-5e70cbb1e865: Couldn't get ACK from > CSME on HOST_GOES_DOWN message > [46452.689567] iwlmei 0000:00:16.0-13280904-7792-4fcb-a1aa-5e70cbb1e865: failed to send the > SAP_ME_MSG_CHECK_SHARED_AREA message -19 > > > I might also need dynamic debgug prints from the mei bus driver but that will be for later. > > Thanks for reporting and providing the data! > > You're welcome! Thanks for looking into it :) > > -Toke
