On Wed, Nov 17, 2021 at 03:25:36PM +0000, Mikolaj Kucharski wrote: > What is strange, I would imagine, that address of they key is one > between those two: > > > $ grep -w ic_def_txkey panic.txt | cut -f3- -d: | tail > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=2, k=0xffff80000009cfc8 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=1, k=0xffff80000009cf00 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=2, k=0xffff80000009cfc8 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=1, k=0xffff80000009cf00 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=2, k=0xffff80000009cfc8 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=1, k=0xffff80000009cf00 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=2, k=0xffff80000009cfc8 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=1, k=0xffff80000009cf00 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=2, k=0xffff80000009cfc8 > ieee80211_setkeysdone() [ieee80211_proto.c|480] case 0 ic_def_txkey > modified, kid=1, k=0xffff80000009cf00 > > However just before panic we see this: > > $ sed -ne '/^20211117.123448.498681Z/,/^20211117.123448.561466Z/p' panic.txt > 20211117.123448.498681Z: MMM: ieee80211_clear_htcaps() > [ieee80211_node.c|2328] memset() v25 > 20211117.123448.503936Z: MMM: ar5008_tx() [ar5008.c|1527] > 20211117.123448.506663Z: MMM: ar5008_tx() [ar5008.c|1530]: key unset for sw > crypto: 0 > 20211117.123448.513071Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|262]: > k: 0xffff8000225a6708 > 20211117.123448.518301Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|263]: > k_id: 0x0 > 20211117.123448.523580Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|264]: > k_flags: 0x0 > 20211117.123448.530034Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|265]: > k_len: 0x0 > 20211117.123448.535279Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|266]: > k_cipher: 0x0 > 20211117.123448.540526Z: MMM: ieee80211_encrypt() [ieee80211_crypto.c|267]: > k_key: 0x0000000000000000000000000000000000000000000000000000000000000000 > 20211117.123448.552314Z: panic: ieee80211_encrypt: key unset for sw crypto: > id=0 cipher=0 flags=0x0 > 20211117.123448.561466Z: Stopped at db_enter+0x10: popq %rbp > > What I did not expect is k=0xffff80000009cfc8 and k=0xffff80000009cf00 > between kid=2 and kid=1 and during panic k=0xffff8000225a6708. I don't > know from where 0xffff8000225a6708 came from. >
Sorry, need to investigate this more. I made a misake of &k vs k in my debug code :/ -- Regards, Mikolaj
