If your laptop does not have a serial console that you can capture kernel panics over, and you don't have a digital camera to capture it either and you don't want to use netconsole (see Documentation/networking/netconsole.txt), the only method left really is to transcribe it by hand. This can be a rather painful process, unless you know what you're looking for. The most useful things, in order of importance are:
A BUG line, if one is displayed. This will normally appear as "kernel BUG at kernel/power/swsusp.c:1234". The filename and the line-number are the useful things here, along with at least the first few lines of the call trace.
- The call trace (aka stack trace). This is outlined in the large red box in the middle of the image below. The list of functions (from top to bottom) are the main part. The numbers along the left-hand side aren't too much help for people who don't have your exact kernel image as they are specific to your exact kernel compilation.
- The code dump. This is the string of two-digit hex numbers along the bottom.
Registers & stack.
