I finally managed to trigger this bug again. The last_kmsg file is attached, and confirms it is indeed a kernel panic. The traceback looks promising too.
I finally managed to trigger this bug again. The last_kmsg file is attached, and confirms it is indeed a kernel panic. The traceback looks promising too.