From eddie@embeddedarm.com Fri Apr 24 19:55:10 2009 Received: from oz.embeddedarm.com ([67.40.67.44]) by stoneboat.aleph1.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1LxQYC-00038q-H3 for yaffs@lists.aleph1.co.uk; Fri, 24 Apr 2009 19:55:10 +0100 Received: from [192.168.0.200] (oz3 [192.168.0.200]) by oz.embeddedARM.com (8.12.11.20060614/8.11.6) with ESMTP id n3OIsbdp004598; Fri, 24 Apr 2009 11:54:37 -0700 (MST) Message-ID: <49F20BBA.1010601@embeddedarm.com> Date: Fri, 24 Apr 2009 11:58:02 -0700 From: Eddie Dawydiuk Organization: Technologic Systems User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Eddie Dawydiuk References: <49F20A22.1080906@embeddedarm.com> In-Reply-To: <49F20A22.1080906@embeddedarm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (oz.embeddedARM.com [192.168.0.11]); Fri, 24 Apr 2009 11:54:37 -0700 (MST) X-SA-Exim-Connect-IP: 67.40.67.44 X-SA-Exim-Mail-From: eddie@embeddedarm.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Cc: yaffs@lists.aleph1.co.uk Subject: Re: [Yaffs] fs/buffer.c errors with Yaffs X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 18:55:10 -0000 Hello, Well I should have looked up where the "uncorrectable error" was coming from before sending out this email. It looks like the MTD layer is getting multi-bit errors and hence can't correct the error. It's kind of interesting that the ECC failures don't affect the data I wrote, that is I can read back the data properly. The other interesting thing I noticed is the sectors where the failures occur appear to be multiples of 8? Eddie Dawydiuk wrote: > Hello, > > I'm running a 2.6.28 Linux kernel with Yaffs2(checked out 04/22/2009). > Were using a 512 MB (2K sector) nand flash chip and I'm currently in the > testing phase. I've found if I transfer large files (approx 400MB) I get > the following errors when I remount the Yaffs filesystem. > > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 0 > __ratelimit: 11 callbacks suppressed > Buffer I/O error on device mtdblock3, logical block 0 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 8 > Buffer I/O error on device mtdblock3, logical block 1 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 16 > Buffer I/O error on device mtdblock3, logical block 2 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 24 > Buffer I/O error on device mtdblock3, logical block 3 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 32 > Buffer I/O error on device mtdblock3, logical block 4 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 40 > Buffer I/O error on device mtdblock3, logical block 5 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 48 > Buffer I/O error on device mtdblock3, logical block 6 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 56 > Buffer I/O error on device mtdblock3, logical block 7 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 64 > Buffer I/O error on device mtdblock3, logical block 8 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 72 > Buffer I/O error on device mtdblock3, logical block 9 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 80 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 88 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 96 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 104 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 112 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 120 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 128 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 0 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 528 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 528 > uncorrectable error : <3>end_request: I/O error, dev mtdblock3, sector 528 > > The large file reads back correctly though(no data corruption). Has > anyone else seen any similiar failures or have any pointers? I've turned > on Yaffs tracing but it's no help seeing as though these messages are > not coming from Yaffs... > > > I'm not sure if MTD would be a more appropriate list to post this to...? > -- Best Regards, ________________________________________________________________ Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200 16525 East Laser Drive | fax: (480) 837-5300 Fountain Hills, AZ 85268 | web: www.embeddedARM.com