From: Jarkko Lavinen <jlavi@iki.fi>
To: David Woodhouse <dwmw2@infradead.org>
Cc: MTD List <linux-mtd@lists.infradead.org>, jffs-dev@axis.com
Subject: Re: Benchmarking JFFS2
Date: Mon, 6 May 2002 15:19:30 +0300 [thread overview]
Message-ID: <20020506151930.A15109@kosh.hut.fi> (raw)
In-Reply-To: <28528.1020448474@redhat.com>; from dwmw2@infradead.org on Fri, May 03, 2002 at 06:54:34PM +0100
> Er, yes, that is concerning. Does it say why? If it's only occasional, then
> it's almost certainly memory allocation problems.
I have caught the message 8 times. It doesn't occur rather seldom when I have
been benchmarking JFFS2 over the weekend.
On five cases the first line was "Unknown INCOMPAT nodetype C002 at 0020293C"
(address varies).
On all 8 cases the next lines are "jffs2_do_read_inode(): No data
nodes found for ino #" then "Eep. read_inode() failed for ino #"
Last year there were two reports about C002 type node: 28 Jun 2001 Frederic
Giasson, and 08 Aug 2001 Xavier DEBREUIL. Is this the same problem they had?
> It would be useful if you could provide a profiling run from the
Do you mean kernel profiling? I am using JFFS2 on an Arm based device and
kernel profiling is not available for Arm or is it?
Jarkko lavinen
next prev parent reply other threads:[~2002-05-06 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 12:56 Benchmarking JFFS2 Jarkko Lavinen
2002-05-02 13:40 ` David Woodhouse
2002-05-03 17:19 ` Jarkko Lavinen
2002-05-03 17:54 ` David Woodhouse
2002-05-06 12:19 ` Jarkko Lavinen [this message]
2002-05-07 15:02 ` David Woodhouse
2002-05-07 15:13 ` Thomas Gleixner
2002-05-07 17:46 ` Jarkko Lavinen
2002-05-07 19:42 ` David Woodhouse
2002-10-08 17:10 ` David Woodhouse
2002-05-12 19:04 ` David Woodhouse
2002-05-13 8:40 ` Jarkko Lavinen
2002-05-13 9:11 ` David Woodhouse
2002-10-17 10:36 ` Jarkko Lavinen
2003-01-23 12:09 ` David Woodhouse
2003-02-13 12:38 ` Jarkko Lavinen
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=20020506151930.A15109@kosh.hut.fi \
--to=jlavi@iki.fi \
--cc=dwmw2@infradead.org \
--cc=jffs-dev@axis.com \
--cc=linux-mtd@lists.infradead.org \
/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