All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
	Richard Purdie <rpurdie@linux.intel.com>,
	Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: mtdoops: helper application for readout?
Date: Tue, 19 Feb 2013 21:25:05 -0800	[thread overview]
Message-ID: <1361337905.13247.3.camel@ted> (raw)
In-Reply-To: <CAN8TOE-eWhvVF_c48548HeA9OZ4D5Mp0xSLJBz9RsdTYwPRqOg@mail.gmail.com>

On Tue, 2013-02-19 at 16:26 -0800, Brian Norris wrote:
> On Thu, Feb 14, 2013 at 3:40 AM, Alexander Stein
> <alexander.stein@systec-electronic.com> wrote:
> > is there already some helper application which can shows the stored oops/panics with mtdoops?
> 
> After a bit of googling, it looks like there are scattered URL
> references to a no-longer-available "oopslog.c", written by the author
> of mtdoops, Richard Purdie. I CC'd him at his last-known address from
> the git logs, but he doesn't seem to have touched this in a while.
> 
> AFAIK, the output from mtdoops is just plain text data (not
> compressed), so you can just dump it straight from the /dev/mtdX
> (where X is the MTD number) with something like 'cat /dev/mtdX'. Of
> course, that will not account for when the ring buffer wraps around
> nor if there are bad blocks.
> 
> Brian
> 
> P.S. With a little more digging, I found a source tarball in the Maemo
> archives that contains oopslog.c. It's a very simple program, and I
> haven't tested it. Use at your own risk:
> 
> http://maemo.org/packages/view/sp-oops-extract/
> 
> http://repository.maemo.org/pool/maemo5.0/free/s/sp-oops-extract/sp-oops-extract_0.0.7-1.tar.gz

You've found the code that works with that setup, I haven't touched it
in a long time...

Cheers,

Richard

  reply	other threads:[~2013-02-20  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 11:40 mtdoops: helper application for readout? Alexander Stein
2013-02-20  0:26 ` Brian Norris
2013-02-20  5:25   ` Richard Purdie [this message]
2013-02-20 10:51   ` Alexander Stein
2014-11-17 11:32   ` Ranjith

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=1361337905.13247.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexander.stein@systec-electronic.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rpurdie@linux.intel.com \
    /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.