mtdoops: helper application for readout?
Hello,
is there already some helper application which can shows the stored oops/panics with mtdoops?
Best regards,
Alexander
Quoted 1 line · Alexander Stein
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
Quoted 17 lines · Brian Norris
Quoted 1 line · Alexander Stein
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
Quoted 7 lines
P.S. With a little more digging, I found a source tarball in the Maemo archives that containsoopslog.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
Quoted 17 lines · Brian Norris
Quoted 1 line · Alexander Stein
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
Quoted 7 lines
P.S. With a little more digging, I found a source tarball in the Maemo archives that containsoopslog.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
Ah, sp-oops-extract seems to be what I looked for. Thanks a lot!
Alexander
Quoted 4 lines · Brian Norris <computersforpeace <at> gmail.com> writes:
Quoted 1 line · On Thu, Feb 14, 2013 at 3:40 AM, Alexander Stein <alexander.stein <at>…
is there already some helper application which can shows the stored
oops/panics with mtdoops?
Quoted 14 lines
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
Quoted 7 lines
P.S. With a little more digging, I found a source tarball in the Maemo archives that containsoopslog.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
Quoted 5 lines
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
Hi Brain,
Have you changed anything in the mtdoops.c driver and how are running this application ..i have used it as in-build(static driver) module.i dint do any changes and i used the application with ./oops /dev/mtd4.here mtd4 id FLOG(nor memory).Do i need to map with any command or how.can you tell me the procedure for enabling the mtdoops and mapping to Nor flas and how to run the application.
Thanks in Advance.
Ranjith.