From: Helge Deller <deller-Mmb7MZpHnFY@public.gmane.org>
To: "Myklebust,
Trond" <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: Linux Kernel Development
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-parisc
<linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU?
Date: Thu, 31 Oct 2013 20:45:54 +0100 [thread overview]
Message-ID: <5272B372.8040307@gmx.de> (raw)
In-Reply-To: <5262CF20.20301-Mmb7MZpHnFY@public.gmane.org>
On 10/19/2013 08:27 PM, Helge Deller wrote:
> On 10/18/2013 10:12 PM, Myklebust, Trond wrote:
>> On Fri, 2013-10-18 at 22:03 m, 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?
>
> sysrq-t doesn't work differently on parisc. For other processes I do get
> a backtrace like the one on x86_64.
> That's the main reason why I asked for ideas here on the list.
> I do see the stuck process, but don't see any indications where it comes from.
I'm pretty sure that the regression (kswapd using 100% CPU) I reported here is fixed by this patch:
http://git.kernel.org/cgit/linux/kernel/git/deller/parisc-linux.git/commit/?id=c56b097af26cb11c1f49a4311ba538c825666fed
I will start some testing...
Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-31 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52604BA9.20104@gmx.de>
[not found] ` <1382044045.3216.44.camel@leira.trondhjem.org>
2013-10-18 19:26 ` 3.12-rcX - NFS regression - kswapd0 / kswapd1 stays using 100% CPU? Helge Deller
[not found] ` <52618B5F.4000508-Mmb7MZpHnFY@public.gmane.org>
2013-10-18 19:36 ` Myklebust, Trond
[not found] ` <1382124981.20461.4.camel-5lNtUQgoD8Pfa3cDbr2K10B+6BGkLq7r@public.gmane.org>
2013-10-18 20:03 ` Helge Deller
[not found] ` <5261940A.4090101-Mmb7MZpHnFY@public.gmane.org>
2013-10-18 20:12 ` Myklebust, Trond
2013-10-19 18:27 ` Helge Deller
[not found] ` <5262CF20.20301-Mmb7MZpHnFY@public.gmane.org>
2013-10-31 19:45 ` Helge Deller [this message]
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=5272B372.8040307@gmx.de \
--to=deller-mmb7mzphnfy@public.gmane.org \
--cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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