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):
unwind_backtrace+0x0/0xf8
warn_slowpath_common+0x50/0x60
warn_slowpath_null+0x1c/0x24
ocal_bh_enable_ip+0xa0/0xac
bdi_register+0xec/0x150
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)
Linux kernel panic. Understanding oops message - pgd?
pgd is short for "page global directory", the kernel's name for the top level of a page table.
Related Topics
Compile Swift Script with Static Swift Core Library
Start Rails Server Automatically When Ever I Start My Ubuntu MAChine
Is There a Clang Mingw Cross Compiler for Linux
Compressing the Core Files During Core Generation
Can't Install Freetds via Yum Package Manager
How to Use Sed to Change File Extensions
How to Change Perf_Event_Open Max Sample Rate
Can an Interrupt Handler Be Preempted
How to Catch the L3-Cache Hits and Misses by Perf Tool in Linux
Can Malloc_Trim() Release Memory from the Middle of the Heap
Critical Timing in an Arm Linux Kernel Driver
Accessing Linux /Dev/Usb as Standard Files to Communicate with Usb Device
Extract Date from a File Name in Unix Using Shell Scripting
Redirect Process Stdin and Stdout to Netcat
Shell Script Password Security of Command-Line Parameters