public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: <linux-mtd@lists.infradead.org>
Subject: root=/dev/mtdblock doesn't work with kernel 2.4.18
Date: Tue, 19 Mar 2002 10:04:30 +0100	[thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJMEKPCDAA.Stephan.Linke@epygi.de> (raw)

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!“

             reply	other threads:[~2002-03-19  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  9:04 Stephan Linke [this message]
2002-03-19 10:48 ` root=/dev/mtdblock doesn't work with kernel 2.4.18 David Woodhouse
2002-03-20 10:18   ` Stephan Linke

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=FCEAKDJJAPHPLJFINDAJMEKPCDAA.Stephan.Linke@epygi.de \
    --to=stephan.linke@epygi.de \
    --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