| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)"
|
To: |
Andreas Kinzler <ml-xen-devel@xxxxxx> |
|
Subject: |
Re: [Xen-devel] Xen dom0 crash: "d0:v0: unhandled page fault (ec=0000)" |
|
From: |
Gianni Tedesco <gianni.tedesco@xxxxxxxxxx> |
|
Date: |
Fri, 29 Oct 2010 16:44:23 +0100 |
|
Cc: |
"Alan J. Wylie" <NDA5OWUy@xxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Konrad, Stefan Kuhne <stefan.kuhne@xxxxxxx>, sven <ml@xxxxxxxxxxxxx> |
|
Delivery-date: |
Fri, 29 Oct 2010 08:53:49 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1287564863.12843.4194.camel@xxxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<19629.39326.337589.71778@xxxxxxxxxxx> <1287498599.12843.2111.camel@xxxxxxxxxxxxxxxxxxxxxx> <4CBDB229.3030501@xxxxxxxxxxxxx> <1287503143.12843.2191.camel@xxxxxxxxxxxxxxxxxxxxxx> <4CBE2A43.70200@xxxxxx> <1287564863.12843.4194.camel@xxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Wed, 2010-10-20 at 09:54 +0100, Gianni Tedesco wrote:
> On Wed, 2010-10-20 at 00:31 +0100, Andreas Kinzler wrote:
> > On 19.10.2010 17:45, Gianni Tedesco wrote:
> > > ditto, I suspected a known bug in my gcc version which broke xchg
> > > because when I compiled with -O2 instead of -Os... the problem went away
> > > but then something else bad happened later (I forget the details, and it
> > > was too many config tweaks ago to get back to last time I had it working
> > > that well)
> >
> > Jeremy, one user earlier reported that he found out that for him there
> > seems to be a relation between kernel size and crash status. He just
> > added/removed some options that could never influence the "crash status"
> > (like adding/removing netfilter modules). With all the experiences here,
> > is may be useful to check for code paths related to kernel size.
> >
> > Regards Andreas
I have dmesg output from 2.6.32.18-ge6b9b2c and the current broken
version.
http://pastebin.com/3m0DpDdW - 2.6.32.24-gd0054d6-dirty - broken
http://pastebin.com/yC4CzLaZ - 2.6.32.18-ge6b9b2c - working
In the panic you can see that %rax contains what the kernel thinks is
xen_start_info (0xffffffff817d3000) and from the xen logs, that is
correct.
>From the kernel messages it looks like the e820 map is being calculated
incorrectly, leading to bad memory mappings being setup which somehow
end up nuking the pagetable entry for xen start info. The
last_pfn/max_arch_pfn end up being an order of magnitude larger even
though both are booted with identical xen and kernel commandline params.
Xen has dom0_mem=752M.
Gianni
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home