From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [81.3.11.18] (helo=mail.ku-gbr.de) by canuck.infradead.org with esmtps (Exim 4.54 #1 (Red Hat Linux)) id 1EPjV5-0001R9-5K for linux-mtd@lists.infradead.org; Wed, 12 Oct 2005 12:30:57 -0400 Received: from p5482721b.dip.t-dialin.net ([84.130.114.27]:56656 helo=synertronixx3) by mail.ku-gbr.de with esmtpa (Exim 4.50 #1 (Debian)) id 1EPjXc-0008Dv-U6 for ; Wed, 12 Oct 2005 18:33:21 +0200 Received: from localhost ([127.0.0.1] helo=synertronixx3.doom ident=konsti) by synertronixx3 with esmtp (Exim 3.36 #1 (Debian)) id 1EPjUv-0006cH-00 for ; Wed, 12 Oct 2005 18:30:33 +0200 Date: Wed, 12 Oct 2005 18:30:33 +0200 Message-ID: <87slv6vgt2.wl%kletschke@synertronixx.de> From: Konstantin Kletschke To: linux-mtd@lists.infradead.org MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: XIP issues introduced between 2.6.12 and 2.6.13 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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