From: "George Spelvin" <linux@horizon.com>
To: dhillf@gmail.com, linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: v3.2-rc2: kernel BUG at mm/migrate.c:578
Date: 3 Dec 2011 23:13:05 -0500 [thread overview]
Message-ID: <20111204041305.30099.qmail@science.horizon.com> (raw)
In-Reply-To: <CAJd=RBDUyH9BygNQghnjNPr8tf0jCLY2c8scfu_sKZ5goFfPqg@mail.gmail.com>
> The following diff is prepared for spotting/catching the triggered bug,
> would you please take another try with it included?
Sure thing. Thanks for the help! It's my desktop at work, so
nothing will happen until Monday at the earliest, and it
was several days before triggering before.
You'd like a copy of the (more informative, presumably) kernel
log if it triggers again? Anything else?
Oh! I stuffed a lot of extra memory I found lying around in the machine
the other day. Enough (16G) that a single 32-bit process couldn't
possibly get into trouble. Should I take it out to increase memory
pressure?
prev parent reply other threads:[~2011-12-04 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 14:07 George Spelvin
2011-12-01 3:01 ` Hugh Dickins
2011-12-01 3:57 ` George Spelvin
2011-12-04 3:36 ` Hillf Danton
2011-12-04 4:13 ` George Spelvin [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=20111204041305.30099.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®