From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: x86@kernel.org
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@suse.de>
Subject: Possible sandybridge livelock issue
Date: Fri, 13 May 2011 11:12:36 -0500 [thread overview]
Message-ID: <1305303156.2611.51.camel@mulgrave.site> (raw)
We've just come off a large round of debugging a kswapd problem over on
linux-mm:
http://marc.info/?t=130392066000001
The upshot was that kswapd wasn't being allowed to sleep (which we're
now fixing). However, in spite of intensive efforts, the actual hang
was only reproducible on sandybridge laptops.
When the hang occurred, kswapd basically pegged one core in 100% system
time. This looks like there's something specific to sandybridge that
causes this type of bad interaction. I was wondering if it could be
something to to with a scheduling problem in turbo mode? Once kswapd
goes flat out, the core its on will kick into turbo mode, which causes
it to get preferentially scheduled there, leading to the live lock.
The only evidence I have to support this theory is that when I reproduce
the problem with PREEMPT, the core pegs at 100% system time and stays
there even if I turn off the load. However, if I can execute work that
causes kswapd to be kicked off the core it's running on, it will calm
back down and go to sleep.
James
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-05-13 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:12 James Bottomley [this message]
2011-05-13 16:36 ` Possible sandybridge livelock issue Andi Kleen
2011-05-13 17:08 ` Christoph Lameter
2011-05-13 18:23 ` Andi Kleen
2011-05-13 18:49 ` James Bottomley
2011-05-16 6:52 ` Ingo Molnar
2011-05-16 6:29 ` Ingo Molnar
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=1305303156.2611.51.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).