From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Justin Clacherty <justin@redfish-group.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Again 2.6.18-RC6 XScale P30 issues
Date: Sat, 09 Sep 2006 14:16:02 +0200 [thread overview]
Message-ID: <4502B082.1090401@kernelconcepts.de> (raw)
In-Reply-To: <4502A2AA.30701@redfish-group.com>
Justin Clacherty schrieb:
> Nils Faerber wrote:
>> 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.
> Is the bootup process writing to flash before you unlock it? syslogd
> might be a culprit...
Well, yes, there are some scripts that touch the fs, but that is IMHO
not the issue here. If it would be I would get the other "unable to
write to locked sector" error.
Instead the fs gets permanently corrupted, i.e. data is written and the
written data is wrong.
Last night I found that the JFFS2 write cache is configured. I will
disable that now and see if that helps - I have the impression that the
fs may contain half-baked stuff after a write. On the other hand, the
JFFS2 write cache is not marked as an experimental feature so I thought
I should be safe...
Well, that like poking with a long pole in the mist, I have to admit.
Very nasty to debug...
If I find something new I'll let you know ;)
But many thanks for your (all of you) help so far!
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
--
next prev parent reply other threads:[~2006-09-09 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 15:27 Again 2.6.18-RC6 XScale P30 issues Nils Faerber
2006-09-09 11:16 ` Justin Clacherty
2006-09-09 12:16 ` Nils Faerber [this message]
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=4502B082.1090401@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=justin@redfish-group.com \
--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