From: "Alexey, Korolev" <alexey.korolev@intel.com>
To: Kein Yuan <kein.yuan@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: Strange problem with JFFS2/MTD on Linux 2.6.9 ith Intel J3 Flash
Date: Sun, 26 Feb 2006 12:25:22 +0300 [thread overview]
Message-ID: <44017402.6030405@intel.com> (raw)
In-Reply-To: <d0cf8c90602240714g69b0bcf5y47dba43e25fb139c@mail.gmail.com>
Kein Yuan wrote:
> I am working on a PXA270 based paltform with Intel J3 Flash on Linux
> 2.6.9. I am sure that jffs2 image was written into the correct place
> and verified by md5chk command in blob, but somehow kernel can detect
> flash, can dump out the context correctly but failed to mount the
> flash partition as my root filesystem. Can anybody here give me some
> hints? The boot log was pasted as below:
>
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00037ef4:
> 0x9f54 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0003f070:
> 0xf960 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040004:
> 0x085c instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00080004:
> 0x1860 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000d2bb4:
> 0x0001 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0012a370:
> 0x006e instead
>
It possible that you specified erase block size improperly when you
created image of JFFS2 file system. Size of erase block can be specified
through -e parameter of mkfs.jffs2 utility.
Erase block size can be obtained using blob. (On attmempt to write
something blob should display size of erase block)
Thanks,
Alexey
next prev parent reply other threads:[~2006-02-26 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 15:14 Strange problem with JFFS2/MTD on Linux 2.6.9 ith Intel J3 Flash Kein Yuan
2006-02-26 9:25 ` Alexey, Korolev [this message]
2006-02-26 12:27 ` Kein Yuan
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=44017402.6030405@intel.com \
--to=alexey.korolev@intel.com \
--cc=kein.yuan@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