From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.airnet.com.au ([202.174.32.5] ident=qmailr) by pentafluge.infradead.org with smtp (Exim 3.22 #1 (Red Hat Linux)) id 18970M-0000Tw-00 for ; Tue, 05 Nov 2002 16:56:43 +0000 Subject: Re: seeking help on JFFS2 From: Darren Freeman To: Junping Zhang Cc: Linux MTD List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: 06 Nov 2002 03:57:38 +0000 Message-Id: <1036555060.2440.11.camel@dirac.home> Mime-Version: 1.0 Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: Hi Junping, I worked for Motorola a year ago and wrote drivers for the MPC8260 using the MPC8260ADS board with TCOM board attached. We used vxWorks in that project so I can't help you here. But I would be interested to hear how things are going anyway =) Now I'm working with the Altera EPXA10 dev board, running ARM-Linux (of course!). I mainly worked on fast ethernet and ATM. Have fun, Darren Freeman On Tue, 2002-11-05 at 13:40, Junping Zhang wrote: > Hi, > > I am new to MTD/JFFS2. Thanks to Christian Gagnaraud's patch, I got MTD > working, but > everytime I use JFFS2 on top of it, I get a kernel oops: "Oops: kernel > access of > bad area, sig: 11" > > Here is my setup: > board: MPC8260ADS > bootloader: ppcboot-1.1.6 > kernel: 2.4.18 > MTD/JFFS2: mtd-snapshot-20021022.tar.bz2 > RAM: 64M > flash: 8M > root disk: ramdisk of 16M > host: x86 with cross-compiler > > Here is the message of MTD from kernel startup: > Found: Intel 28F016S5 > MPC8260ADS Bank 0: Found 4 x8 devices at 0x0 in 32-bit mode > Using word write method > MPC8260ADS flash bank 0: Using static image partition definition > Creating 4 MTD partitions on "MPC8260ADS Bank 0": > 0x00000000-0x00700000 : "jffs2-root" > mtd: Giving out device 1 to jffs2-root > 0x00700000-0x00740000 : "ppcboot" > mtd: Giving out device 2 to ppcboot > 0x00740000-0x00780000 : "environment" > mtd: Giving out device 3 to environment > 0x00780000-0x00800000 : "spare" > mtd: Giving out device 4 to spare > > Here is how I made oops happen: > eraseall /dev/mtd1 > mount -t jffs2 /dev/mtdblock1 /mnt/flash > cp -R sbin /mnt/flash > > Here is the oops message through ksymoops: > >>NIP; c00e1938 <===== > Trace; c0011480 > Trace; c00df668 > Trace; c00e3be8 > Trace; c00a2ba0 > Trace; c00a1fe0 > Trace; c00a1b90 > Trace; c009df2c > Trace; c0041d84 > Trace; c0041e8c > Trace; c0003ddc > Trace; 1002f4f0 Before first symbol > Trace; 100056c4 Before first symbol > Trace; 1002f2c8 Before first symbol > Trace; 1002ef18 Before first symbol > Trace; 0fecef70 Before first symbol > Trace; 00000000 Before first symbol > > Here are what I have tried: > (a) I tried plain JFFS on MTD, and it works. The steps I use: > > eraseall /dev/mtd1 > mount -t jffs /dev/mtdblock1 /mnt/flash > > I can then copy/edit/delete from it, and diff shows that > the data is consistant. > > So I think MTD layer is fine and the configuration on MTD > part (.config) is fine. > > (b) I tried mkfs.jffs2 on both target and my x86 host (with > big-endian option) > > mkfs.jffs2 -dipc -e0x40000 -p0x700000 -b -o /opt/ipc.jffs2 > > I then cp it on a mtd device with: > eraseall /dev/mtd1 > cp /mnt/nfs/ipc.jffs2 /dev/mtd1 > > the "cp" goes fine, but when I tried to mount & use the > JFFS2 system, within one or two commands, it will give me > the oops with the same reason "kernel access of bad area" > > But if I now boot into ppcboot(with JFFS2 capability compiled > in), ppcboot can recognize my JFFS2 files just fine, which > lead me to believe the linux JFFS2 subsystem is the problem. > > (c) I then tried disabling the compression for JFFS2 by forcing > return of JFFS2_COMPR_NONE from jffs2_compress() to see if > zlib is a problem. It doesn't seem to have any effect. > > Any ideas? I have been reading the mailing list archive and could > not find the answer to this. > > Thanks a lot > > > - Junping > > > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/ >