From: "Mark Richards" <markr@massmicro.com>
To: <linux-mtd@lists.infradead.org>
Subject: RE: MTD - DOC 2000 freezes on umount
Date: Tue, 20 Jan 2004 08:51:26 -0500 [thread overview]
Message-ID: <010301c3df5c$7fdb9c70$6e01a8c0@solarwave> (raw)
In-Reply-To: <009a01c3defc$5a0b9820$6e01a8c0@solarwave>
Update... I have also discovered that sometimes the first umount works, but
a subsequent umount (preceded of course by a mount) also freezes. In
addition, I also get an occasional freeze-up when issuing the mount command.
If I don't umount at the commandline, but instead call a reboot, the file
system umounts fine - question: since I have mounted the MTD manually, is it
considered part of the file system to be umounted when the machine shuts
down?
This is more a nuisance, as are the occasional freeze-ups I experience just
accessing the DOC once mounted, but since it's a departure from the previous
good performance, perhaps it's worth looking into?
Mark Richards
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org [mailto:linux-mtd-
> bounces@lists.infradead.org] On Behalf Of Mark Richards
> Sent: Monday, January 19, 2004 21:23
> To: linux-mtd@lists.infradead.org
> Subject: MTD - DOC 2000 freezes on umount
>
> I've been through several good learning experiences getting my development
> system set up to work with a DOC 2000 for an embedded project. I've
> finally
> settled on a RedHat 7.2 distribution and the 2.4.24 kernel. All worked
> well
> with the MTD drivers in several other setups: RedHat 9, Mandrake 9.2, but
> for reasons I can't yet fathom, the MTD drivers seem a bit unstable in
> this
> particular kernel.
>
> Most frequently when I perform a umount /mnt/doc (doc being the mount
> point)
> the shell session freezes (the umount command does not return a prompt).
>
> If I then perform a sfdisk -l /dev/nftla the command again goes off into
> space with no return data.
>
> Then the shut down hangs up.
>
> I tried in one kernel build to apply the latest sources to my source tree
> using the instructions (and the shell script) but this caused a compile
> failure.
>
> May I have some suggestions as to how I can further diagnose this problem,
> or what I can do to provide information that will help?
>
> Many thanks,
>
> Mark
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2004-01-20 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 2:23 MTD - DOC 2000 freezes on umount Mark Richards
2004-01-20 13:51 ` Mark Richards [this message]
2004-01-20 14:07 ` David Woodhouse
2004-01-20 15:11 ` Mark Richards
2004-01-20 18:04 ` Mark Richards
2004-01-20 18:10 ` David Woodhouse
2004-01-20 18:32 ` Mark Richards
2004-01-21 5:51 ` Mark Richards
2004-01-20 18:20 ` Matthew S. McClintock
2004-01-20 18:22 ` David Woodhouse
2004-01-20 18:28 ` Matthew S. McClintock
2004-01-23 3:35 ` Mark Richards
[not found] <E1Aj0eB-0006rS-Bn@pentafluge.infradead.org>
2004-01-20 20:01 ` Bob Beers
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='010301c3df5c$7fdb9c70$6e01a8c0@solarwave' \
--to=markr@massmicro.com \
--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