* Problem with nand flash while booting 2.6.30
@ 2009-08-12 7:36 Saurabh Kadekodi
2009-08-12 15:12 ` Mike Rapoport
2009-08-12 17:17 ` Leo (Hao) Chen
0 siblings, 2 replies; 5+ messages in thread
From: Saurabh Kadekodi @ 2009-08-12 7:36 UTC (permalink / raw)
To: linux-mtd
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.
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:
> [<c0028a34>] (dump_backtrace+0x0/0x110) from [<c0028b78>] (dump_stack+0x18/0x1c)
> r6:c03af144 r5:c001d884 r4:cf81df54
> [<c0028b60>] (dump_stack+0x0/0x1c) from [<c003ca9c>] (panic+0x60/0x13c)
> [<c003ca3c>] (panic+0x0/0x13c) from [<c0008dac>] (mount_block_root+0x104/0x234)
> r3:00000000 r2:20000013 r1:cf81df54 r0:c0330e50
> [<c0008ca8>] (mount_block_root+0x0/0x234) from [<c0008fb8>] (mount_root+0xdc/0x100)
> [<c0008edc>] (mount_root+0x0/0x100) from [<c0009024>] (prepare_namespace+0x48/0x190)
> r7:00000000 r6:c001d840 r5:c001d83c r4:c03ae0c4
> [<c0008fdc>] (prepare_namespace+0x0/0x190) from [<c00087dc>] (kernel_init+0xc8/0xf4)
> r6:c001cdec r5:c001cb58 r4:c03ae0b8
> [<c0008714>] (kernel_init+0x0/0xf4) from [<c003fc90>] (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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Problem with nand flash while booting 2.6.30 2009-08-12 7:36 Problem with nand flash while booting 2.6.30 Saurabh Kadekodi @ 2009-08-12 15:12 ` Mike Rapoport [not found] ` <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com> 2009-08-12 17:17 ` Leo (Hao) Chen 1 sibling, 1 reply; 5+ messages in thread From: Mike Rapoport @ 2009-08-12 15:12 UTC (permalink / raw) To: Saurabh Kadekodi; +Cc: linux-mtd 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: >> [<c0028a34>] (dump_backtrace+0x0/0x110) from [<c0028b78>] (dump_stack+0x18/0x1c) >> r6:c03af144 r5:c001d884 r4:cf81df54 >> [<c0028b60>] (dump_stack+0x0/0x1c) from [<c003ca9c>] (panic+0x60/0x13c) >> [<c003ca3c>] (panic+0x0/0x13c) from [<c0008dac>] (mount_block_root+0x104/0x234) >> r3:00000000 r2:20000013 r1:cf81df54 r0:c0330e50 >> [<c0008ca8>] (mount_block_root+0x0/0x234) from [<c0008fb8>] (mount_root+0xdc/0x100) >> [<c0008edc>] (mount_root+0x0/0x100) from [<c0009024>] (prepare_namespace+0x48/0x190) >> r7:00000000 r6:c001d840 r5:c001d83c r4:c03ae0c4 >> [<c0008fdc>] (prepare_namespace+0x0/0x190) from [<c00087dc>] (kernel_init+0xc8/0xf4) >> r6:c001cdec r5:c001cb58 r4:c03ae0b8 >> [<c0008714>] (kernel_init+0x0/0xf4) from [<c003fc90>] (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. ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com>]
* Re: Problem with nand flash while booting 2.6.30 [not found] ` <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com> @ 2009-08-13 5:25 ` Mike Rapoport 2009-08-13 7:12 ` Saurabh Kadekodi 0 siblings, 1 reply; 5+ messages in thread From: Mike Rapoport @ 2009-08-13 5:25 UTC (permalink / raw) To: Saurabh Kadekodi, linux-mtd 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<mike@compulab.co.il> 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: >>>> [<c0028a34>] (dump_backtrace+0x0/0x110) from [<c0028b78>] (dump_stack+0x18/0x1c) >>>> r6:c03af144 r5:c001d884 r4:cf81df54 >>>> [<c0028b60>] (dump_stack+0x0/0x1c) from [<c003ca9c>] (panic+0x60/0x13c) >>>> [<c003ca3c>] (panic+0x0/0x13c) from [<c0008dac>] (mount_block_root+0x104/0x234) >>>> r3:00000000 r2:20000013 r1:cf81df54 r0:c0330e50 >>>> [<c0008ca8>] (mount_block_root+0x0/0x234) from [<c0008fb8>] (mount_root+0xdc/0x100) >>>> [<c0008edc>] (mount_root+0x0/0x100) from [<c0009024>] (prepare_namespace+0x48/0x190) >>>> r7:00000000 r6:c001d840 r5:c001d83c r4:c03ae0c4 >>>> [<c0008fdc>] (prepare_namespace+0x0/0x190) from [<c00087dc>] (kernel_init+0xc8/0xf4) >>>> r6:c001cdec r5:c001cb58 r4:c03ae0b8 >>>> [<c0008714>] (kernel_init+0x0/0xf4) from [<c003fc90>] (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. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problem with nand flash while booting 2.6.30 2009-08-13 5:25 ` Mike Rapoport @ 2009-08-13 7:12 ` Saurabh Kadekodi 0 siblings, 0 replies; 5+ messages in thread From: Saurabh Kadekodi @ 2009-08-13 7:12 UTC (permalink / raw) To: Mike Rapoport, linux-mtd Hi Mike, Thanks for the solution. That really helped. Board is now recognising the flash device. Regards, Saurabh On Thu, Aug 13, 2009 at 10:55 AM, Mike Rapoport<mike@compulab.co.il> wrote: > 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<mike@compulab.co.il> 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: >>>>> [<c0028a34>] (dump_backtrace+0x0/0x110) from [<c0028b78>] (dump_stack+0x18/0x1c) >>>>> r6:c03af144 r5:c001d884 r4:cf81df54 >>>>> [<c0028b60>] (dump_stack+0x0/0x1c) from [<c003ca9c>] (panic+0x60/0x13c) >>>>> [<c003ca3c>] (panic+0x0/0x13c) from [<c0008dac>] (mount_block_root+0x104/0x234) >>>>> r3:00000000 r2:20000013 r1:cf81df54 r0:c0330e50 >>>>> [<c0008ca8>] (mount_block_root+0x0/0x234) from [<c0008fb8>] (mount_root+0xdc/0x100) >>>>> [<c0008edc>] (mount_root+0x0/0x100) from [<c0009024>] (prepare_namespace+0x48/0x190) >>>>> r7:00000000 r6:c001d840 r5:c001d83c r4:c03ae0c4 >>>>> [<c0008fdc>] (prepare_namespace+0x0/0x190) from [<c00087dc>] (kernel_init+0xc8/0xf4) >>>>> r6:c001cdec r5:c001cb58 r4:c03ae0b8 >>>>> [<c0008714>] (kernel_init+0x0/0xf4) from [<c003fc90>] (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. > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problem with nand flash while booting 2.6.30 2009-08-12 7:36 Problem with nand flash while booting 2.6.30 Saurabh Kadekodi 2009-08-12 15:12 ` Mike Rapoport @ 2009-08-12 17:17 ` Leo (Hao) Chen 1 sibling, 0 replies; 5+ messages in thread From: Leo (Hao) Chen @ 2009-08-12 17:17 UTC (permalink / raw) To: Saurabh Kadekodi; +Cc: linux-mtd@lists.infradead.org On Wed, Aug 12, 2009 at 12:36:53AM -0700, Saurabh Kadekodi wrote: > > 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 You may try to re-burn the rootfs to your flash. I had experienced similar problem when I switched my kernel from 2.6.27 to 2.6.30. I don't know the exact reason, but the ECC algorithm or something may have been changed. -- Leo Hao Chen Software Engineer Broadcom Canada Inc. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-08-13 7:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-08-12 7:36 Problem with nand flash while booting 2.6.30 Saurabh Kadekodi
2009-08-12 15:12 ` Mike Rapoport
[not found] ` <967093cd0908122207q5198dfe8j207455c477dacf23@mail.gmail.com>
2009-08-13 5:25 ` Mike Rapoport
2009-08-13 7:12 ` Saurabh Kadekodi
2009-08-12 17:17 ` Leo (Hao) Chen
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.