Messages in this thread | | | Date | Thu, 06 Jan 2005 16:25:30 -0800 | From | "Randy.Dunlap" <> | Subject | Re: [PATCH] kernel/printk.c lockless access |
| |
Anton Blanchard wrote: > > >>We faced the same problem in the Digeo kernel. When the kernel oopses we >>want to grab the last kilobyte or so of the printk buffer and stash it into >>nvram. We did this via a function which copies the data rather than >>exporting all those variables, which I think is a nicer and more >>maintainable approach: > > > Actually Id love to do this on ppc64 too. Its always difficult to get a > customer to remember to save away an oops report.
We need /proc/kallsyms, /proc/modules, etc. also.... can you capture all of that for a complete oops/panic analysis? (short of kdump, that is)
-- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |