All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weekes <lists.xen@nuclearfallout.net>
To: xen-devel@lists.xensource.com,
	"Christopher S. Aker" <caker@theshore.net>
Subject: Re: 2.6.32.27 dom0 - BUG: unable to handle kernel	paging request
Date: Mon, 10 Jan 2011 13:49:28 -0800	[thread overview]
Message-ID: <4D2B7EE8.7070309@nuclearfallout.net> (raw)
In-Reply-To: <20110110185610.GC9837@dumpdata.com>

> We hit the BUG again on a third test box -- at least it's fairly easy to reproduce.  Has anyone had a chance to poke at this, or have a suggestion for something for me to try/test?

Have you tried raising /proc/sys/vm/min_free_kbytes ? When I was seeing 
a similar "unable to handle kernel paging request" error on some 
machines, I bumped mine up to 32768, and it seemed to eliminate the problem.

-John

  reply	other threads:[~2011-01-10 21:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 22:57 2.6.32.27 dom0 - BUG: unable to handle kernel paging request Christopher S. Aker
2010-12-31  1:29 ` Jeremy Fitzhardinge
2010-12-31 17:19   ` Christopher S. Aker
2011-01-02 20:08     ` Christopher S. Aker
2011-01-04  9:16 ` Ian Campbell
2011-01-04 20:30   ` Christopher S. Aker
2011-01-04 20:34     ` Ian Campbell
2011-01-04 21:59       ` Christopher S. Aker
2011-01-09 18:07         ` Christopher S. Aker
2011-01-10 18:56           ` Konrad Rzeszutek Wilk
2011-01-10 21:49             ` John Weekes [this message]
2011-01-15 15:57               ` Christopher S. Aker
2011-01-31 21:07                 ` Christopher S. Aker
2011-01-31 21:17                   ` Konrad Rzeszutek Wilk
2011-01-31 22:19                     ` Jeremy Fitzhardinge
2011-01-31 22:22                   ` Jeremy Fitzhardinge
2011-01-31 22:25                   ` Jeremy Fitzhardinge
2011-02-14 23:52                     ` Christopher S. Aker
2011-02-15  0:19                       ` Jeremy Fitzhardinge
2011-02-15  1:15                         ` Christopher S. Aker
2011-01-13 14:43           ` Konrad Rzeszutek Wilk

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=4D2B7EE8.7070309@nuclearfallout.net \
    --to=lists.xen@nuclearfallout.net \
    --cc=caker@theshore.net \
    --cc=xen-devel@lists.xensource.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.