Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755115AbZLBVTp (ORCPT ); Wed, 2 Dec 2009 16:19:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754273AbZLBVTo (ORCPT ); Wed, 2 Dec 2009 16:19:44 -0500 Received: from 2605ds1-ynoe.0.fullrate.dk ([90.184.12.24]:41501 "EHLO shrek.krogh.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753016AbZLBVTn (ORCPT ); Wed, 2 Dec 2009 16:19:43 -0500 Message-ID: <4B16D9EC.7080009@krogh.cc> Date: Wed, 02 Dec 2009 22:19:40 +0100 From: Jesper Krogh User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org Subject: Re: 2.6.31.6, unresponsiveness and something with nfs References: <4B13FBE7.9040304@krogh.cc> In-Reply-To: <4B13FBE7.9040304@krogh.cc> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1066 Lines: 27 > I have a system running 2.6.31.6 that when running a particular process > become "unresponsive". I cannot really tell what it is but the effect is > that logins as ordinary users hangs, when that user has its home on a > remote NFS-server. > > so from root "su - localuser" works excellent. But su - user-with-home > on-nfs doesnt. Ok, the situation is more advanced than just that. I now have the "sorting" process running while there is high cpu-only load and that doesn't trigger the problem, so it seems to be that I have to have "large merging, high cpu-load and lots of networktraffic on the NIC (10GbitE)" before I encounter the prooblem. Is there anything I can do to get a trace or other information about what's holding the "login" process back the next time I get into this situation? Thanks -- Jesper -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/