* root=/dev/mtdblock doesn't work with kernel 2.4.18
@ 2002-03-19 9:04 Stephan Linke
2002-03-19 10:48 ` David Woodhouse
0 siblings, 1 reply; 3+ messages in thread
From: Stephan Linke @ 2002-03-19 9:04 UTC (permalink / raw)
To: linux-mtd
Hi!
After changing from 2.4.8-pre4 to a 2.4.18 kernel I can't mount the flash as
root device any more. I'm using the "root=" boot argument to do so.
The filesystem (cramfs) is alredy detected in mount_root() (super.c) when
mount_root calls blkdev_put(bdev, BDEV_FS); Which for some reasons has to
call the release function of the device which results in mtdblock_release()
being called. The hole thing stops when invalidate_device() calls
fsync_dev(dev). Where we'll shurely get back to the MTD driver (some how).
Calling blk_dev_get() and blk_dev_put() in mount_root() is a difference
between both kernel versions. But removing that change simply leades to
another problem...
Everything works fine when running with NFS as rootfs mounting the flash
with /etc/fstab. So it looks like this is some kind of race condition.
Maybe this is an issue to the FS people. But you should have experience with
using the rootfs that way.
Thanks, Stephan
#--
STEPHAN LINKE (dipl. inform); software engineer
epygi labs de gmbh; herrenstraße 23, 3. og, D-76133 karlsruhe
http://www.epygi.de; mailto:stephan.linke@epygi.de
phone 0721-20596-30; fax 0721-20596-59
----------------------------------------
Motto: Wenn es defekt ist, dann isses kaputt!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: root=/dev/mtdblock doesn't work with kernel 2.4.18
2002-03-19 9:04 root=/dev/mtdblock doesn't work with kernel 2.4.18 Stephan Linke
@ 2002-03-19 10:48 ` David Woodhouse
2002-03-20 10:18 ` Stephan Linke
0 siblings, 1 reply; 3+ messages in thread
From: David Woodhouse @ 2002-03-19 10:48 UTC (permalink / raw)
To: Stephan Linke; +Cc: linux-mtd
On Tue, 19 Mar 2002, Stephan Linke wrote:
> After changing from 2.4.8-pre4 to a 2.4.18 kernel I can't mount the flash as
> root device any more. I'm using the "root=" boot argument to do so.
> The filesystem (cramfs) is alredy detected in mount_root() (super.c) when
> mount_root calls blkdev_put(bdev, BDEV_FS); Which for some reasons has to
> call the release function of the device which results in mtdblock_release()
> being called. The hole thing stops when invalidate_device() calls
> fsync_dev(dev).
Remove just the call to invalidate_device() in mtdblock_release()
--
dwmw2
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: root=/dev/mtdblock doesn't work with kernel 2.4.18
2002-03-19 10:48 ` David Woodhouse
@ 2002-03-20 10:18 ` Stephan Linke
0 siblings, 0 replies; 3+ messages in thread
From: Stephan Linke @ 2002-03-20 10:18 UTC (permalink / raw)
To: linux-mtd
Thank's David! Now it works.
>
> > After changing from 2.4.8-pre4 to a 2.4.18 kernel I can't mount the
flash as
> > root device any more. I'm using the "root=" boot argument to do so.
> > The filesystem (cramfs) is alredy detected in mount_root() (super.c)
when
> > mount_root calls blkdev_put(bdev, BDEV_FS); Which for some reasons has
to
> > call the release function of the device which results in
mtdblock_release()
> > being called. The hole thing stops when invalidate_device() calls
> > fsync_dev(dev).
>
> Remove just the call to invalidate_device() in mtdblock_release()
>
> --
> dwmw2
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-03-20 10:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-19 9:04 root=/dev/mtdblock doesn't work with kernel 2.4.18 Stephan Linke
2002-03-19 10:48 ` David Woodhouse
2002-03-20 10:18 ` Stephan Linke
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox