public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: linux-mtd@lists.infradead.org
Subject: Again 2.6.18-RC6 XScale P30 issues
Date: Fri, 08 Sep 2006 17:27:34 +0200	[thread overview]
Message-ID: <45018BE6.5040102@kernelconcepts.de> (raw)

Hi, me again ...
I am sorry to bother you again, but I still have issues withe the P30
flashes.
Now that I can write to the chips I tested it a little more. After a
fresh write of a clean rootfs I can create and delete files almost fine
(I just get very few CRC errors but everything else works OK, also the
files are intact).

But after creating and deleting files and a reboot I get:

----------
[42949375.760000] Write of 68 bytes at 0x00cf91d0 failed. returned -30,
retlen 0
[42949375.770000] Not marking the space at 0x00cf91d0 as dirty because
the flash driver returned retlen zero
[42949375.780000] Write of 68 bytes at 0x00cf91d0 failed. returned -30,
retlen 0
[42949375.780000] Not marking the space at 0x00cf91d0 as dirty because
the flash driver returned retlen zero
ifup: /var/run/ifstate: Read-only file system

............

Starting telnetd...
Starting slideshow with images from the internal flash...
Starting pid 695, console /dev/ttyS0: '/bin/sh'

Processing /etc/profile... Done
[@colineator /]#cd
[@colineator /root]#ls -l
-rw-r--r--    1 0        0         5242880 Jan  1 00:14 blub
[@colineator /root]#rm blub
[42949387.590000] Write of 44 bytes at 0x00cf91d0 failed. returned -30,
retlen 0
[42949387.600000] Not marking the space at 0x00cf91d0 as dirty because
the flash driver returned retlen zero
[42949387.610000] Write of 44 bytes at 0x00cf91d0 failed. returned -30,
retlen 0
[42949387.620000] Not marking the space at 0x00cf91d0 as dirty because
the flash driver returned retlen zero
rm: unable to remove `blub': Read-only file system
----------------

So something is still wrong. At runtime the filesystem seems to be OK
but after a reboot it seems to be defect. Only way to recover is to
reflash the rootfs.

I am quite desperate right now.
For the new approach I took the Mainstone MTD mapping driver and
modified it for the single two-chip configuration. But I did not change
anything beyond that.

Cheers
  nils faerber

-- 
kernel concepts GbR      Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          Mob: +49-176-21024535
--

             reply	other threads:[~2006-09-08 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 15:27 Nils Faerber [this message]
2006-09-09 11:16 ` Again 2.6.18-RC6 XScale P30 issues Justin Clacherty
2006-09-09 12:16   ` Nils Faerber
2006-09-09 14:10     ` Josh Boyer
2006-09-09 22:00     ` Justin Clacherty

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=45018BE6.5040102@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --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