public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* Re: mtdblock_ro and ext2 yields panic: block not locked
@ 2002-10-23 17:15 Eugene Surovegin
  2002-10-27 19:53 ` Jörn Engel
  0 siblings, 1 reply; 6+ messages in thread
From: Eugene Surovegin @ 2002-10-23 17:15 UTC (permalink / raw)
  To: linux-mtd

At 08:49 AM 10/23/2002, you wrote:

>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.


mtdblock_ro is buggy. It uses nr_sectors instead current_nr_sectors while 
processing request.

I sent a patch to MTD maintainer several weeks ago - nothing happened.

Thanks,


  Eugene Surovegin <mailto:ebs@innocent.com>

^ permalink raw reply	[flat|nested] 6+ messages in thread
* mtdblock_ro and ext2 yields panic: block not locked
@ 2002-10-23 15:49 William A. Gatliff
       [not found] ` <5.1.0.14.2.20021023101127.03ed2df0@pop.prodigy.net>
  0 siblings, 1 reply; 6+ messages in thread
From: William A. Gatliff @ 2002-10-23 15:49 UTC (permalink / raw)
  To: linux-mtd

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-10-30 12:03 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-23 17:15 mtdblock_ro and ext2 yields panic: block not locked Eugene Surovegin
2002-10-27 19:53 ` Jörn Engel
2002-10-29 14:28   ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23 15:49 William A. Gatliff
     [not found] ` <5.1.0.14.2.20021023101127.03ed2df0@pop.prodigy.net>
     [not found]   ` <20021023121843.A9783@saturn.billgatliff.com>
2002-10-23 17:22     ` Eugene Surovegin
2002-10-23 18:13       ` William A. Gatliff

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox