From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: XIP issues introduced between 2.6.12 and 2.6.13
Date: Thu, 13 Oct 2005 11:43:27 +0200 [thread overview]
Message-ID: <8764s169c0.wl%kletschke@synertronixx.de> (raw)
Well, I want to be more precise:
If I build in jffs2 into Kernel, the Kernel freezes immediatly after
starting sometimes. In seldom times it boots to prompt (with / on
nfs). If it boots to prompt, I can mount mtdblock partitions rw and ls
them. If I touch a file then on it, it breaks 100%.
With jffs2 as module, nor Problem.
How this could correlate with
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-October/031686.html
I have really no clue!
Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next reply other threads:[~2005-10-13 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 9:43 Konstantin Kletschke [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 16:30 XIP issues introduced between 2.6.12 and 2.6.13 Konstantin Kletschke
2005-10-12 16:52 ` Nicolas Pitre
2005-10-12 17:06 ` Konstantin Kletschke
2005-10-12 17:47 ` Nicolas Pitre
2005-10-12 20:11 ` Konstantin Kletschke
2005-10-12 20:44 ` Konstantin Kletschke
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=8764s169c0.wl%kletschke@synertronixx.de \
--to=lists@ku-gbr.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