From: Jarkko Lavinen <jarkko.lavinen@nokia.com>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] oops and panic message logging to MTD
Date: Tue, 3 Jul 2007 12:47:02 +0300 [thread overview]
Message-ID: <20070703094702.GA11992@angel.research.nokia.com> (raw)
In-Reply-To: <1182247254.5760.17.camel@localhost.localdomain>
On Tue, Jun 19, 2007 at 11:00:54AM +0100, Richard Purdie wrote:
> Its not a case of formatting the whole partition. The whole point of
> this code is the following use case:
>
> 1. Device crashes
> 2. Device reboots
> 3. mtdoops partition has a log of why it crashed
The oops logger uses oops_in_progress variable to detect the begin and the
end of an oops. The end is detected when the first non-oops line comes and
oops_in_progress is false.
This works if the kernel is still running after the oops and gemerates some
non-oops messages. But if there is no non-oops line following an oops, no
flushing will occur and there won't be a log on flash.
Jarkko Lavinen
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Lavinen <jarkko.lavinen@nokia.com>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: dedekind@infradead.org, linux-mtd <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] oops and panic message logging to MTD
Date: Tue, 3 Jul 2007 12:47:02 +0300 [thread overview]
Message-ID: <20070703094702.GA11992@angel.research.nokia.com> (raw)
In-Reply-To: <1182247254.5760.17.camel@localhost.localdomain>
On Tue, Jun 19, 2007 at 11:00:54AM +0100, Richard Purdie wrote:
> Its not a case of formatting the whole partition. The whole point of
> this code is the following use case:
>
> 1. Device crashes
> 2. Device reboots
> 3. mtdoops partition has a log of why it crashed
The oops logger uses oops_in_progress variable to detect the begin and the
end of an oops. The end is detected when the first non-oops line comes and
oops_in_progress is false.
This works if the kernel is still running after the oops and gemerates some
non-oops messages. But if there is no non-oops line following an oops, no
flushing will occur and there won't be a log on flash.
Jarkko Lavinen
next prev parent reply other threads:[~2007-07-03 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 16:31 [PATCH/RFC] oops and panic message logging to MTD 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 12:31 Richard Purdie
2007-05-29 12:35 ` Richard Purdie
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=20070703094702.GA11992@angel.research.nokia.com \
--to=jarkko.lavinen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rpurdie@openedhand.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.