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
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 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
ffffc90000062000
[ 3.749005] IP: [<ffffffff81258492>]
acpi_ex_system_memory_space_handler+0x16d/0x1df
[ 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?
BR,
Carsten.
-----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 2.6.32.18/21
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
"dom_mem="...
Jan
putty.log
Description: Binary data
DSDT.dsl
Description: Binary data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|