A revision of my initial comment. I was able to reproduce the bug once while replaying the trace and generated the same error in the dmesg output but I am no longer able to reproduce the error while replaying the trace currently which is very odd.