From: Artem Bityutskiy <dedekind@infradead.org>
To: kyungmin.park@samsung.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI and OneNAND
Date: Tue, 07 Nov 2006 11:16:41 +0200 [thread overview]
Message-ID: <1162891001.31636.8.camel@sauron> (raw)
In-Reply-To: <32544906.187201162866905328.JavaMail.weblogic@ep_ml06>
On Tue, 2006-11-07 at 02:35 +0000, 박경민 wrote:
> Hi,
>
> Sorry for changing subject. My mail program has some problem.
>
> > > I think the following commands just worked:
> > >
> > > mkdir /mnt/nvm
> > > flash_eraseall /dev/mtd6
> > > mount -t jffs2 /dev/mtdblock6 /mnt/nvm
> > >
> > >
> > > I wonder whether this is the first attempt to run a kernel using
> > > jffs2 and ubi and mtd and onenand and mips? First or not, it seems to work.
>
> > Yes, it is. For both onenand and MIPS. That is good news. Thanks for
> > testing!
>
> Umm. I think 'John' just mounts jffs2 without UBI.
>
> I also tried but I can't mount jffs2
>
> It is my sequence.
>
> # mkdir -p /mnt
> # insmod ubi.ko mtd=3
>
> UBI: attached mtd3 to ubi0
> UBI: MTD device name: "rootfs"
> UBI: MTD device size: 16 MB
> UBI: physical eraseblock size: 131072 bytes (128 KB)
> UBI: logical eraseblock size: 126976 bytes
> UBI: number of good PEBs: 127
> UBI: number of bad PEBs: 1
> UBI: smallest flash I/O unit: 2048
> UBI: VID header offset: 2048 (aligned 2048)
> UBI: data offset: 4096
> UBI: max. allowed volumes: 124
> UBI: wear-levelling threshold: 4096
> UBI: number of internal volumes: 2
> UBI: number of user volumes: 0
> UBI: available PEBs: 122
> UBI: total number of reserved PEBs: 5
> UBI: number of PEBs reserved for bad PEB handling: 1
>
May I kindly ask you to do the following:
1. Enable "UBI debugging" option
2. Go to "UBI debugging messages --->" and enable:
a "User interface unit messages"
b "Messages from the gluebi sub-unit"
c "Volume management unit messages"
d "Eraseblock association unit messages"
Then try to mount JFFS2.
Then do:
# mount -t debugfs none /mnt/debugfs
# cat /mnt/debugfs/ubi/log > log
and send me the log file.
Also see http://www.linux-mtd.infradead.org/faq/ubi.html#L_how_debug
which is a bit out-of-date but still may be helpful.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-07 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 2:35 UBI and OneNAND 박경민
2006-11-07 8:50 ` Frank Haverkamp
2006-11-07 10:20 ` John Smith
2006-11-07 11:39 ` Artem Bityutskiy
2006-11-07 11:47 ` Josh Boyer
2006-11-07 14:10 ` Artem Bityutskiy
2006-11-07 14:24 ` Josh Boyer
2006-11-07 14:39 ` Artem Bityutskiy
2006-11-07 9:16 ` Artem Bityutskiy [this message]
2006-11-08 16:03 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2006-11-07 12:52 Kyungmin Park
2006-11-08 16:09 ` Artem Bityutskiy
2006-11-04 8:22 UBI and OneNand John
2006-11-06 9:46 ` Frank Haverkamp
2006-11-06 13:18 ` Artem Bityutskiy
2006-11-06 20:16 ` John Smith
2006-11-06 20:54 ` Josh Boyer
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=1162891001.31636.8.camel@sauron \
--to=dedekind@infradead.org \
--cc=kyungmin.park@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.