public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: Tino Keitel <tino.keitel@innominate.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 error with gcc 3.3.2
Date: Tue, 27 Apr 2004 17:26:06 +0200	[thread overview]
Message-ID: <1083079565.3620.174.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <20040427141926.GA23637@dose.home.local>

I used once jffs2 over blkmtd on compact flash (ide)  
on a powerpc system, all built with gcc 3.3.2 (and linux 2.4.25) 
and had no problems beside that mounting was very slow.

regards,

Jaap-Jan

On Tue, 2004-04-27 at 16:19, Tino Keitel wrote:
> Hi folks,                                            
>                                                      
> I build a kernel 2.4.25 for ARM XScale using the MTD CVS version from
> last week with a plain gcc 3.3.2 and binutils 2.14. When the kernel
> mounts the root-FS, I get this message:
>    
> VFS: Mounted root (jffs2 filesystem).                     
> Mounted devfs on /dev                
> Freeing init memory: 68K  
> jffs2_get_inode_nodes(): CRC failed on node at 0x00d063a8: Read
> 0x648da27a, calculated 0xaad091fe                    
> jffs2_do_read_inode(): No data nodes found for ino #513                       
> jffs2_get_inode_nodes(): Data CRC failed on node at 0x00d7aea4: Read   
> 0xc9706472, calculated 0xfb804e0f                    
> jffs2_do_read_inode(): No data nodes found for ino #451                       
> Kernel panic: No init found.  Try passing init= option to kernel.
>                                                                  
> After a reboot, the filesystem is completly trashed:
> 
> VFS: Mounted root (jffs2 filesystem).
> Mounted devfs on /dev                                            
> Freeing init memory: 68K                                         
> jffs2_do_read_inode() on nonexistent ino 513
> jffs2_do_read_inode() on nonexistent ino 451                     
> Kernel panic: No init found.  Try passing init= option to kernel.
> 
> The filesystem worked before this with a kernel wich was built with gcc
> 2.95.3. Are there any known issues regarding jffs2 and gcc 3.x?
> 
> Regards,
> Tino
>    
-- 
J.G.J. Boor                       Anton Philipsweg 1
Software Engineer                 1223 KZ Hilversum
AimSys bv                         tel. +31 35 689 1941
Postbus 2194, 1200 CD Hilversum   mailto:jjboor@aimsys.nl

  reply	other threads:[~2004-04-27 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 14:19 jffs2 error with gcc 3.3.2 Tino Keitel
2004-04-27 15:26 ` Jaap-Jan Boor [this message]
2004-04-28 11:18 ` Tino Keitel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1083079565.3620.174.camel@linpc003.aimsys.nl \
    --to=jjboor@aimsys.nl \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tino.keitel@innominate.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox