All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sławek Kosowski" <slawek.k_xl@wp.pl>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Kernel paging request error
Date: Sat, 27 Oct 2012 14:36:29 +0200	[thread overview]
Message-ID: <508bd54daa7c16.24872119@wp.pl> (raw)
In-Reply-To: <5086e5740096e2.94910907@wp.pl> <1351068592.2237.104.camel@zakaz.uk.xensource.com>

Thank you, now I don't have any errors after reboot, we'll see how it will be in the future.

Regards
Slawek

> On Tue, 2012-10-23 at 19:44 +0100, Sławek Kosowski wrote:
> > Reposting from xen-users (no response)
> > I'm having a problem with: http://pastebin.com/CuGHqwhy
> > It occurs on the reboot, but sometimes, when I try to start manually one 
> of
> > my machines. Sometime, one of the machines does not want to start
> > permanently and I have to reinstall/restore it.
> 
> One experiment to try, based on Debian bug #642154 would be to try
> "noxsave" and/or "noxsaveopt" on your kernel command line. Please try
> each independently and both together.
> 
> I thought this sort of thing was ironed out before 3.2. Since you are
> running a bpo kernel you could also consider running a backport of Xen
> 4.1 from Wheezy as well.
> 
> > This problem comes for me randomly, but maybe there is a trigger.
> > I've tried to follow:
> > http://xen.1045712.n5.nabble.com/2-6-32-27-dom0-BUG-unable-to-handle-kernel-paging-request-td3323011.html
> > and raise /proc/sys/vm/min_free_kbytes, but it did not help.
> 
> That is a completely unrelated problem, "BUG unable to handle kernel
> paging request" is a very generic error message which is common to loads
> of different potential issues.
> 
> [...]
> 
> Ian.

      reply	other threads:[~2012-10-27 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 18:44 Kernel paging request error Sławek Kosowski
2012-10-24  8:39 ` Jan Beulich
2012-10-24  8:49 ` Ian Campbell
2012-10-27 12:36   ` Sławek Kosowski [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=508bd54daa7c16.24872119@wp.pl \
    --to=slawek.k_xl@wp.pl \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 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.