This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

There is no mtdblockx under /dev

I compiled a new dm646x kernel image for my dm6467 platform. When starting the system using the new kernel image, some logs indicating flash bad eraseblocks show up like the following:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@localhost.localdomain) (gcc version 4.2.0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #4 PREEMPT Thu Jun 6 13:55:38 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DM646x EVM
Memory policy: ECC disabled, Data cache writeback
DaVinci dm6467_rev3.x variant 0x1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 28448
Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.30.240:/home/comeback/myrootfs,v3,nolock mem=112M eth=00:0E:FF:FF:FF:80 ip=192.168.30.249:192.168.30.240:192.168.30.240
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 112MB = 112MB total
Memory: 110140k/110140k available, 4548k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xff000000 - 0xffe00000 ( 14 MB)
vmalloc : 0xc7800000 - 0xfea00000 ( 882 MB)
lowmem : 0xc0000000 - 0xc7000000 ( 112 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0029000 ( 132 kB)
.text : 0xc0029000 - 0xc0323000 (3048 kB)
.data : 0xc0324000 - 0xc0342fa0 ( 124 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 147.86 BogoMIPS (lpj=739328)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 43 gpio irqs
NET: Registered protocol family 16
MUX: Setting register STSOMUX_DISABLE
PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000
MUX: Setting register STSIMUX_DISABLE
PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000
MUX: Setting register PTSOMUX_DISABLE
PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000
MUX: Setting register PTSIMUX_DISABLE
PINMUX0 (0x00000000) = 0x00000000 -> 0x00000000
bio: create slab <bio-0> at 0
pcf857x: probe of 1-0038 failed with error -121
Switching to clocksource timer0_1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 215
io scheduler noop registered (default)
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a ST16654
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x1c20400 (irq = 41) is a ST16650V2
serial8250.0: ttyS2 at MMIO 0x1c20800 (irq = 42) is a ST16650V2
brd: module loaded
NAND device: Maf ID: 0x20, Chip ID: 0xf1 (ST Micro, )
erasesize: 0x20000, writesize: 2048, oobsize: 64
Scanning device for bad blocks
Bad eraseblock 550 at 0x0000044c0000
Bad eraseblock 551 at 0x0000044e0000
Bad eraseblock 552 at 0x000004500000
Bad eraseblock 553 at 0x000004520000
Bad eraseblock 554 at 0x000004540000
Bad eraseblock 555 at 0x000004560000
Bad eraseblock 556 at 0x000004580000
Bad eraseblock 557 at 0x0000045a0000
Bad eraseblock 558 at 0x0000045c0000

………………………………

Bad eraseblock 798 at 0x0000063c0000
Bad eraseblock 799 at 0x0000063e0000
Bad eraseblock 800 at 0x000006400000
Bad eraseblock 801 at 0x000006420000
Bad eraseblock 803 at 0x000006460000
Creating 5 MTD partitions on "davinci_nand.0":
0x000000000000-0x000000080000 : "bootloader"
0x000000080000-0x0000000a0000 : "params"
0x0000000a0000-0x0000004a0000 : "kernel"
0x0000004a0000-0x0000044a0000 : "filesystem"
0x0000044a0000-0x000008000000 : "yaffs2"
davinci_nand davinci_nand.0: controller rev. 2.2
davinci_mdio davinci_mdio.0: davinci mdio revision 1.4
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver ET1011C
dm9000 Ethernet Driver, V1.31
console [netcon0] enabled
netconsole: network logging started
i2c /dev entries driver
TCP cubic registered
NET: Registered protocol family 17
davinci_emac_probe: using random MAC addr: ce:e1:c1:42:2c:74
net eth0: attached PHY driver [ET1011C] (mii_bus:phy_addr=0:01, id=282f014)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, addr=192.168.30.249, mask=255.255.255.0, gw=192.168.30.240,
host=192.168.30.249, domain=, nis-domain=(none),
bootserver=192.168.30.240, rootserver=192.168.30.240, rootpath=
PHY: 0:01 - Link is Up - 100/Full
VFS: Mounted root (nfs filesystem) on device 0:12.
Freeing init memory: 132K
starting pid 839, tty '': '/etc/init.d/rcS'

Please press Enter to activate this console. 
starting pid 846, tty '/dev/console': '-/bin/sh'

Another thing, when system is booted up, I find that there are only mtdx, but no mtdblockx, under /dev.

/ # ls /dev/mtd*
/dev/mtd0 /dev/mtd1 /dev/mtd2 /dev/mtd3 /dev/mtd4
/dev/mtd0ro /dev/mtd1ro /dev/mtd2ro /dev/mtd3ro /dev/mtd4ro

/ # cat /proc/mtd 

dev: size erasesize name
mtd0: 00080000 00020000 "bootloader"
mtd1: 00020000 00020000 "params"
mtd2: 00400000 00020000 "kernel"
mtd3: 04000000 00020000 "filesystem"
mtd4: 03b60000 00020000 "yaffs2"

However, when using the old image, there is nothing special happened. I think it is due to the new kernel image, but I do not know how to fix it.