public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <dedekind@oktetlabs.ru>
To: Mansi.Mahur@infineon.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Mounting File System .
Date: Mon, 25 Apr 2005 16:01:07 +0400	[thread overview]
Message-ID: <426CDC03.3020902@oktetlabs.ru> (raw)
In-Reply-To: <D99246B510C34944823191CB90759C8652804C@blrse201.ap.infineon.com>

Mansi.Mahur@infineon.com wrote:
> I simply mount jffs2 on to a mount point
> and test for jffs2 . But the behaviour is seen that if I give mount
> point as /tmp and not any other directory I get abnormal behaviour like:
Frankly, I hardly understand what do you mean :-)

> 1.following log seen
> [root@Linux tmp]$ waiting for chip to be ready timed out in word write
> Write error in obliterating obsoleted node at 0x0011c570: -5
This implies JFFS2 can not write to flash. This must a problem of 
underlying layers (your driver is buggy, your HW is broken, etc).

> Unable to handle kernel NULL pointer dereference at virtual address
> 00000000
This probably a bug in JFFS2 - it doesn't handle an error gracefully.

Please, do the following:

1. inform us about your kernel version;
2. explore http://www.linux-mtd.infradead.org carefully;
3. try the latest MTD snapshot;
4. post to the MTD mailing list - all the MTD people are there.

If the last snapshot doesn't help, then:

1. enable MTD debugging and JFFS2 debug level 1 in your .config;
2. post the JFFS2/MTD debugging output;
3. post the output of 'cat /proc/mtd;
4. use the last MTD snapshot.

Cheers,
Artem.

-- 
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: dedekind@oktetlabs.ru, web: http://www.oktetlabs.ru

  reply	other threads:[~2005-04-25 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 11:43 Mounting File System Mansi.Mahur
2005-04-25 12:01 ` Artem B. Bityuckiy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25  6:09 Mansi.Mahur
2005-04-25  8:12 ` Bernd Petrovitsch
2005-04-25  8:27 ` Artem B. Bityuckiy

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=426CDC03.3020902@oktetlabs.ru \
    --to=dedekind@oktetlabs.ru \
    --cc=Mansi.Mahur@infineon.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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