public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Vrabel <dvrabel@arcom.co.uk>
To: mtd@infradead.org, jffs-dev@axis.com
Subject: JFFS oopses on mount
Date: Fri, 18 Aug 2000 09:42:25 +0100	[thread overview]
Message-ID: <399CF6F1.4622CF44@arcom.co.uk> (raw)

Hi,

JFFS oopses during mounting.  Are the latest CVS sources likely to fix
this problem (last checked out Aug 16th)? If not how can I go about
finding out what the problem is?  Unfortunatly I had to disable
debugging because the problem didn't occur with it enabled (sending
masses of debugging information via a serial link reduces greatly the
number of test iterations).  I do have more images of the flash than you
can shake a stick at though.

Possibly a message of interest
jffs_garbage_collect_now(): free_size == 0. This is BAD.

David Vrabel



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2000-08-18  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-18  8:42 David Vrabel [this message]
2000-08-18  9:09 ` JFFS oopses on mount David Woodhouse
2000-08-22 11:33   ` David Vrabel
2000-08-22 12:24     ` David Woodhouse
2000-08-22 13:16     ` 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=399CF6F1.4622CF44@arcom.co.uk \
    --to=dvrabel@arcom.co.uk \
    --cc=jffs-dev@axis.com \
    --cc=mtd@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