From: Ales Makarov <ales.makarov@wolfhill.cz>
To: linux-mtd@lists.infradead.org
Subject: JFFS2 without compression
Date: Thu, 03 Oct 2002 14:59:24 +0200 [thread overview]
Message-ID: <3D9C3F2C.1040901@wolfhill.cz> (raw)
Hi,
we use MTD & JFFS2 on our board (based on Motorola DragonBall VZ) running
uClinux with AMD/Fujitsu 29LVxxx flashes.
It seems to work most of the time, but the kernel sometimes crashes and produces
ooops messages. Right now I have some file that crashes kernel every time I try
to write it to JFFS2 filesystem. Now I suspect there is a problem with the
compression...
Example:
I have this file named "outputs" and is 83 bytes long.
# cat outputs
0;RELAY 1
0;RELAY 2 (movement sensor)
0;RELAY 3
0;RELAY 4 (not connected)
0;BUZZER
#
When I try to edit the file (I change the 3rd line to "0;COOLER") and save the
file, the kernel crashes with:
*** Exception 981 *** FORMAT=3
Current process id is 65
BAD KERNEL TRAP: 00000000
PC: [<00a7b04f>]
SR: 3f55 SP: 00a79cb2 a2: 000e8d58
d0: 00000000 d1: 00000001 d2: 00000000 d3: 00000000
d4: 00152d1a d5: 00000003 a0: 00a79da0 a1: 00000003
Process vi (pid: 65, stackpage=00a79000)
Frame format=3 eff addr=20000006
Stack from 00a79cea:
b2b00000 00000000 00030000 00000020 00000000 00000018 9dfc00df f46000df
f46000a7 9df00000 000000a7 9da40000 00000000 00000000 000000a7 80000000
00000006 d7a400df f3600000 00000018 9dfc0000 000300a7 9da000a7 b04f0000
00000018 9dfc0000 00010000 00440000 00020000 00ff00a7 9dfc0005 a13e00df
f4600000 00000018 9dfc0000 000300a7 9da000a7 b04f3de6 73840000 0047ffff
ffff0000 000300d8 54c600c5 1d4000c3 310000c
Here is this file after the reboot:
# cat outputs
0;RELAY 1
0;RELAY 2 (movement sensor)
0;COOLER
0;RELAY 4 (not connected)
0;BUZZ#
I'd like to try the JFFS2 without compression. Where can I disable the zlib
compression?
Thanks.
Ales Makarov
next reply other threads:[~2002-10-03 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 12:59 Ales Makarov [this message]
2002-10-03 13:03 ` JFFS2 without compression David Woodhouse
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=3D9C3F2C.1040901@wolfhill.cz \
--to=ales.makarov@wolfhill.cz \
--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