From: Oleg Nesterov <oleg@tv-sign.ru>
To: Zilvinas Valinskas <zilvinas@wilibox.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel NFS lockd freezes notebook on shutdown (Linux 2.6.22-rc1 + CFS v12)
Date: Thu, 17 May 2007 22:45:56 +0400 [thread overview]
Message-ID: <20070517184556.GA81@tv-sign.ru> (raw)
In-Reply-To: <1179390065.4760.5.camel@zv.wilibox.com>
Hello Zilvinas,
On 05/17, Zilvinas Valinskas wrote:
>
> Patch seems to help and it seems kernel doesn't free anymore. I've
> booted new kernel and did :
OK, thank you very much. So, we have some other problems, and I _think_
that workqueue.c is not the source of them.
However, I can't understand why cleanup_workqueue_thread() hangs anyway.
It shouldn't. Looks like rpciod/1 was preempted, and can't get CPU. According
to kernel-nfs-freeze.log it is TASK_RUNNING. Strange.
It is very sad, because this code was supposed to be cleanuped anyway,
but if it is really buggy, it would be great to know why.
Perhaps, we can understand the problem with your help. Could you please
revert the patch I sent, and send me (privately) the output of
objdump -d kernel/workqueue.o
? I doubt very much I'll see something interesting, but who knows...
Thanks!
Oleg.
next prev parent reply other threads:[~2007-05-17 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 18:00 Zilvinas Valinskas
2007-05-16 19:15 ` Andrew Morton
2007-05-16 22:55 ` Oleg Nesterov
2007-05-17 6:17 ` Zilvinas Valinskas
2007-05-17 8:21 ` Zilvinas Valinskas
2007-05-17 9:00 ` Zilvinas Valinskas
2007-05-17 18:45 ` Oleg Nesterov [this message]
2007-05-18 10:47 ` Zilvinas Valinskas
2007-05-18 20:28 ` Oleg Nesterov
2007-05-20 10:37 ` zilvinas
2007-05-20 17:01 ` J. Bruce Fields
2007-05-20 19:21 ` Oleg Nesterov
2007-05-18 12:17 ` Zilvinas Valinskas
2007-05-18 15:34 ` Andrew Morton
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=20070517184556.GA81@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zilvinas@wilibox.com \
/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
Powered by JetHome