2011-08-23 13:29:03     mtd assignment error upon boot

Document created by Aaronwu Employee on Aug 27, 2013
Version 1Show Document
  • View in full screen mode

2011-08-23 13:29:03     mtd assignment error upon boot

Rob Maris (GERMANY)

Message: 103093   

 

While updating to Linux 3.0.0 I'm encountering an error which I cannot explain. Last OK boot was kernel 2.6.39.2.

 

Boot log excerpt:

 

gpio-addr-flash: probing 16-bit flash bus

gpio-addr-flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x008820

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Using buffer write method

Using auto-unlock on power-up/resume

cfi_cmdset_0001: Erase suspend on write enabled

3 cmdlinepart partitions found on MTD device gpio-addr-flash

gpio-addr-flash: Using commandline partition definition

Creating 3 MTD partitions on "gpio-addr-flash":

0x000000000000-0x080001ed0074 : "uboot"

Data access CPLB miss

<5> - Used by the MMU to signal a CPLB miss on a data access.

Kernel OOPS in progress

Deferred Exception context

CURRENT PROCESS:

COMM=swapper PID=1  CPU=0

invalid mm

 

Of course, the uboot size is fully wrong. Correct is 0x000000040000.

 

From tcm-bf537.c (where it is ensured that this section is built):

 

#if defined(CONFIG_MTD_GPIO_ADDR) || defined(CONFIG_MTD_GPIO_ADDR_MODULE)

static struct mtd_partition cm_partitions[] = {

{

.name   = "bootloader(nor)",

.size   = 0x40000,

.offset = 0,

}, {

.name   = "linux kernel(nor)",

.size   = 0x100000,

.offset = MTDPART_OFS_APPEND,

}, {

.name   = "file system(nor)",

.size   = MTDPART_SIZ_FULL,

.offset = MTDPART_OFS_APPEND,

}

};

 

 

Where to look for the cause of this problem?

 

 

.

QuoteReplyEditDelete

 

 

2011-08-23 14:01:45     Re: mtd assignment error upon boot

Rob Maris (GERMANY)

Message: 103094   

 

Well, it's the command line args that is screwed up while processing, not the structs in the quoted source, which is printed correcly during boot as:

 

Kernel command line: root=/dev/mtdblock0 rw mtdparts=gpio-addr-flash:256k(uboot),5888k(kernel_rootfs),-(user) console=ttyBF0,115200 ip=192.168.1.70:192.168.1.64:192.168.1.254:255.255.255.0:tcm-bf537:eth0:off

Attachments

    Outcomes