From: "guilherme m. schroeder" <guilherme.m.schroeder@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [REGRESSION] 2.6.32.36 - Linux Xen DomU doesn't boot anymore
Date: Thu, 14 Apr 2011 17:35:58 -0300 [thread overview]
Message-ID: <BANLkTim-KC7qfijD5rFNTR98GSs=cTPzJw@mail.gmail.com> (raw)
Hi,
Linux Kernel 2.6.32.36 introduced a regression that prevents Linux Xen
DomU from booting.
Linux DomU starts and after a while it shutdown without log messages.
I bisected a vanilla kernel from 2.6.32.36 (bad) to 2.6.32.32 (good)
and got this commit:
vm:~/linux-2.6.32.y# git bisect bad
856460aa905dcc6d11a05a832d487a7b0ce69402 is the first bad commit
commit 856460aa905dcc6d11a05a832d487a7b0ce69402
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Fri Feb 18 11:32:40 2011 +0000
xen: set max_pfn_mapped to the last pfn mapped
commit 14988a4d350ce3b41ecad4f63c4f44c56f5ae34d upstream.
Do not set max_pfn_mapped to the end of the initial memory mappings,
that also contain pages that don't belong in pfn space (like the mfn
list).
Set max_pfn_mapped to the last real pfn mapped in the initial memory
mappings that is the pfn backing _end.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
:040000 040000 a679f50b64c290b9a51e3dba8d3d648bca50fdf0
e7b018c4e0015aae44ed6f9f6323d8b13d032b86 M arch
I have tested against XCP 1.0, Citrix XenServer 5.6 and 5.6 FP1.
Without this patch, Linux DomU boots and runs fine.
If more info is needed, please let me know.
next reply other threads:[~2011-04-14 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 20:35 guilherme m. schroeder [this message]
2011-04-14 20:52 ` Stratos Psomadakis
2011-04-14 22:03 ` guilherme m. schroeder
2011-04-15 7:33 ` guilherme m. schroeder
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='BANLkTim-KC7qfijD5rFNTR98GSs=cTPzJw@mail.gmail.com' \
--to=guilherme.m.schroeder@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®