From: "William A. Gatliff" <bgat@billgatliff.com>
To: linux-mtd@lists.infradead.org
Subject: mtdblock_ro and ext2 yields panic: block not locked
Date: Wed, 23 Oct 2002 10:49:57 -0500 [thread overview]
Message-ID: <20021023104957.G8758@saturn.billgatliff.com> (raw)
Guys:
I'm running linux-2.4.18-mips on an Au1500 board with an AMD AM29LV642
flash. I'm using the readonly block driver and a partitioned flash.
The mtdblock_ro.c file has "mtdblock_ro.c,v 1.9" at the top.
I've been tinkering with mounting ext2 and romfs root filesystems at
boot from my mtdblock0 partition. I seem to be able to mount romfs
fine, but when I use ext2, I get this:
...
ttyS03 at 0xb1400000 (irq = 3) is a 16550
mtdblock_open
ok
mtdblock_open
ok
mtdblock_release
ok
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 192k freed
Kernel panic: mtdblock: block not locked
The panic comes via the INIT_REQUEST macro in mtdblock_request, but
only after half a dozen requests or so. The requests appear to be
associated with the execve at the end of the kernel boot process.
I also get this with yesterday's CVS.
Ideas? I don't think this is an MTD problem per se, but I'm stumped
nonetheless.
Thanks!
b.g.
--
Bill Gatliff
I'm an embedded GNU developer first, GNU instructor second.
See http://billgatliff.com for details.
next reply other threads:[~2002-10-23 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 15:49 William A. Gatliff [this message]
[not found] ` <5.1.0.14.2.20021023101127.03ed2df0@pop.prodigy.net>
[not found] ` <20021023121843.A9783@saturn.billgatliff.com>
2002-10-23 17:22 ` mtdblock_ro and ext2 yields panic: block not locked Eugene Surovegin
2002-10-23 18:13 ` William A. Gatliff
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 17:15 Eugene Surovegin
2002-10-27 19:53 ` Jörn Engel
2002-10-29 14:28 ` 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=20021023104957.G8758@saturn.billgatliff.com \
--to=bgat@billgatliff.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