From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dan.rpsys.net ([93.97.175.187]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1U82Bc-0006Jx-SG for linux-mtd@lists.infradead.org; Wed, 20 Feb 2013 05:25:46 +0000 Message-ID: <1361337905.13247.3.camel@ted> Subject: Re: mtdoops: helper application for readout? From: Richard Purdie To: Brian Norris Date: Tue, 19 Feb 2013 21:25:05 -0800 In-Reply-To: References: <2131687.FmJCQHlDMX@ws-stein> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: linux-mtd@lists.infradead.org, Richard Purdie , Alexander Stein List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2013-02-19 at 16:26 -0800, Brian Norris wrote: > On Thu, Feb 14, 2013 at 3:40 AM, Alexander Stein > 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