public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "\"Fredrik Jönsson B (AL/EAB)\"" <fredrik.b.jonsson@ericsson.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: The magic bitmask question - again
Date: Mon, 31 Oct 2005 16:03:40 +0300	[thread overview]
Message-ID: <4366162C.4050406@yandex.ru> (raw)
In-Reply-To: <EF4121B4EBC4E045BDE1273F9D0A87FFCD410C@esealmw107.eemea.ericsson.se>

Fredrik Jönsson B (AL/EAB) wrote:
> This may be a stupid question, but I still need to ask.
> 
> We have a system with a 128Mb NOR-flash of which 3Mb is used as a
> keep-off area for the kernel and the rest for a JFFS2 root file
> system.
128 Megabit?

> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
> 0x00000000: 0x4800 instead
This message says that there is something unexpected at the offset 
0x00000000 of the JFFS2 partition. JFFS2 expects there is either a node 
there (most likely a clean marker node) or the block contains all 0xFF.

How can this garbage get into the beginning of an eraseblock? No idea. 
May be this is an effect of an unclean reboot? But if it happens often 
it is strange and looks like something not normal. Or the other 
possibility is that you did not erase your flash properly before putting 
the JFFS2 image there. And also it may be the result of hardware/driver 
problems.

Try to play with this. Try to erase the partition, check that it 
actually contain all 0xFFs, flash your image, compare with the original, 
mount and see is there are such messages.

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

  reply	other threads:[~2005-10-31 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 12:31 The magic bitmask question - again Fredrik Jönsson B (AL/EAB)
2005-10-31 13:03 ` Artem B. Bityutskiy [this message]
2005-10-31 13:15 ` David Jander
  -- strict thread matches above, loose matches on Subject: below --
2005-10-31 15:52 Fredrik Jönsson B (AL/EAB)

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=4366162C.4050406@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=fredrik.b.jonsson@ericsson.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