Linux booting problem when initializing flash file system

Linux booting problem when initializing flash file system

[Atit_Shah]

Hi All,

	I am using a board which has a ST Micro Electronics Flash
(M29W640DB) and when booting the Linux Kernel I get the following error:

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x0020 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0x22df instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0x0008 instead

Further such events for this erase block will not be printed
JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000:
0x0020 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004:
0x22df instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c:
0x0008 instead

And it ends with................

Cowardly refusing to erase blocks on filesystem with no valid JFFS2
nodes
Kernel panic: VFS: Unable to mount root fs on 1f:00
<0>Rebooting in 180 seconds..

The reference board using an AMD flash works fine. I selected the ST
Flash from make xconfig in Linux but the kernel crashes before it even
calls start_kernel.
Could somebody suggest wrong....

Thanks
Atit




DISCLAIMER:
This email (including any attachments) is intended for the sole use of =
the intended recipient/s and may contain material that is CONFIDENTIAL =
AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or =
copying or distribution or forwarding of any or all of the contents in =
this message is STRICTLY PROHIBITED. If you are not the intended =
recipient, please contact the sender by email and delete all copies; =
your cooperation in this regard is appreciated.

Re: Linux booting problem when initializing flash file system

[Robin Gilks]

Atit_Shah wrote:
> Hi All,
> 
> 	I am using a board which has a ST Micro Electronics Flash
> (M29W640DB) and when booting the Linux Kernel I get the following error:
> 
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
> 0x0020 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
> 0x22df instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
> 0x0008 instead
> 
> Further such events for this erase block will not be printed
> JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000:
> 0x0020 instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004:
> 0x22df instead
> jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c:
> 0x0008 instead
> 
> And it ends with................
> 
> Cowardly refusing to erase blocks on filesystem with no valid JFFS2
> nodes
> Kernel panic: VFS: Unable to mount root fs on 1f:00
> <0>Rebooting in 180 seconds..
> 
> The reference board using an AMD flash works fine. I selected the ST
> Flash from make xconfig in Linux but the kernel crashes before it even
> calls start_kernel.
> Could somebody suggest wrong....
> 
> Thanks
> Atit

If the M29W640DB has the same problem as the M28W640ECB that I've used, 
then a fixup table entry may be required in drivers/mtd/cfi_cmdset_0001 
to say that buffered write is not supported.

You don't say which kernel or mtd version you are using - I'm assuming 
2.4 and an mtd about a year old!!

-- 
Robin Gilks
Senior Design Engineer          Phone: (+64)(3) 357 1569
Tait Electronics                Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@tait.co.nz
New Zealand

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================