From: "Chris Zimman" <czimman@bloomberg.com>
To: "Andrew Lunn" <andrew@lunn.ch>,
"Srinivas rao" <ch_srinivas321@yahoo.co.in>
Cc: "ecos" <ecos-discuss@sourceware.org>
Subject: RE: [ECOS] jffs2_1 test case error
Date: Thu, 26 Oct 2006 12:56:00 -0000 [thread overview]
Message-ID: <4B24CC52E8A6EB4A95B414126492987C01616AFE@lo2525.corp.bloomberg.com> (raw)
Just for what it's worth -- unless you are using the new eCosCentric V2
flash drivers, make sure you have interrupts disabled during JFFS2
access. eCosCentric did a lot of work on JFFS2 to make it stable under
eCos. I have no idea how well the stock JFFS2 code works.
--Chris
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: 26 October 2006 12:35
To: Srinivas rao
Cc: ecos
Subject: Re: [ECOS] jffs2_1 test case error
On Thu, Oct 26, 2006 at 11:33:41AM +0100, Srinivas rao wrote:
> Hi All,
>
> Iam running jffs2 test cases on my board. After
> reading the directories getting error like below.
> Pls give me the solution.
Sorry, but we don't give solutions. We try to help you find the
solution to your problem.
>
> <INFO>: reading directory /
> <INFO>: entry . [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry .. [mode 016f0001 ino
> 00000001 nlink 1 size 0]
> <INFO>: entry etc [mode 017f0001 ino
> 00000004 nlink 1 size 0]
> <INFO>: entry dev<FAIL>: stat() returned -1
> No such entity
>
> <INFO>: entry bin [mode 017f0001 ino
> 00000002 nlink 1 size 0]
> <INFO>: entry lib [mode 017f0001 ino
> 00000005 nlink 1 size 0]
> <INFO>: entry mnt [mode 017f0001 ino
> 00000006 nlink 1 size 0]
> <INFO>: entry var [mode 017f0001 ino
> 000000f6 nlink 1 size 0]
> <INFO>: entry tmp [mode 017f0001 ino
> 000000fb nlink 1 size 0]
> <INFO>: entry sbin [mode 017f0001 ino
> 00000007 nlink 1 size 0]
> <INFO>: create file /foo size 202
> <5>Write of 68 bytes at 0x003e3144 failed. returned
> -5, retlen 68
Well if you look in packages/error/current/include/codes.h you will
find that 5 is EIO. So you probably need to single step this write
call and find out where and why it returns EIO.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2006-10-26 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 12:56 Chris Zimman [this message]
2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
2008-03-27 9:58 ` Chris Zimman
2008-03-28 15:24 ` Jürgen Lambrecht
2008-03-29 8:35 ` Chris Zimman
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 10:33 Srinivas rao
2006-10-26 11:34 ` Andrew Lunn
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=4B24CC52E8A6EB4A95B414126492987C01616AFE@lo2525.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=andrew@lunn.ch \
--cc=ch_srinivas321@yahoo.co.in \
--cc=ecos-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).