public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: "Artem B. Bityuckiy" <dedekind@yandex.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 problem
Date: Tue, 19 Jul 2005 14:19:34 +0200	[thread overview]
Message-ID: <42DCEFD6.8010006@cetrtapot.si> (raw)
In-Reply-To: <42DCEC94.8050505@yandex.ru>

Artem B. Bityuckiy wrote:
> Hinko Kocevar wrote:
> 
>> There you go. This is with JFFS2 debug set to 2 and MTD debug set to 3.
>> ...
>> NET: Registered protocol family 17
>> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 
>> 0x234a instead
> 
> 
> Even though you enabled JFFS2 debugging,
> the debugging messages are not seen on your console.
> 
> Could you please dump the first N (say, 128) bytes at the offset 
> 0x00000000 of the JFFS2 partition (/dev/mtd2)? Does it contain 0x234a 
> (LE) as the first 16-bit word?
> 

Creating 3 MTD partitions on "Trizeps2 flash":
0x00000000-0x00060000 : "Bootloader"
mtd: Giving out device 0 to Bootloader
0x00060000-0x00140000 : "Kernel"
mtd: Giving out device 1 to Kernel
0x00140000-0x01000000 : "Filesystem"
mtd: Giving out device 2 to Filesystem


Core#0>md 0x140000
00140000 : 20031985 0000000c e41eb0b1 e0011985  ... ............
00140010 : 0000002b 7d266ee6 00000001 00000000  +....n&}........
00140020 : 00000002 424913b1 00000403 daeea20c  ......IB........
00140030 : 556683ff ff6e6962 e0021985 00000044  ..fUbin.....D...
00140040 : 98f7fb1d 00000002 00000001 000041ed  .............A..
00140050 : 006403e8 00000000 424913b1 424913b1  ..d.......IB..IB
00140060 : 424913b1 00000000 00000000 00000000  ..IB............
00140070 : 00000000 00000000 379225cb e0011985  .........%.7....
00140080 : 0000002b 7d266ee6 00000001 00000001  +....n&}........
00140090 : 00000003 4242dd58 00000403 855955ad  ....X.BB.....UY.
001400a0 : ee322817 ff766564 e0021985 00000044  .(2.dev.....D...
001400b0 : 98f7fb1d 00000003 00000001 000041ed  .............A..
001400c0 : 006403e8 00000000 4242dd58 4242dd58  ..d.....X.BBX.BB
001400d0 : 4242dd58 00000000 00000000 00000000  X.BB............
001400e0 : 00000000 00000000 c54033c0 e0011985  .........3@.....
001400f0 : 0000002b 7d266ee6 00000001 00000002  +....n&}........


I've spotted possible problem here - it seems that kernel overwrites part of 
the rootfs at the begining - I have reserved 0xe0000 for kernel partition, but 
I noticed that my newer kernels are larger than this. Need to check this out...

-- 
..because under Linux "if something is possible in principle,
then it is already implemented or somebody is working on it".

					--LKI

  parent reply	other threads:[~2005-07-19 12:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 10:11 jffs2 problem Hinko Kocevar
2005-07-19 10:32 ` Artem B. Bityuckiy
2005-07-19 10:58   ` Hinko Kocevar
2005-07-19 11:05     ` Artem B. Bityuckiy
2005-07-19 11:45       ` Hinko Kocevar
2005-07-19 12:05         ` Artem B. Bityuckiy
2005-07-19 12:09           ` Steven Scholz
2005-07-19 12:21             ` Artem B. Bityuckiy
2005-07-19 12:19           ` Hinko Kocevar [this message]
2005-07-19 12:30             ` Hinko Kocevar
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10  8:29 JFFS2 problem Amit Kumar Sharma
2006-08-10  9:32 ` Artem B. Bityutskiy
2004-06-09  6:57 jffs2 problem zhang hao
2004-06-09  9:41 ` David Woodhouse
2004-03-22 16:18 JFFS2 problem Michael Palme
2003-07-30  2:37 Vikram Mehta
2002-07-11 13:29 JFFS2 Problem Frederic Giasson
2002-07-10 21:52 Snehaprabha
2002-07-11  7:05 ` David Woodhouse
2002-07-11 19:18   ` Snehaprabha
2002-07-11 19:32     ` Russ Dill
2001-09-03  8:49 jffs2 problem Wojciech Kromer
2001-04-30 22:03 JFFS2 Problem Jeff Smith
2001-05-03 21:55 ` David Woodhouse
2001-03-23  2:02 jffs2 problem Douglas S. J. De Couto
2001-03-23  8:37 ` David Woodhouse
2001-03-23 14:25   ` Douglas S. J. De Couto
2001-03-23 14:31     ` 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=42DCEFD6.8010006@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --cc=dedekind@yandex.ru \
    --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