From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linas Vepstas <linas@austin.ibm.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] kernel/printk.c lockless access
Date: Thu, 06 Jan 2005 16:25:30 -0800 [thread overview]
Message-ID: <41DDD6FA.2050403@osdl.org> (raw)
In-Reply-To: <20050107002648.GD14239@krispykreme.ozlabs.ibm.com>
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
next prev parent reply other threads:[~2005-01-07 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:58 [PATCH] kernel/printk.c lockless access Linas Vepstas
2005-01-06 20:50 ` Andi Kleen
2005-01-07 0:12 ` Andrew Morton
2005-01-07 0:26 ` Anton Blanchard
2005-01-07 0:25 ` Randy.Dunlap [this message]
2005-01-07 1:54 ` Alan Cox
2005-01-09 10:44 ` Frank van Maarseveen
2005-01-09 22:31 ` David Wagner
2005-01-09 23:00 ` Alan Cox
2005-01-10 20:43 ` Matt Mackall
2005-01-08 2:37 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41DDD6FA.2050403@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).