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 <[email protected]>
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 <[email protected]>
Acked-by: Konrad Rzeszutek Wilk <[email protected]>
LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop>
Signed-off-by: H. Peter Anvin <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
: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.
On 04/14/2011 11:35 PM, guilherme m. schroeder wrote:
> 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 <[email protected]>
> 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 <[email protected]>
> Acked-by: Konrad Rzeszutek Wilk <[email protected]>
> LKML-Reference: <alpine.DEB.2.00.1103171739050.3382@kaball-desktop>
> Signed-off-by: H. Peter Anvin <[email protected]>
> Signed-off-by: Greg Kroah-Hartman <[email protected]>
>
> :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.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Can you try 2.6.32.37-rc1?
The patch you're referring to was committed I think along with another
patch which caused some trouble in the -stable trees(I'm not surea bout
that though :/).
And in 2.6.32.37-rc1 it was reverted:
[59/74] [PATCH] Revert "x86: Cleanup highmap after brk is concluded"
Maybe it fixes your problem.
--
Stratos Psomadakis
<[email protected]>
On Thu, Apr 14, 2011 at 5:52 PM, Stratos Psomadakis <[email protected]> wrote:
> Can you try 2.6.32.37-rc1?
> The patch you're referring to was committed I think along with another
> patch which caused some trouble in the -stable trees(I'm not surea bout
> that though :/).
> And in 2.6.32.37-rc1 it was reverted:
> [59/74] [PATCH] Revert "x86: Cleanup highmap after brk is concluded"
> Maybe it fixes your problem.
>
> --
> Stratos Psomadakis
> <[email protected]>
No problem with 2.6.32.37-rc1.
Do I need to bisect 2.6.32.37-rc1 against 2.6.32.36 to make sure it is
the patch that you mentioned?
And if we find it, there'll be a 2.6.32.36.1 release or we need to
wait for 2.6.32.37?
I'm asking this because some distros are already taking 2.6.32.36
(Debian 6.0 proposed kernel for example).
2.6.32.37 fixed the regression.
Thanks.