This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with pvops Ke

To: JBeulich <JBeulich@xxxxxxxxxx>
Subject: AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with pvops Kernel?
From: "Carsten Schiers" <carsten@xxxxxxxxxx>
Date: Thu, 9 Sep 2010 20:27:10 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 09 Sep 2010 11:28:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C88CBAD02000078000152AD@xxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Ups. My fault. But this won't make a difference. Find log for 3840MB, 
1024MB, and 256MB in attached log.

(XEN) Command line: dom0_mem=3840M loglvl=all guest_loglvl=all 
sync_console console_to_ring com1=19200,8n1 console=com1
[    3.579906] input: Power Button as 
[    3.580827] ACPI: Power Button [PWRF]
[    3.647887] ACPI: SSDT 00000000bbfb00b0 00235 (v01 DpgPmm  P001Ist 
00000011 INTL 20051117)
[    3.698280] ACPI: SSDT 00000000bbfb02f0 00235 (v01 DpgPmm  P002Ist 
00000012 INTL 20051117)
(XEN) mm.c:860:d0 Error getting mfn 80000 (pfn 7c9ec) from L1 entry 
8000000080000473 for l1e_owner=0, pg_owner=32753
[    3.749005] BUG: unable to handle kernel paging request at 
[    3.749005] IP: [<ffffffff81258492>] 
[    3.749005] PGD bb80d067 PUD bb80e067 PMD bb80f067 PTE 0
[    3.749005] Oops: 0000 [#1] SMP 

I did a 

  cp /proc/acpi/dsdt > DSDT
  iasl -d DSDT 

and provided the output, just in case it is what you needed. I will for 
sure need some time to understand that.
Is the hypothesis that a) the BIOS is wrong, and b) Xen is checking more 
extreme than bare metal, so we need to
make the Xen Code a bit more relaxed (error message instead of crash)?

How to extract SSDT I don't know. Are they in this file also?


-----Ursprüngliche Nachricht-----
Von: Jan Beulich [mailto:JBeulich@xxxxxxxxxx] 
Gesendet: Donnerstag, 9. September 2010 11:58
An: Carsten Schiers
Cc: xen-devel
Betreff: AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with 
pvops Kernel?

>>> On 08.09.10 at 22:15, "Carsten Schiers" <carsten@xxxxxxxxxx> wrote:
> Hi,
> no change when I set e.g. to dom0_mem=3000M (see below and in log. In 
> log, I also tried 196M, same result).

You spell it right here, but the logs in the other mail say you used


Attachment: putty.log
Description: Binary data

Attachment: DSDT.dsl
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>