Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757031Ab3JRUMT (ORCPT ); Fri, 18 Oct 2013 16:12:19 -0400 Received: from mx12.netapp.com ([216.240.18.77]:54287 "EHLO mx12.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756856Ab3JRUMP convert rfc822-to-8bit (ORCPT ); Fri, 18 Oct 2013 16:12:15 -0400 X-IronPort-AV: E=Sophos;i="4.93,524,1378882800"; d="scan'208";a="102054501" From: "Myklebust, Trond" To: Helge Deller CC: Linux Kernel Development , NFS list , linux-parisc Subject: Re: 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU? Thread-Topic: 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU? Thread-Index: AQHOy3lvGBMaqnz/ckaeVwLZiNCsrJn52CeAgAF2G4CAAALIgIAAB40AgAACeYA= Date: Fri, 18 Oct 2013 20:12:14 +0000 Message-ID: <1382127133.20461.9.camel@leira.trondhjem.org> References: <52604BA9.20104@gmx.de> <1382044045.3216.44.camel@leira.trondhjem.org> <52618B5F.4000508@gmx.de> <1382124981.20461.4.camel@leira.trondhjem.org> <5261940A.4090101@gmx.de> In-Reply-To: <5261940A.4090101@gmx.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="utf-7" Content-ID: <0C8CAFECCC43B14290CE04CBE14BD7C3@hq.netapp.com> Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1511 Lines: 33 On Fri, 2013-10-18 at 22:03 +-0200, Helge Deller wrote: +AD4- On 10/18/2013 09:36 PM, Myklebust, Trond wrote: +AD4- +AD4- Also, could you please try a sysRQ-t the next time it happens, so that +AD4- +AD4- we can get a trace of where the mount program is hanging. Knowing that +AD4- +AD4- the mount is stuck in +ACIAXwBf-schedule()+ACI- is not really interesting unless we +AD4- +AD4- know from where that was called. +AD4- +AD4- Actually, the machine was still running in this state. +AD4- Here is sysrq-t: +AD4- +AFs-112009.084000+AF0- mount S 00000000401040c0 0 25331 1 0x00000010 +AD4- +AFs-112009.084000+AF0- Backtrace: +AD4- +AFs-112009.084000+AF0- +AFsAPA-0000000040113a68+AD4AXQ- +AF8AXw-schedule+0x500/0x810- +AD4- +AFs-112009.232000+AF0- +AD4- +AFs-112009.232000+AF0- mount.nfs D 00000000401040c0 0 25332 25331 0x00000010 +AD4- +AFs-112009.232000+AF0- Backtrace: +AD4- +AFs-112009.232000+AF0- +AFsAPA-0000000040113a68+AD4AXQ- +AF8AXw-schedule+0x500/0x810- That makes no sense unless sysrq-t works differently on parisc than on other platforms. I'd expect the backtrace to at least include a system call. Parisc experts? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust+AEA-netapp.com www.netapp.com -- 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/