You're only showing us part pf the error. There should be more above the list pf modules loaded that will provide useful information

dmesg > dmesg-out will give the entire dmesg log as a text file, and you can cut out the irrelevant parts

I don't pretend to be an expert in this, and I also have no idea what the state machine looks like for unauthenticated WiFi, but my thinking on the call stack is either you were authenticated and the association with the AP dropped while sending a frame and puked, or it kicked it while attempting to authenticate to an AP, and I have no idea why a mutex would be taken, or to what, but it timed out apparently.

So why would this happen after a rebuild?

1. freak accident/timing thing.

2. I see multiple mt## modules loaded, and I'm suspecting while not looking it up that they are operating a MediaTek chip in that dongle, and are potentially conflicting.

3. lots of wifi devices I've seen recently have loaded firmware separately from driver from /use/lib(or lib64)/firmware and the version changed from before, and maybe needs updating now or you did it before or whatever.

I agree with others - I'd give you a fiver if it happens again without the adapter connected.

Don't know much, but nl80211 in the stack is indicative that the crash happens in a WiFi driver.

Looks like maybe some bad behaviour with a mutex.

It's the networking stack causing the panic, my guess is the WiFi card gets sad.

Does it still get the error without the wifi adapter connected? The stack trace shows some network-related stuff (which doesn't necessarily mean that's where the issue arose, but it would be a little coincidence based on what you said).

That's the first thing I'd try, and if removing the adapter fixes it (long term) I wouldn't use the adapter anymore. Sometimes broken hardware breaks other hardware it's connected to.

If removing the adapter doesn't fix it, then the next thing I'd try is booting back into the known-good old old OS, maybe removing the NVidia card, basically simplify everything one step at a time until it stops happening, if you can.

Comm: wpa_supplicant being the wifi function makes me suspicious of your wifi hardware as well before I saw the rest of your post. I've had the best success with PCIe based wifi cards (if this is a desktop pc)

Oem was too lazy.

Look at the line with the asm_exc_invalid_op. That seems like a hardware fault caused by an invalid asm instruction to me. Either something wrong is being interpreted as an opcode (unlikely) or maybe the driver was compiled with extensions not available on the current machine.

OP, how old is your CPU? And how old is the nic you are using?

Edit: ~~did you use a custom driver for the NIC? I'm looking at the Linux src and rt_mutex_schedule does not exist.~~ Nevermind. Was checking 4.18 instead of 6.7. found it now. The bug is most likely inside a macro called preempt_disable(). Unfortunately most of the functions are pretty heavily inlined and architecture dependent so you won't get much out of it. But it is likely any changes you made in terms of premption might also be causing the bug.