From: "Andre" <andre@rocklandocean.com>
To: <linux-mtd@lists.infradead.org>
Cc: fabrice.bellard@netgem.com, tglx@linutronix.de,
dwmw2@infradead.org, gerg@snapgear.com
Subject: kernel messages from INFTL
Date: Tue, 21 Jun 2005 15:06:09 -0700 [thread overview]
Message-ID: <006301c576ad$70547490$6702a8c0@niro> (raw)
First of all, thank you Thomas for your help on trying to get my
diskonchip2000 to be recognized by linuxmtd.
After enabling the right config flags in the kernel, I can now mount my
diskonchip2000.
There were some messages during the initial loading of the inftl module that
frightened me a bit. Here is the entire output from dmesg:
==================
DiskOnChip found at 0xd0000
Detected 3 chips per floor.
NAND device: Manufacturer ID: 0xec, Chip ID: 0x79 (Samsung NAND 128MiB 3,3V
8-bit)
3 NAND chips detected
Bad block table not found for chip 0
Bad block table not found for chip 0
Found DiskOnChip BNAND Media Header at 0x4000
bootRecordID = BNAND
NoOfBootImageBlocks = 0
NoOfBinaryPartitions = 1
NoOfBDTLPartitions = 1
BlockMultiplerBits = 0
FormatFlgs = 1
OsakVersion = 5.1.4.0
PercentUsed = 98
PARTITION[0] ->
virtualUnits = 4
firstUnit = 2
lastUnit = 5
flags = 0x20000000
spareUnits = 0
PARTITION[1] ->
virtualUnits = 24072
firstUnit = 11
lastUnit = 24575
flags = 0xc0000000
spareUnits = 2
Creating 2 MTD partitions on "DiskOnChip 2000 (INFTL Model)":
0x00008000-0x00018000 : " DiskOnChip BDK partition"
0x0002c000-0x18000000 : " DiskOnChip BDTL partition"
<Andre> looks ok up until here
INFTL: inftlcore.c $Revision: 1.18 $, inftlmount.c $Revision: 1.16 $
INFTL: corrupt block 10588 in chain 10588, chain length 0, erase mark 0x0?
INFTL: formatting chain at block 10588
INFTL: formatting block 10588
INFTL: error while formatting block 10588
INFTL: corrupt block 15274 in chain 15274, chain length 0, erase mark 0x0?
INFTL: formatting chain at block 15274
INFTL: formatting block 15274
INFTL: error while formatting block 15274
INFTL: corrupt block 21286 in chain 21286, chain length 0, erase mark 0x0?
INFTL: formatting chain at block 21286
INFTL: formatting block 21286
INFTL: error while formatting block 21286
INFTL: corrupt block 24574 in chain 24574, chain length 0, erase mark
0xffff?
INFTL: formatting chain at block 24574
INFTL: formatting block 24574
INFTL: corrupt block 24575 in chain 24575, chain length 0, erase mark
0xffff?
INFTL: formatting chain at block 24575
INFTL: formatting block 24575
inftla: inftla1
==================
The INFTL messages do not appear on subsequent loads of the inftl module.
Can somebody please explain what happened, i.e. should I be concerned?
/proc/mtd:
mtd0: 18000000 00004000 "DiskOnChip 2000 (INFTL Model)"
mtd1: 00010000 00004000 " DiskOnChip BDK partition"
mtd2: 17fd4000 00004000 " DiskOnChip BDTL partition"
cheers,
Andre
next reply other threads:[~2005-06-21 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 22:06 Andre [this message]
2005-06-22 22:59 ` kernel messages from INFTL Andre
2005-06-30 6:30 ` Greg Ungerer
2005-06-30 17:52 ` Andre
2005-07-05 4:55 ` Greg Ungerer
2005-07-06 17:01 ` Andre
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='006301c576ad$70547490$6702a8c0@niro' \
--to=andre@rocklandocean.com \
--cc=dwmw2@infradead.org \
--cc=fabrice.bellard@netgem.com \
--cc=gerg@snapgear.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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