All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard@openedhand.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH/RFC] oops and panic message logging to MTD
Date: Tue, 29 May 2007 13:35:06 +0100	[thread overview]
Message-ID: <1180442106.5822.58.camel@localhost.localdomain> (raw)
In-Reply-To: <1180441903.5822.53.camel@localhost.localdomain>

On Tue, 2007-05-29 at 13:32 +0100, Richard Purdie wrote:
> Kernel oops and panic messages are invaluable when debugging crashes.
> These messages often don't make it to flash based logging methods (say a
> syslog on jffs2) due to the overheads involved in writing to flash.
> 
> This patch allows you to turn an MTD partition into a circular log
> buffer where kernel oops and panic messages are written to. The messages
> are obtained by registering a console driver and checking
> oops_in_progress. Erases are performed in advance to maximise the
> chances of a saving messages.
> 
> To activate it, add console=ttyMTDx to the kernel commandline (where x
> is the mtd device number to use).
> 
> Signed-off-by: Richard Purdie <rpurdie@openedhand.com>

I meant to add, http://folks.o-hand.com/richard/oopslog.c is an example
of extracting this information in userspace. It will work with an
mtdblock device or a dump of the mtd partition.

Cheers,

Richard

  reply	other threads:[~2007-05-29 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 12:31 [PATCH/RFC] oops and panic message logging to MTD Richard Purdie
2007-05-29 12:35 ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-18 16:31 Richard Purdie
2007-06-19  7:55 ` Artem Bityutskiy
2007-06-19 10:00   ` Richard Purdie
2007-06-19 10:29     ` Artem Bityutskiy
2007-06-19 10:52       ` Richard Purdie
2007-06-19 11:05         ` Artem Bityutskiy
2007-07-03  9:47     ` Jarkko Lavinen
2007-07-03  9:47       ` Jarkko Lavinen
2007-07-04  8:54       ` Richard Purdie
2007-07-04  8:54         ` Richard Purdie
2007-06-19  8:07 ` Artem Bityutskiy

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=1180442106.5822.58.camel@localhost.localdomain \
    --to=richard@openedhand.com \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.