From: Orjan Friberg <of@flatfrog.com>
To: <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 oops when writing to two partitions simultaneously
Date: Tue, 24 Jan 2012 18:15:53 +0100 [thread overview]
Message-ID: <4F1EE749.6020801@flatfrog.com> (raw)
In-Reply-To: <4F1E802D.5010402@flatfrog.com>
A couple of new observations in trying to box this in:
Early revisions (A2) of the BeagleBoard xM has both NAND and SD/MMC. If
I boot the system (Linux + rootfs) off the SD card (ext3 formatted) and
create two JFFS2 partitions in the NAND flash, I cannot repeat the
problem. That system uses a pretty recent kernel, 3.0.17.
As a sanity check, I ran the 2.6.32 configuration on the xM board to
verify that it wasn't a problem isolated to our own board. Sure enough,
it happens there too.
I'm going to check whether the oops is dependent on Linux + rootfs being
on a JFFS2 partition or if it's just a matter of kernel version.
On a side note, is there a more easily searchable archive than
http://lists.infradead.org/pipermail/linux-mtd/?
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2012-01-24 17:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:55 JFFS2 oops when writing to two partitions simultaneously Orjan Friberg
2012-01-24 17:15 ` Orjan Friberg [this message]
2012-01-24 19:02 ` Orjan Friberg
2012-01-25 19:53 ` Orjan Friberg
2012-01-25 21:01 ` Orjan Friberg
2012-01-26 8:19 ` Joakim Tjernlund
2012-01-26 9:02 ` Orjan Friberg
2012-01-26 9:53 ` Joakim Tjernlund
2012-01-26 9:02 ` Orjan Friberg
2012-01-26 11:53 ` Joakim Tjernlund
2012-01-26 12:51 ` Orjan Friberg
2012-01-26 13:16 ` Joakim Tjernlund
2012-01-26 14:07 ` Orjan Friberg
2012-01-26 14:23 ` Joakim Tjernlund
2012-01-26 14:53 ` Orjan Friberg
2012-01-26 15:17 ` Joakim Tjernlund
2012-01-26 15:25 ` Orjan Friberg
2012-01-26 16:05 ` Orjan Friberg
2012-01-26 16:17 ` Joakim Tjernlund
2012-01-26 14:52 ` Joakim Tjernlund
2012-01-26 15:09 ` Joakim Tjernlund
2012-01-26 15:18 ` Orjan Friberg
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=4F1EE749.6020801@flatfrog.com \
--to=of@flatfrog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox