From: Benny Chen <bennyc@rtunet.com>
To: David Jander <david.jander@protonic.nl>
Cc: Leon Zhang <leoncamel@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: Mounting large JFFS2 causes other process to stop running!
Date: 06 Sep 2005 15:52:49 +1000 [thread overview]
Message-ID: <1125985969.4419.63.camel@Vigor4> (raw)
In-Reply-To: <200509051346.54202.david.jander@protonic.nl>
Hi David,
Thanks for replying.
> I can't make up the MTD version out of your kernel version. Would it be the
> last CVS for 2.4.x from March 2005, or older?
Yap, that is right. My mtd is quite old it is packaged with linux-2.4.21
kernel, so I checked the dates it is about 25/07/2002. I guess
mtd-linux is not supporting 2.4.x anymore. We will probably have to cop
this penalty until we upgrade our kernel.
Can you turn debug-level to 1 in the jffs2 (and mtd) driver and post
(relevant
> parts of) console output here? I'm not sure if I can help, but MTD developers
> might want to see what the kernel is busy with for so long.
Below are sniplets of the jffs2 debug level 1 message. It loops through
the jffs2_scan_inode.node() for majority of the time. This is also when
nothing else is running on the cpu.
Node is ino #2, version 43. Range 0x29000-0x2a000
jffs2_scan_inode_node(): Node at 0x0002ab80
Node is ino #2, version 44. Range 0x2a000-0x2b000
jffs2_scan_inode_node(): Node at 0x0002bbc4
Node is ino #2, version 45. Range 0x2b000-0x2c000
jffs2_scan_inode_node(): Node at 0x0002cc08
Node is ino #2, version 46. Range 0x2c000-0x2d000
Regards,
Benny
On Mon, 2005-09-05 at 21:46, David Jander wrote:
> On Monday 05 September 2005 10:55, Leon Zhang wrote:
> > Hi. there.
> > I confirm this bug.
> > My kernel is linux-2.4.29-vrs1-pxa1-intc4-col1. and my board CPU is PXA27x,
> > and the flash is on board flash.
>
> I can't make up the MTD version out of your kernel version. Would it be the
> last CVS for 2.4.x from March 2005, or older?
>
> > I am burned a minimum jffs2 rooffs. about 2M, only a busybox in it.
> > But, if a burned a 10M size rootfs. The console respone slowly first, and
> > after a while, the console will respone nonthing.
>
> Can you turn debug-level to 1 in the jffs2 (and mtd) driver and post (relevant
> parts of) console output here? I'm not sure if I can help, but MTD developers
> might want to see what the kernel is busy with for so long.
> I personally want to know if it has any relation with the architecture you are
> running on. I have had problems in the past with 2.4.x on PowerPC and older
> versions of MTD. Since I changed to CVS-march2005 I have not had any trouble,
> but I want to know more, and I need to be as sure as possible that I will not
> have any more trouble. The problem is, this kernel version is not officially
> supported anymore by mtd developers, so we are a little bit left out in the
> cold if there is trouble.
>
> Best regards,
next prev parent reply other threads:[~2005-09-06 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 2:42 Mounting large JFFS2 causes other process to stop running! Benny Chen
2005-09-05 6:44 ` David Jander
[not found] ` <ad39a30f05090501553458af6e@mail.gmail.com>
2005-09-05 11:46 ` David Jander
2005-09-06 5:52 ` Benny Chen [this message]
2005-09-06 6:45 ` David Woodhouse
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=1125985969.4419.63.camel@Vigor4 \
--to=bennyc@rtunet.com \
--cc=david.jander@protonic.nl \
--cc=leoncamel@gmail.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