Google _dabt_svc arm or __dabt_svc arm
I see two links in my top ten...
This tells me that a kernel update (or revert to older) is in order. An update is the easy thing
to do and explore. Reading the notes there is some interaction with fast interrupts
involving networking. Since I have an OLD 10baseT network hub I might connect
100baseT traffic to the slow hub and then to the PandaB as a work around.
You do have stack info in your screen shot and the running kernel so do a bit
of debugging and unwind the pile on the stack. The problem may be deeper
in the stack (or time) and the last couple symbols (functions) on the stack
are simply bystanders that witness the problem and pulled the fire-alarm.