public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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: Wed, 12 Oct 2005 18:30:33 +0200	[thread overview]
Message-ID: <87slv6vgt2.wl%kletschke@synertronixx.de> (raw)


Well, as two other guys also I experience Problems getting XIP
functional on 2.6.13.
In order to debug this I set up a nfs root to play from there.

The funny thing I relize now, is the following:

With jffs2 build into the kernel image the system freezes reproducable
when touching a file.

When build and load as a module I can do anything with the mounted
jffs2 partition, everything works fine.

Now I am puzzled. The not being a module or being a module is the only
difference and I testet both situations a dozen of times.
Another sidenote: I once had an XIP Kernel today running, root over
nfs and used /dev/mtdblock4 as a swap device with no problems. How
comes that :) ?

Regards, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

             reply	other threads:[~2005-10-12 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 16:30 Konstantin Kletschke [this message]
2005-10-12 16:52 ` XIP issues introduced between 2.6.12 and 2.6.13 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
  -- strict thread matches above, loose matches on Subject: below --
2005-10-13  9:43 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=87slv6vgt2.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