All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weston <jweston@securenet.com.au>
To: linux-mtd@lists.infradead.org
Subject: Re: Booting from /dev/mtdblock/0
Date: Mon, 29 Apr 2002 11:15:47 +1000	[thread overview]
Message-ID: <3CCC9EC3.C233A4C2@securenet.com.au> (raw)
In-Reply-To: 3CCC9A64.87F68E3@securenet.com.au

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

Hi again,

Pardon my last message. Having looked up the mail archive found the solution
there. Seems to be a problem calling the invalidate_device function call in
the mtdblock.c code.

Seems like I had better look harder next time.

Thanks anyway.

John Weston


John Weston wrote:

> G'day,
>
> Have not got to the bottom of this yet, but having the same problem. We had
> a development board which worked fine using kernel version 2.4.3 but since
> updating to 2.4.18 we are now seeing the same problem.
>
> Does anyone know of any required patches for this?
>
> Thanks
>
> John Weston
>
> Mutada Shah wrote:
>
> > Hi,
> >
> > I'm trying to boot from /dev/mtdblock/0 (root=/dev/mtdblock/0 in cmdline
> > options)
> >
> > When I boot from nfs, I can mount /dev/mtdblock/0 no problem from
> > command line & unmount etc.
> >
> > But if I pass it as the root= option, while booting it gets stuck.
> >
> > With mtd debug level to 3 I see that it tries mtdblock_open twice...
> > which it shouldnt..
> >
> > "mtdblock_open
> > ok
> > mtdblock_open
> > mtdblock_release"
> >
> > Then it hangs here for a long time.
> > What could be the cause?
> >
> > Murtada
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 1122 bytes --]

  reply	other threads:[~2002-04-29  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 20:11 Booting from /dev/mtdblock/0 Murtada Shah
2002-04-29  0:57 ` John Weston
2002-04-29  1:15   ` John Weston [this message]
2002-04-29  2:28   ` Jim Thompson

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=3CCC9EC3.C233A4C2@securenet.com.au \
    --to=jweston@securenet.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.