From: Karim Yaghmour <karim@opersys.com>
To: Linux-MTD <linux-mtd@lists.infradead.org>
Subject: Problems with NFTL in 2.4.22
Date: Tue, 11 Nov 2003 19:30:40 -0500 [thread overview]
Message-ID: <3FB17F30.7090006@opersys.com> (raw)
I haven't seen anything in the archives about this, so here goes:
I've had quite a few problems trying to interface with an 8MB DOC with
2.4.22. The system would simply freeze when I tried doing things like
mount, unmount, mke2fs, cat fs image to device, etc. No oops no nothing,
just the tools would not return to the command line and I'd have to
hard-reset the system. I tried a few variations in the commands to try
to get the same results, but nothing really got it working. I eventually
gave up and tried 2.4.21 instead, and then everything I was trying to
do before just worked fine ...
I cannot say exactly what's the problem, and I don't have the time
to track it down, but I can say that 2.4.22 has a problem with handling
at least the 8MB DOC.
HTH,
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 514-812-4145
next reply other threads:[~2003-11-12 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 0:30 Karim Yaghmour [this message]
2003-11-12 9:57 ` Problems with NFTL in 2.4.22 David Woodhouse
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=3FB17F30.7090006@opersys.com \
--to=karim@opersys.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