Re: [PATCH] kernel/printk.c lockless access

Randy.Dunlap
2005-01-07T00:58:19Z

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