Messages in this thread | | | From | "Myklebust, Trond" <> | Subject | Re: 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU? | Date | Fri, 18 Oct 2013 20:12:14 +0000 |
| |
On Fri, 2013-10-18 at 22:03 +0200, Helge Deller wrote: > On 10/18/2013 09:36 PM, Myklebust, Trond wrote: > > Also, could you please try a sysRQ-t the next time it happens, so that > > we can get a trace of where the mount program is hanging. Knowing that > > the mount is stuck in "__schedule()" is not really interesting unless we > > know from where that was called. > > Actually, the machine was still running in this state. > Here is sysrq-t: > [112009.084000] mount S 00000000401040c0 0 25331 1 0x00000010 > [112009.084000] Backtrace: > [112009.084000] [<0000000040113a68>] __schedule팞瓓ﴱ > [112009.232000] > [112009.232000] mount.nfs D 00000000401040c0 0 25332 25331 0x00000010 > [112009.232000] Backtrace: > [112009.232000] [<0000000040113a68>] __schedule팞瓓ﴱ
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@netapp.com www.netapp.com
| |