On Thu, Aug 27, 2009 at 4:03 AM, Andrey Yurovsky<andrey@xxxxxxxxxxx> wrote: > Hi Richard, > > On Wed, Aug 26, 2009 at 4:11 PM, Richard Farina<sidhayn@xxxxxxxxx> wrote: >> Again, I'm not trying to point my finger blaming someone, I'm trying to help >> fix a problem. I am traveling for the next few days, when I get home to my >> camera I hope you are all calm enough to help me troubleshoot this bug so we >> can find a solution instead of accusing each other of accusing each other. > > you may want to try kexec in place of having to take photos of the > kernel panic output. This will enable you to load a crash-recovery > kernel, which will be booted automatically once you've successfully > reproduced the problem. From there you can use gdb together with > /proc/vmcore and your kernel image to reconstruct what you'd see in > dmesg and paste the entire oops. Please see > Documentation/kdump/kdump.txt for more details and use > Documentation/kdump/gdbmacros.txt to give gdb a "dmesg" macro. Or use the "crash" utility (a wrapper for gdb), which can directly extract the kernel log from vmcore. > > -Andrey > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
