From: "Martin Creutziger" <martin.creutziger@barco.com>
To: "linux-mtd" <linux-mtd@lists.infradead.org>
Cc: Damir Shayhutdinov <lost404@gmail.com>
Subject: Re: JFFS2: Kernel 2.6.24.2 Ooops during excessive write test
Date: Tue, 01 Apr 2008 09:36:11 +0200 [thread overview]
Message-ID: <1207035371.6252.7.camel@KARCLT0275> (raw)
In-Reply-To: <679044850803310823x10ac1f9dg7de6ed531c7d01b6@mail.gmail.com>
On Mon, 2008-03-31 at 19:23 +0400, Damir Shayhutdinov wrote:
> Hi!
>
> 2008/3/31, Martin Creutziger wrote:
> > I did some searching in the archive already and did not find anything,
> > so I just post it myself in the hope that somebody can help me.
> >
> > I am doing some excessive write tests on a PPC405EP running kernel
> > 2.6.24.2 at the moment. At irregular intervals, the "space accounting
> > superblock info" gets "screwed" and I'd like to know why this happens
> > and if it is fixable. And if not, that information might help me to
> > decide whether or not this affects the planned application.
> >
> > Thanks for the help,
>
> Can you test this patch with your system?
> http://lists.infradead.org/pipermail/linux-mtd/2007-November/019866.html
Yes, will do that. I also activated verbose info on BUG() now, maybe
that gives additional information in case it goes wrong again.
I have to add, however, that it can take up to a week until the oops
occurs again, so be patient :)
Thanks so far,
Martin
DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
next prev parent reply other threads:[~2008-04-01 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 14:17 JFFS2: Kernel 2.6.24.2 Ooops during excessive write test Martin Creutziger
2008-03-31 15:23 ` Damir Shayhutdinov
2008-04-01 7:36 ` Martin Creutziger [this message]
2008-04-07 6:30 ` Martin Creutziger
2008-04-23 10:12 ` David Woodhouse
2008-04-23 10:15 ` [JFFS2] Fix free space leak with in-band cleanmarkers David Woodhouse
2008-04-26 0:50 ` patch jffs2-fix-free-space-leak-with-in-band-cleanmarkers.patch added to 2.6.24-stable tree gregkh
2008-04-26 1:01 ` patch jffs2-fix-free-space-leak-with-in-band-cleanmarkers.patch added to 2.6.25-stable tree gregkh
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=1207035371.6252.7.camel@KARCLT0275 \
--to=martin.creutziger@barco.com \
--cc=linux-mtd@lists.infradead.org \
--cc=lost404@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox