From: Wolfgang Denk Date: Sun, 24 May 2009 23:10:24 +0200 Subject: [U-Boot] [RFC/PATCH] jffs2/mtdparts: Fix problem with usage from JFFS2 and MTDPARTS together In-Reply-To: <200905201201.50810.sr@denx.de> References: <1242468262-25814-1-git-send-email-sr@denx.de> <20090517135428.0B53D832E416@gemini.denx.de> <200905201201.50810.sr@denx.de> Message-ID: <20090524211024.56F71832E416@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Stefan Roese, In message <200905201201.50810.sr@denx.de> you wrote: > > > => fsinfo > > ### filesystem type is JFFS2 > > Scanning JFFS2 FS: read_nand_cached: error reading nand off 0xabfe00 size > > 8192 bytes read_nand_cached: error reading nand off 0xadfe00 size 8192 > > bytes > > read_nand_cached: error reading nand off 0xac0000 size 8192 bytes > > read_nand_cached: error reading nand off 0xaffe00 size 8192 bytes > > > > > The addresses where the read errors occur don't seem to be related to > > the bad blocks reported by Linux. > > No. What does a "normal" "nand read" return when reading this complete > partition into RAM? On PPC4xx it returned -117 here. I fixed it with the > already posted patches for the 4xx NDFC ECC byte ordering. Perhaps the TQM8548 > has similar incompatibility issues with the Linux kernel here too? I get this: => nand read 200000 0 1000000 NAND read: device 0 offset 0x0, size 0x1000000 NAND read from offset 0 failed -74 16777216 bytes read: ERROR Hm, this is indeed a very helpful message. What does it tell you? I can't parse that. May we please have more readable error messages from the NAND code? Please?! Is this -74 decimal as EBADMSG or -0x74 = NAND_CMD_STATUS_ERROR1 ? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Being schizophrenic is better than living alone.