All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Freeman <free0076@flinders.edu.au>
To: Junping Zhang <JZhang@erinc.com>
Cc: Linux MTD List <linux-mtd@lists.infradead.org>
Subject: Re: seeking help on JFFS2
Date: 06 Nov 2002 03:57:38 +0000	[thread overview]
Message-ID: <1036555060.2440.11.camel@dirac.home> (raw)
In-Reply-To: <F4608F665DF5D311B231009027B70F70012ED670@MAIL>

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 <do_read_onechip+b8/4ec>   <=====
>     Trace; c0011480 <printk+15c/1b4>
>     Trace; c00df668 <cfi_intelext_read+b4/100>
>     Trace; c00e3be8 <part_read+68/a0>
>     Trace; c00a2ba0 <jffs2_mark_node_obsolete+468/88c>
>     Trace; c00a1fe0 <jffs2_do_reserve_space+264/55c>
>     Trace; c00a1b90 <jffs2_reserve_space+1b8/2d8>
>     Trace; c009df2c <jffs2_mkdir+54/454>
>     Trace; c0041d84 <vfs_mkdir+10c/130>
>     Trace; c0041e8c <sys_mkdir+e4/108>
>     Trace; c0003ddc <ret_from_syscall_1+0/b4>
>     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/
> 

  parent reply	other threads:[~2002-11-05 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 13:40 seeking help on JFFS2 Junping Zhang
2002-11-05 16:41 ` Jörn Engel
2002-11-06  3:57 ` Darren Freeman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 17:17 Jeffrey Lim
2002-11-05 19:32 ` Jörn Engel
2002-11-05 17:39 Junping Zhang
2002-11-05 19:31 ` Jörn Engel
2002-11-05 19:56 Junping Zhang
2002-11-05 21:08 ` Jörn Engel
2002-11-06 13:13 Junping Zhang
2002-11-06 16:09 Junping Zhang
2002-11-06 16:14 ` David Woodhouse
2002-11-07  8:28   ` Joakim Tjernlund
2002-11-07  8:49     ` David Woodhouse
2002-11-06 18:26 Junping Zhang

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=1036555060.2440.11.camel@dirac.home \
    --to=free0076@flinders.edu.au \
    --cc=JZhang@erinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.