AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel?

["Carsten Schiers" <carsten@xxxxxxxxxx>]

OK, I took out 2GB of memory to be at 2GB now. It will come up, but says 
now:

[    3.470518] ACPI: Power Button [PWRB]
[    3.542045] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    3.543005] ACPI: Power Button [PWRF]
[    3.609966] ACPI: SSDT 000000007ffb00b0 00235 (v01 DpgPmm  P001Ist 
00000011 INTL 20051117)
[    3.660356] ACPI: SSDT 000000007ffb02f0 00235 (v01 DpgPmm  P002Ist 
00000012 INTL 20051117)
[    3.710648] ------------[ cut here ]------------
[    3.711073] WARNING: at mm/page_alloc.c:1820 
__alloc_pages_nodemask+0x1b5/0x603()
[    3.711073] Hardware name: To Be Filled By O.E.M.
[    3.711073] Modules linked in:
[    3.711073] Pid: 1, comm: swapper Not tainted 2.6.32.21 #1
[    3.711073] Call Trace:
[    3.711073]  [<ffffffff810478da>] warn_slowpath_common+0x77/0x8f
[    3.711073]  [<ffffffff81047901>] warn_slowpath_null+0xf/0x11
[    3.711073]  [<ffffffff810afcae>] __alloc_pages_nodemask+0x1b5/0x603
[    3.711073]  [<ffffffff81030e41>] ? __ioremap_caller+0x291/0x2f7
[    3.711073]  [<ffffffff8146bed2>] ? _spin_unlock_irqrestore+0x48/0x4b
[    3.711073]  [<ffffffff81459bc1>] ? acpi_os_map_memory+0x12/0x1b
[    3.711073]  [<ffffffff810b010e>] __get_free_pages+0x12/0x4f
[    3.711073]  [<ffffffff810daae5>] __kmalloc+0x42/0x180
[    3.711073]  [<ffffffff81253f53>] acpi_os_allocate+0x33/0x35
[    3.711073]  [<ffffffff8125402d>] acpi_ex_load_op+0xd8/0x263
[    3.711073]  [<ffffffff812567ae>] acpi_ex_opcode_1A_1T_0R+0x25/0x4b
[    3.711073]  [<ffffffff8124e020>] acpi_ds_exec_end_op+0xea/0x3d6
[    3.711073]  [<ffffffff8125feef>] acpi_ps_parse_loop+0x7bb/0x940
[    3.711073]  [<ffffffff8124e8f5>] ? 
acpi_ds_call_control_method+0x174/0x1e3
[    3.711073]  [<ffffffff8125eff5>] acpi_ps_parse_aml+0x9a/0x2d9
[    3.711073]  [<ffffffff8126073a>] acpi_ps_execute_method+0x1e4/0x2b6
[    3.711073]  [<ffffffff8125bec9>] acpi_ns_evaluate+0xe1/0x1a8
[    3.711073]  [<ffffffff8125b910>] acpi_evaluate_object+0xf9/0x1f2
[    3.711073]  [<ffffffff81023da1>] ? init_intel_pdc+0xd1/0x191
[    3.711073]  [<ffffffff81269ec7>] acpi_processor_set_pdc+0x3c/0x3e
[    3.711073]  [<ffffffff8146988d>] xen_acpi_processor_add+0x303/0x43a
[    3.711073]  [<ffffffff812453a7>] acpi_device_probe+0x4b/0x11d
[    3.711073]  [<ffffffff812f7f70>] driver_probe_device+0x9a/0x11f
[    3.711073]  [<ffffffff812f804d>] __driver_attach+0x58/0x7c
[    3.711073]  [<ffffffff812f7ff5>] ? __driver_attach+0x0/0x7c
[    3.711073]  [<ffffffff812f75ce>] bus_for_each_dev+0x4e/0x83
[    3.711073]  [<ffffffff812f7def>] driver_attach+0x19/0x1b
[    3.711073]  [<ffffffff812f7a47>] bus_add_driver+0xb1/0x1fe
[    3.711073]  [<ffffffff812f8311>] driver_register+0x99/0x10a
[    3.711073]  [<ffffffff8173c1c1>] ? acpi_processor_init+0x0/0x128
[    3.711073]  [<ffffffff81245de0>] acpi_bus_register_driver+0x3e/0x40
[    3.711073]  [<ffffffff8126cd2a>] xen_acpi_processor_init+0x10/0x12
[    3.711073]  [<ffffffff8173c26f>] acpi_processor_init+0xae/0x128
[    3.711073]  [<ffffffff81245de0>] ? 
acpi_bus_register_driver+0x3e/0x40
[    3.711073]  [<ffffffff8173c14b>] ? acpi_video_init+0x0/0x76
[    3.711073]  [<ffffffff8100a05f>] do_one_initcall+0x59/0x170
[    3.711073]  [<ffffffff817176fe>] kernel_init+0x153/0x1a9
[    3.711073]  [<ffffffff81013caa>] child_rip+0xa/0x20
[    3.711073]  [<ffffffff81012e61>] ? int_ret_from_sys_call+0x7/0x1b
[    3.711073]  [<ffffffff8101361d>] ? retint_restore_args+0x5/0x6
[    3.711073]  [<ffffffff81013ca0>] ? child_rip+0x0/0x20
[    3.711073] ---[ end trace a7919e7f17c0a725 ]---
[    3.711073] ACPI Error (psparse-0537): Method parse/execution failed 
[\_PR_.P003._OSC] (Node ffff88001f865640), AE_NO_MEMORY
[    5.440328] ACPI Error (psparse-0537): Method parse/execution failed 
[\_PR_.P003._PDC] (Node ffff88001f865620), AE_NO_MEMORY
[    5.508528] ACPI Error (psparse-0537): Method parse/execution failed 
[\_PR_.P004._OSC] (Node ffff88001f8656c0), AE_NO_MEMORY
[    5.575663] ACPI Error (psparse-0537): Method parse/execution failed 
[\_PR_.P004._PDC] (Node ffff88001f8656a0), AE_NO_MEMORY
[    5.648962] Event-channel device installed.

BR,
Carsten.

-----Ursprüngliche Nachricht-----
Von: Carsten Schiers 
Gesendet: Donnerstag, 9. September 2010 20:41
An: JBeulich@xxxxxxxxxx; Carsten Schiers
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Betreff: AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 
pvops Kernel?

OK, here are the three SSDT's that I seem to have. BR, Carsten.

-----Ursprüngliche Nachricht-----
Von: Carsten Schiers
Gesendet: Donnerstag, 9. September 2010 20:27
An: JBeulich
Cc: xen-devel
Betreff: AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 
pvops Kernel?

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







_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel