Also that RIP looks daunting. What is this about?
RIP does not mean "Rest in peace"
It means "Instruction Pointer Register"
Instruction pointer points to portion of code or instruction that is to be executed next by CPU.
Register in simple terms means a storage within CPU that holds the IP (Instruction Pointer), there are many other registers holding other values.
In your screenshot below RIP is "Code:" portion which shows the code that CPU is about to execute, in binary ofc. but it's shown in hexadecimal for easier understanding.
What follows are several other CPU registers, ex. RSP, RAX, RBX etc...
Depending on Code values in those registers will be used by CPU.
---
Entries Between <TASK> and RIP is stack trace and shows function calls that were called prior crash, (they were called from top to bottom) until crash.
What follows is state of RIP, other registers and Code at the time of a crash.
This output between <TASK></TASK> can be useful to the person who already knows how kernel works and to those already familiar with kernel source code.
Normal users can look at function calls and hope to find some pattern (ex. self explanatory function name) and then google out the meaning to try pinpoint the cause but often times this is not sufficient.
In this case stack trace is useless to regular user because kernel panic started early and the output is all about procedure of error handling rather than showing what caused it.
For instance stack trace starts with "show_stack..." function which means it's all about error handling and what follows is only error handling.
to understand "do_syscall..." functions one needs to look at the numbers that are being called:
As you can see this output is pretty much very hard to understand for a regular user but in some cases it can be self-explanatory.