mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zilvinas Valinskas <zilvinas@wilibox.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
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: Fri, 18 May 2007 13:47:10 +0300	[thread overview]
Message-ID: <1179485230.3800.20.camel@zv.wilibox.com> (raw)
In-Reply-To: <20070517184556.GA81@tv-sign.ru>

Hello Oleg,

On Thu, 2007-05-17 at 22:45 +0400, Oleg Nesterov wrote:
> 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.

You are welcome. I wish I could determine and fix the problem myself. I
will try to help, debug the problem as long as there is any progress or
ideas to try out.

> 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.

Can this be related to :

CONFIG_PREEMPT=y
# CONFIG_PREEMPT_BKL is not set


> 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 have uploaded files at http://barclay.balt.net/~zilvinas/oops/ 

workqueue.objdump - without any patch.
workqueue+oleg-old.objdump - with older patch Oleg sent on Thu, 17 May.
workqueue+oleg-new.objdump - with the newest patch from Oleg applied.

For what it's worth, I am using Debian/Unstable 
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c
++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1
--enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug
--enable-mpfr --enable-checking=release x86_64-linux-gnu
Thread model: posix
gcc version 4.1.3 20070514 (prerelease) (Debian 4.1.2-7)

$ ld -V
GNU ld (GNU Binutils for Debian) 2.17.50.20070426
  Supported emulations:
   elf_x86_64
   elf_i386
   i386linux

> ? I doubt very much I'll see something interesting, but who knows...
> 
> Thanks!
> 
> Oleg.
> 


  reply	other threads:[~2007-05-18 10:47 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
2007-05-18 10:47         ` Zilvinas Valinskas [this message]
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=1179485230.3800.20.camel@zv.wilibox.com \
    --to=zilvinas@wilibox.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    /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

all inboxes | Powered by JetHome®