From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, mgorman@suse.de
Cc: dave@linux.vnet.ibm.com, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 3.7-rc6 soft lockup in kswapd0
Date: 23 Nov 2012 05:02:22 -0500 [thread overview]
Message-ID: <20121123100222.21774.qmail@science.horizon.com> (raw)
In-Reply-To: <20121123085137.GA646@suse.de>
tl;dr: Have installed Dave Hansen's patch as requested, rebooted.
Now it's a matter of waiting for lockup...
Mel Gorman wrote:
> heh, those P4s are great for keeping the room warm in winter. Legacy
> high five?
I wanted a physically separate box for some lightly used outside-facing
network services, and it was lying around. Since then, if it ain't broke,
don't fix it.
If you want *legacy*, a few months ago I installed recent kernels on
an original F00F-bug Pentium (96 MB RAM,bit only 64 MB cacheable!),
and an original MCM PPro. They aren't actually in service, though.
> Joking aside, the UP aspect of this is the most relevant.
Yeah, I wondered how much testing that got these days. :-)
>> It's kind of a funny lockup. Some things work:
>>
>> - TCP SYN handshake
>> - Alt-SysRq
>>
>> And others don't:
>>
>> - Caps lock
>> - Shift-PgUp
>> - Alt-Fn
>> - Screen unblanking
>> - Actually talking to a daemon
>>
> So basically interrupts work but the machine has otherwise locked up. On
> a uniprocessor, it's possible it is infinite looping in kswapd and
> nothing else is getting the chance to run if it never hits a
> cond_resched().
Did caps lock LED handling get moved to something above interrupt context?
I used to use that as the test of "is the machine locked hard".
It might be worth seeing if that functionality can be restored. The fact
that I can make the console scroll down with Alt-SysRq, but can't scroll
back up to see what just got printed, is maddening.
> Ok, is there any chance you can capture more of sysrq+m, particularly the
> bits that say how much free memory there is and many pages of each order
> that is free? If you can't, it's ok. I ask because my kernel bug dowsing
> rod is twitching in the direction of the recent free page accounting bug
> Dave Hansen identified and fixed -- https://lkml.org/lkml/2012/11/21/504
Will do when I get in front of the machine again. I had rebooted with
2.6.5, but I can remotely reboot with 2.7-rc6, then it's just a matter
of waiting.
> You might have a machine that is able to hit this particular bug faster. It's
> not a memory leak as such, but it acts like one. The kernel would think
> the watermarks are not met because it's using NR_FREE_PAGES instead of
> checking the free lists.
>
> Can you try that patch out please?
Okay, so I've cherry-picked ef6c5be658f6a70c1256fbd18e18ee0dc24c3386
from mainline, and rebooted.
I've never tried disabling console blanking remotely, though. I did
# echo '^[[9;0]' > /dev/tty0
# echo '^[[9;0]' > /dev/tty1
# echo '^[[14;0]' > /dev/tty1
# echo '^[[14;0]' > /dev/tty0
I hope that works...
> The interesting information in this case is further up. First look for
> the line that looks kinda like this
Will do if it locks up again. I did notice that all three zones had
at least one free page of size 4096kb, FWIW.
> The free page counter and these free lists should be close together. If
> there is a big gap then it's almost certainly the bug Dave identified.
>
> There is another potential infinite loop in kswapd that Johannes has
> identified and it could also be that. However, lets rule out Dave's bug
> first.
Thanks a lot!
next prev parent reply other threads:[~2012-11-23 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 17:58 3.7-rc6 soft lockup in kswapd0 George Spelvin
2012-11-22 22:06 ` Jan Kara
2012-11-22 22:36 ` Jan Kara
2012-11-23 8:51 ` Mel Gorman
2012-11-23 10:02 ` George Spelvin [this message]
2012-11-24 7:52 ` George Spelvin
2012-11-26 3:58 ` George Spelvin
2012-11-26 10:01 ` Mel Gorman
2012-11-26 13:05 ` George Spelvin
2012-11-26 18:32 ` Johannes Weiner
2012-11-26 18:53 ` George Spelvin
2012-11-26 19:09 ` Mel Gorman
2012-11-27 21:25 ` George Spelvin
2012-11-28 11:39 ` Mel Gorman
2012-11-29 14:54 ` George Spelvin
2012-11-29 15:20 ` Mel Gorman
2012-11-29 17:08 ` Johannes Weiner
2012-12-03 18:28 ` George Spelvin
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=20121123100222.21774.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=dave@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).