From: Vlastimil Babka <vbabka@suse.cz>
To: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: 3.18-rc3: soft lockup in compact_zone, dead machine
Date: Fri, 07 Nov 2014 17:54:16 +0100 [thread overview]
Message-ID: <545CF938.7050906@suse.cz> (raw)
In-Reply-To: <20141107100611.GA4175@amd>
On 11/07/2014 11:06 AM, Pavel Machek wrote:
> Hi!
>
> My main machine died completely, it seems that original failure was
> soft lockup in compact_zone().
(expanding CC)
Welcome to the club...
http://article.gmane.org/gmane.linux.kernel.mm/124451/match=isolate_freepages_block+very+high+intermittent+overhead
https://lkml.org/lkml/2014/11/4/144
https://lkml.org/lkml/2014/11/4/904
How reproducible is your case? So far it seems that git revert
e14c720efdd73c6d69cd8d07fa894bcd11fe1973 helped one of the reporters.
I still don't know what's wrong, but suspect a free scanner
(cc->free_pfn) position being broken (i.e. underflow), which would allow
isolate_migratepages() to run for a loooooooong time. The code does
cond_resched() periodically, so soft lockup looks strange, but I guess
that can happen in some contexts?
Vlastimil
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
David Rientjes <rientjes@google.com>,
linux-mm <linux-mm@kvack.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: 3.18-rc3: soft lockup in compact_zone, dead machine
Date: Fri, 07 Nov 2014 17:54:16 +0100 [thread overview]
Message-ID: <545CF938.7050906@suse.cz> (raw)
In-Reply-To: <20141107100611.GA4175@amd>
On 11/07/2014 11:06 AM, Pavel Machek wrote:
> Hi!
>
> My main machine died completely, it seems that original failure was
> soft lockup in compact_zone().
(expanding CC)
Welcome to the club...
http://article.gmane.org/gmane.linux.kernel.mm/124451/match=isolate_freepages_block+very+high+intermittent+overhead
https://lkml.org/lkml/2014/11/4/144
https://lkml.org/lkml/2014/11/4/904
How reproducible is your case? So far it seems that git revert
e14c720efdd73c6d69cd8d07fa894bcd11fe1973 helped one of the reporters.
I still don't know what's wrong, but suspect a free scanner
(cc->free_pfn) position being broken (i.e. underflow), which would allow
isolate_migratepages() to run for a loooooooong time. The code does
cond_resched() periodically, so soft lockup looks strange, but I guess
that can happen in some contexts?
Vlastimil
next prev parent reply other threads:[~2014-11-07 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:06 3.18-rc3: soft lockup in compact_zone, dead machine Pavel Machek
2014-11-07 16:54 ` Vlastimil Babka [this message]
2014-11-07 16:54 ` Vlastimil Babka
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=545CF938.7050906@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@osdl.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pavel@ucw.cz \
--cc=rientjes@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.