From: David Woodhouse <dwmw2@infradead.org>
To: karim@opersys.com
Cc: Linux-MTD <linux-mtd@lists.infradead.org>
Subject: Re: Problems with NFTL in 2.4.22
Date: Wed, 12 Nov 2003 09:57:56 +0000 [thread overview]
Message-ID: <1068631075.10450.3.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <3FB17F30.7090006@opersys.com>
On Tue, 2003-11-11 at 19:30 -0500, Karim Yaghmour wrote:
> 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.
Did you get a backtrace of the offending process(es) with SysRq-T?
I suspected it might be because we're calling cond_resched() when one of
our callers has already set current->state to TASK_UNINTERRUPTIBLE. But
I've had a report that it still happens in the current CVS code, in
which that definitely shouldn't be the case. Can you confirm that?
--
dwmw2
prev parent reply other threads:[~2003-11-12 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 0:30 Problems with NFTL in 2.4.22 Karim Yaghmour
2003-11-12 9:57 ` David Woodhouse [this message]
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=1068631075.10450.3.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=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