From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: odd userspace lockups.
Date: Tue, 26 Nov 2013 13:58:33 -0500 [thread overview]
Message-ID: <20131126185833.GA4121@redhat.com> (raw)
In-Reply-To: <CA+55aFzvc9g896HK2AVU2A37t50PiCL2+tjGzNyn3BJ-om+7fg@mail.gmail.com>
On Tue, Nov 26, 2013 at 10:44:16AM -0800, Linus Torvalds wrote:
> > At first I thought it was just being really slow, (especially after seeing
> > all those congestion related symbols in the stack traces), but even after
> > being left for hours, it doesn't seem to progress.
>
> It *does* seem to be hung in some congestion thing. Possibly brought
> on by being low on memory due to a memory leak.
>
> I'm not seeing any suspicious locks: the sshd that holds the mmap_sem
> locks for a fork() seems to be in congestion-wait for the disk due to
> trying to allocate memory, exactly like all the trinity children are.
>
> You don't have memory information in your dump, but to me it looks
> like you're basically out of memory (there's a *lot* of
> trinity-children trying to allocate pages), and the oom killer isn't
> triggering for whatever reason.
>
> Of course, it could easily be a kernel memory leak too (rather than
> trinity), triggered by your odd workload.
So, completely different machine: Yesterday I got back from my vacation to
find my router running 3.12+ from a week earlier had hung completely.
On the screen was some oom killer output. After bringing it back up
I looked at the mrtg graphs of it for the last week:
http://codemonkey.org.uk/junk/mem.free-week.png
Those stair-steps are around the time of morning that cron runs.
Normally I reboot that machine every day to update to the latest kernel,
but because I was on vacation, it had enough uptime to accumulate a leak.
That machine is just routing packets (and making pretty mrtg graphs) though,
not doing any fuzz testing or anything weird.
Who knows, maybe it's something totally unrelated. I'll keep poking at things,
and try and find an easier way to reproduce it.
Dave
prev parent reply other threads:[~2013-11-26 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 18:21 odd userspace lockups Dave Jones
2013-11-26 18:44 ` Linus Torvalds
2013-11-26 18:58 ` Dave Jones [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=20131126185833.GA4121@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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