public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Steve Tsai" <startec@ms11.hinet.net>
To: "Linux MTD mailing list" <linux-mtd@lists.infradead.org>
Subject: nand_write_ecc
Date: Thu, 25 Jul 2002 15:33:41 +0800	[thread overview]
Message-ID: <002801c233ad$a2d39810$5501a8c0@synso.com.tw> (raw)

I am using NAND flash as a root file system. When I and flash a new root
image to NAND flash and reboot the system. I copy a file to flash and
the system halt.  I got the following message when I operate the board. 
When nand_write_ecc  was called, I will print out message as,
"nand_write_ecc: col=%d last=%d page=%x ecc_code=%x %x %x %x %x %x". I
think the first nand_write_ecc was called by GC and when I copy the file
nand_write_ecc was called again. But as the following message, the two
calls write to the same page 0x18FF. Why they write the same page?

Steve Tsai


/home> cd /bin
nand_write_ecc: col=0 last=512 page=18ff ecc_code=c3 33 f ff ff ff

/bin>
/bin>
/bin>
/bin> cp test test3
ARGH. About to write node to 0x0011fe90 on flash, but there's data
already there
:
0x0011fe90: 85 19 04 20 70 01 00 00 1a f5 30 d9 ff ff ff ff
nand_write_ecc: col=0 last=512 page=18ff ecc_code=ff c0 f c0 c0 ff
nand_write_ecc: Failed write verify, page 0x000018ff
<2>jffs2_flush_wbuf(): Writ
e failed with -5
nand_write_ecc: col=0 last=512 page=18ff ecc_code=ff c0 f c0 c0 ff
nand_write_ecc: Failed write verify, page 0x000018ff
<2>jffs2_flush_wbuf(): Writ
e failed with -5
Write of 2269 bytes at 0x0044400c failed. returned -5, retlen 0
Not marking the space at 0x0044400c as dirty because the flash driver
returned r
etlen zero

             reply	other threads:[~2002-07-25  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  7:33 Steve Tsai [this message]
2002-07-30 22:40 ` nand_write_ecc David Woodhouse

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='002801c233ad$a2d39810$5501a8c0@synso.com.tw' \
    --to=startec@ms11.hinet.net \
    --cc=linux-mtd@lists.infradead.org \
    /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