From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from compulab.co.il ([67.18.134.219]) by bombadil.infradead.org with esmtps (Exim 4.69 #1 (Red Hat Linux)) id 1MbSoL-0002lj-MC for linux-mtd@lists.infradead.org; Thu, 13 Aug 2009 05:25:17 +0000 Message-ID: <4A83A3B2.4070300@compulab.co.il> Date: Thu, 13 Aug 2009 08:25:06 +0300 From: Mike Rapoport MIME-Version: 1.0 To: Saurabh Kadekodi , linux-mtd Subject: Re: Problem with nand flash while booting 2.6.30 References: <967093cd0908120036q51283790se400dc08219daed@mail.gmail.com> <4A82DBE7.3090901@compulab.co.il> <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com> In-Reply-To: <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi Saurabh, (Adding linux-mtd back to CC) Saurabh Kadekodi wrote: > Hi Mike, > > I have already enabled the NAND_BUILTIN in the kernel configuration. > That is why it iterated through all the providers and then since it > couldn't match any of the providers it printed 'Unknown'. Try setting .keep_config in pxa3xx_nand_platform_data in your board configuration file. This will tell the driver to preserve controller settings set up by the bootloader. > Actually it is a Micron Nand flash. > > It can't be a jffs2 problem since the driver itself cannot recognize > the hardware. Can it be timing related? > > Thanks and Regards, > > Saurabh > > > > On Wed, Aug 12, 2009 at 8:42 PM, Mike Rapoport wrote: >> >> Saurabh Kadekodi wrote: >>> Hi All, >>> >>> I am working on a board with pxa320 processor. It has a micron 128 mb >>> flash. It boots well with kernel 2.6.25, but when booting with 2.6.30, >>> it somehow cannot detect the nand chip properly. >>> >>> It shows following messages: >>> >>> NAND device: Manufacturer ID: 0x00, Chip ID: 0xa1 (Unknown NAND 128MiB >>> 1,8V 8-bit) >>> >>> While with 2.6.25 it properly detects as a micron flash. >> Make sure that you either select CONFIG_MTD_NAND_PXA3xx_BUILTIN or set >> .keep_config flag in pxa3xx_nand_platform_data in your board configuration. >> >>> Then later it gives a lot of ECC errors and prints the following messages: >>> >>> >>> Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes >>>> empty_blocks 0, bad_blocks 208, c->nr_blocks 438 >>>> VFS: Cannot open root device "mtdblock2" or unknown-block(31,2) >>>> Please append a correct "root=" boot option; here are the available partitions: >>>> 1f00 256 mtdblock0 (driver?) >>>> 1f01 2048 mtdblock1 (driver?) >>>> 1f02 112128 mtdblock2 (driver?) >>>> 1f03 512 mtdblock3 (driver?) >>>> b300 2008064 mmcblk0 driver: mmcblk >>>> b301 31288 mmcblk0p1 >>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) >>>> Backtrace: >>>> [] (dump_backtrace+0x0/0x110) from [] (dump_stack+0x18/0x1c) >>>> r6:c03af144 r5:c001d884 r4:cf81df54 >>>> [] (dump_stack+0x0/0x1c) from [] (panic+0x60/0x13c) >>>> [] (panic+0x0/0x13c) from [] (mount_block_root+0x104/0x234) >>>> r3:00000000 r2:20000013 r1:cf81df54 r0:c0330e50 >>>> [] (mount_block_root+0x0/0x234) from [] (mount_root+0xdc/0x100) >>>> [] (mount_root+0x0/0x100) from [] (prepare_namespace+0x48/0x190) >>>> r7:00000000 r6:c001d840 r5:c001d83c r4:c03ae0c4 >>>> [] (prepare_namespace+0x0/0x190) from [] (kernel_init+0xc8/0xf4) >>>> r6:c001cdec r5:c001cb58 r4:c03ae0b8 >>>> [] (kernel_init+0x0/0xf4) from [] (do_exit+0x0/0x6c8) >>>> r6:00000000 r5:00000000 r4:00000000 >>>> >>>> >>> Please can someone guide me as to what maybe wrong. The flash cannot >>> be corrupt as >>> 2.6.25 boots correctly. Then where am I going wrong? >>> >>> Thanks in advance, >>> >>> Saurabh >>> >>> ______________________________________________________ >>> Linux MTD discussion mailing list >>> http://lists.infradead.org/mailman/listinfo/linux-mtd/ >>> >> -- >> Sincerely yours, >> Mike. >> >> > -- Sincerely yours, Mike.