From: "Michael Gibson" <m.gibson@esesixtech.com>
To: <mtd@infradead.org>
Subject: Kernel panic DiskOnChip /Newbie question
Date: Mon, 5 Mar 2001 13:03:59 +0100 [thread overview]
Message-ID: <002101c0a56c$5caf3090$3201a8c0@thinstuff.com> (raw)
Is there somebody who could help me with following jffs problem?
kernel 2.4.2, mtd cvs snapshot of 02nd March 2001(same problem with original
mtd modules from kernel 2.4.2), DOC2000 8MB with firmware 1.21
DOC2000 is detected OK
when I try to do "mount -t jffs /dev/mtdblock0 /test" after "erase
/dev/mtd0" (as described in the mtd/jffs HOWTO from the CVS snapshot)
I get a Kernel panic:
" Didn´t read all bytes in flash_safe_read(). Returned 0 "
but NFTL workes fine, I can do nftl_format - create a partition - put a
minix fs on it and mount it.
Also writing to the nftl partition works fine.
What am I doing wrong?
Best regards
Michael Gibson
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2001-03-05 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 12:03 Michael Gibson [this message]
2001-03-05 12:39 ` Kernel panic DiskOnChip /Newbie question 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='002101c0a56c$5caf3090$3201a8c0@thinstuff.com' \
--to=m.gibson@esesixtech.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