From: "??" <kevin@gv.com.tw>
To: <brendan.simon@ctam.com.au>, "linux-mtd" <linux-mtd@lists.infradead.org>
Subject: Re: kernel hangs on DOC2000 root filesystem
Date: Wed, 7 Aug 2002 09:35:08 +0800 [thread overview]
Message-ID: <003001c23db2$a9fe8d20$1b0448c0@gv.com.tw> (raw)
In-Reply-To: 3D505C85.80705@ctam.com.au
(2.4.18)mount_root():blkdev_put():bdev->bd_op->release():invalidate_device()
: invalidate_inodes(sb)
probably caused by doing invalidate_xxx() inside mount_root()?
(some other driver also hang when doing release() operation inside
mount_root)
----- Original Message -----
From: "Brendan J Simon" <brendan.simon@ctam.com.au>
To: "linux-mtd" <linux-mtd@lists.infradead.org>
Sent: Wednesday, August 07, 2002 7:32 AM
Subject: Re: kernel hangs on DOC2000 root filesystem
>
>
> David Woodhouse wrote:
>
> >brendan.simon@ctam.com.au said:
> >
> >> Any ideas why the kernel just hangs ?
> >>
> >>>>>>>>>>BJS: nftl_release(): invalidate_device()
> >>>>>>>>>>
>
> Is this because get_super() fails ???
>
> I've done an fsck.ext2 and it passed with no problems. This should mean
> that the super blocks are OK, should it ???
>
> I formatted the DOC with nftl_format if that makes any difference.
> I also used the latest fdisk from util-linux for format the drive with
> an MSDOS partition table and one ext2 partition.
>
> Thanks for any help or advice.
> Brendan Simon.
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-08-07 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 8:33 kernel hangs on DOC2000 root filesystem Brendan J Simon
2002-08-06 8:57 ` David Woodhouse
2002-08-06 23:32 ` Brendan J Simon
2002-08-07 1:35 ` ?? [this message]
2002-08-06 23:52 ` Brendan J Simon
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='003001c23db2$a9fe8d20$1b0448c0@gv.com.tw' \
--to=kevin@gv.com.tw \
--cc=brendan.simon@ctam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox