How to read, understand, analyze, and debug a Linux kernel panic?

It’s just an ordinary backtrace, those functions are called in reverse order (first one called was called by the previous one and so on):


The bdi_register+0xec/0x150 is the symbol + the offset/length there’s more information about that in Understanding a Kernel Oops and how you can debug a kernel oops. Also there’s this excellent tutorial on Debugging the Kernel

Note: as suggested below by Eugene, you may want to try addr2line first, it still needs an image with debugging symbols though, for example

addr2line -e vmlinux_with_debug_info 0019594c(+offset)

Leave a Comment