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

[Carsten Schiers <carsten@xxxxxxxxxx>]

Hi,

I repeat to report this issue, because Jeremy thinks it might be more a Xen 
related
issue. Also I missed to provide the comunity with an excerpt of the log, for 
those
only able to read quickly through their mails:

Xen 4.0.1 self compiled on Debian Lenny 5.0.5 64 Bit, 2.6.32.18 and 2.6.32.21 
pvops 
kernel boots well w/o Xen, but reports the following error (complete log 
attached):

[    3.478270] ACPI: Power Button [PWRB]
[    3.549779] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    3.550689] ACPI: Power Button [PWRF]
[    3.617753] ACPI: SSDT 00000000bbfb00b0 00235 (v01 DpgPmm  P001Ist 00000011 
INTL 20051117)
[    3.668512] ACPI: SSDT 00000000bbfb02f0 00235 (v01 DpgPmm  P002Ist 00000012 
INTL 20051117)
(XEN) mm.c:860:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 
8000000080000473 for l1e_owner=0, pg_owner=32753
[    3.719125] BUG: unable to handle kernel paging request at ffffc90000062000
[    3.719125] IP: [<ffffffff81223d03>] 
acpi_ex_system_memory_space_handler+0x16e/0x1cf
[    3.719125] PGD 1f80f067 PUD 1f854067 PMD 1f855067 PTE 0
[    3.719125] Oops: 0000 [#1] SMP 
[    3.719125] last sysfs file: 
[    3.719125] CPU 0 
[    3.719125] Modules linked in:
[    3.719125] Pid: 1, comm: swapper Not tainted 2.6.32.21 #2 To Be Filled By 
O.E.M.
[    3.719125] RIP: e030:[<ffffffff81223d03>]  [<ffffffff81223d03>] 
acpi_ex_system_memory_space_handler+0x16e/0x1cf
[    3.719125] RSP: e02b:ffff88001f86b9a0  EFLAGS: 00010246
[    3.719125] RAX: ffffc90000062000 RBX: 0000000000001000 RCX: 0000000000000040
[    3.719125] RDX: ffffc90000062000 RSI: 0000000000000001 RDI: 8000000080000273
[    3.719125] RBP: ffff88001f86b9d0 R08: ffffffff8165a270 R09: 0000000000000068
[    3.719125] R10: 0000000000080000 R11: 0000000000000001 R12: 0000000080000000
[    3.719125] R13: ffff88001f9a6a40 R14: 0000000000000008 R15: ffff88001f86ba88
[    3.719125] FS:  0000000000000000(0000) GS:ffff880002120000(0000) 
knlGS:0000000000000000
[    3.719125] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    3.719125] CR2: ffffc90000062000 CR3: 0000000001001000 CR4: 0000000000000660
[    3.719125] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    3.719125] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    3.719125] Process swapper (pid: 1, threadinfo ffff88001f86a000, task 
ffff88001f870000)
[    3.719125] Stack:
[    3.719125]  0000000000000000 ffffffff81223b95 ffff88001ee22288 
ffff88001f8624c8
[    3.719125] <0> ffff88001ee22048 0000000000000000 ffff88001f86ba30 
ffffffff8121c7a1
[    3.719125] <0> 0000000000000024 ffff88001f86ba88 0000000000000008 
0000000000000000
[    3.719125] Call Trace:
[    3.719125]  [<ffffffff81223b95>] ? 
acpi_ex_system_memory_space_handler+0x0/0x1cf
[    3.719125]  [<ffffffff8121c7a1>] acpi_ev_address_space_dispatch+0x176/0x1c3
[    3.719125]  [<ffffffff8121f6ac>] acpi_ex_load_op+0x93/0x254
[    3.719125]  [<ffffffff812226a7>] ? acpi_ex_resolve_operands+0x1e5/0x4e2
[    3.719125]  [<ffffffff81221fcf>] acpi_ex_opcode_1A_1T_0R+0x28/0x4e

Would be glad if anybody has an idea, even if it is only how to proceed.

BR,
Carsten.

Attachment: putty.log
Description: Binary data

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