* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-23 21:25 Boris Derzhavets
2010-04-23 21:35 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-23 21:25 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 2043 bytes --]
I've sent you dmesg output twice (as attachment) and it matches serial log trace log. It's attached to this message also. Serial log was sent to Yu Ke per
his request, that messade was cc'd to you and Jeremy as well.
What you mean as a console log ?
File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
but i was unable to find
"CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
Should i just add it :-
CONFIG_ACPI_DEBUG_FUNC_TRACE=y
Sorry to bother you too much. It's not production, it's development box
and testing box. If i would not be on the bench in meantime, i would just
replace board for ASUS P5Q3 and that's it.
Thank you.
Boris.
--- On Fri, 4/23/10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 4:16 PM
On Fri, Apr 23, 2010 at 06:50:06AM -0700, Boris Derzhavets wrote:
> Here it goes.
>
> Grub entry
>
> menuentry "Xen 4 / Ubuntu 9.10 kernel 2.6.32.10" {
> insmod ext2
> set root=(hd1,1)
> multiboot (hd1,1)/boot/xen.gz
> module (hd1,1)/boot/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb1 ro console=tty0 acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug
> module (hd1,1)/boot/initrd-2.6.32.10.img
> }
>
Where is the console output? Boris, you have to understand I can't help you
with debugging this out without some notion of what is going on.
Please send me the console output (and do have the CONFIG_ACPI_DEBUG=y,
CONFIG_ACPI_DEBUG_FUNC_TRACE=y set), or the motherboard.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2768 bytes --]
[-- Attachment #2: dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 18349 bytes --]
[-- Attachment #3: config.2.6.10-P5Q-E.gz --]
[-- Type: application/x-gzip, Size: 25686 bytes --]
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 21:25 Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log) Boris Derzhavets
@ 2010-04-23 21:35 ` Konrad Rzeszutek Wilk
2010-04-24 2:09 ` Yu, Ke
0 siblings, 1 reply; 22+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-04-23 21:35 UTC (permalink / raw)
To: Boris Derzhavets
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> I've sent you dmesg output twice (as attachment) and it matches serial log trace log. It's attached to this message also. Serial log was sent to Yu Ke per
> his request, that messade was cc'd to you and Jeremy as well.
You are right. I completly failed to see it. Thank you for sending it
and sorry about the duplicate request.
>
> What you mean as a console log ?
Serial log or anything that has a stack trace of the problem. The
attachment you sent contains that, so that is good.
The bug looks to be:
calling acpi_processor_init+0x0/0x136 [processor] @ 812
ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012 INTL 20060113)
BUG: unable to handle kernel paging request at ffffc900117e0000
IP: [<ffffffff81287f28>] acpi_ex_system_memory_space_handler+0x21e/0x2ba
PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
CPU 1
Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>] acpi_ex_system_memory_space_handler+0x21e/0x2ba
RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
FS: 00007f62694606f0(0000) GS:ffff880028055000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task ffff8801e1b74700)
Stack:
0000000000000008 ffff880100000000 ffff880100000000 ffff880180000000
<0> 0000000000000000 0000000000000000 ffff8801dd34b8a8 ffff8801e573a780
<0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000 ffffffff81287d0a
Call Trace:
[<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
[<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
[<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
[<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
[<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
[<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
[<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
[<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
[<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
[<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
[<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
[<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
[<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
[<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
[<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
[<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
[<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
[<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
[<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
[<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
[<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
[<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
[<ffffffff8136058f>] __driver_attach+0x5d/0x81
[<ffffffff81360532>] ? __driver_attach+0x0/0x81
[<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
[<ffffffff813601b1>] driver_attach+0x1e/0x20
[<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
[<ffffffff8136087c>] driver_register+0x9d/0x10e
[<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
[<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
[<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
[<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
[<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
[<ffffffff8100a069>] do_one_initcall+0x5e/0x159
[<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
[<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83 ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24 eb 15 41 0f b7 04 24
udev: renamed network interface eth1 to eth2
eb 0e 45 8b 24 24 4d 89 65
RIP [<ffffffff81287f28>] acpi_ex_system_memory_space_handler+0x21e/0x2ba
RSP <ffff8801dd34b858>
CR2: ffffc900117e0000
---[ end trace 9f4c43facc7b61c1 ]---
>
> File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> but i was unable to find
> "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> Should i just add it :-
> CONFIG_ACPI_DEBUG_FUNC_TRACE=y
The kernel looks to have those config options built-in.?
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 21:35 ` Konrad Rzeszutek Wilk
@ 2010-04-24 2:09 ` Yu, Ke
2010-04-24 13:07 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Yu, Ke @ 2010-04-24 2:09 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Boris Derzhavets
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-24 2:09 ` Yu, Ke
@ 2010-04-24 13:07 ` Boris Derzhavets
2010-04-26 9:32 ` Yu, Ke
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-24 13:07 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, KeYu
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 15579 bytes --]
First dump obtained in previous message.
Second dump re-executed ( there was mistake at first run - 0x cff7e350 ):-
root@ServerLucid:~# acpidump --addr 0xcff7e350 --length 0x277 --binary --output ssdt2.dat
root@ServerLucid:~# iasl -d ssdt2.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt2.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "ssdt2.dsl"
root@ServerLucid:~# cat ssdt2.dsl
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt2.dat, Sat Apr 24 17:04:06 2010
*
*
* Original Table Header:
* Signature "SSDT"
* Length 0x00000277 (631)
* Revision 0x01
* Checksum 0x97
* OEM ID "DpgPmm"
* OEM Table ID "P002Ist"
* OEM Revision 0x00000012 (18)
* Compiler ID "INTL"
* Compiler Version 0x20060113 (537264403)
*/
DefinitionBlock ("ssdt2.aml", "SSDT", 1, "DpgPmm", "P002Ist", 0x00000012)
{
External (NCPU)
External (NPCP, IntObj)
External (PDC1)
External (CFGD)
External (\_PR_.P002, DeviceObj)
Scope (\_PR.P002)
{
Method (_PPC, 0, NotSerialized)
{
Return (Zero)
}
Method (_PCT, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
},
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
}
})
}
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000900, // Address
,)
},
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000902, // Address
,)
}
})
}
Method (_PSD, 0, NotSerialized)
{
Name (DOMN, 0x00)
Name (CRTP, 0x00)
Name (NOPR, 0x00)
If (And (PDC1, 0x0800))
{
Store (0xFE, CRTP)
}
Else
{
Store (0xFC, CRTP)
}
Divide (0x02, NPCP, Local1, Local2)
If (LEqual (Local1, 0x00))
{
Store (NPCP, Local1)
}
Decrement (Local1)
Store (Local1, DOMN)
Divide (NCPU, NPCP, Local2, Local3)
Store (Local3, NOPR)
Return (Package (0x01)
{
Package (0x05)
{
0x05,
0x00,
DOMN,
CRTP,
NOPR
}
})
}
Method (_PSS, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (NPSS)
}
Return (SPSS)
}
Name (SPSS, Package (0x04)
{
Package (0x06)
{
0x00000BB8,
0x00015BA8,
0x000000A0,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6B,
0x00013880,
0x000000A0,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x0000091D,
0x00011940,
0x000000A0,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D0,
0x0000FDE8,
0x000000A0,
0x0000000A,
0x0000061A,
0x0000061A
}
})
Name (NPSS, Package (0x04)
{
Package (0x06)
{
0x00000BBB,
0x00015BA8,
0x0000000A,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6E,
0x00013880,
0x0000000A,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x00000920,
0x00011940,
0x0000000A,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D3,
0x0000FDE8,
0x0000000A,
0x0000000A,
0x0000061A,
0x0000061A
}
})
}
}
--- On Fri, 4/23/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 10:09 PM
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 33569 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-24 13:07 ` Boris Derzhavets
@ 2010-04-26 9:32 ` Yu, Ke
2010-04-26 10:44 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Yu, Ke @ 2010-04-26 9:32 UTC (permalink / raw)
To: Boris Derzhavets, Konrad Rzeszutek Wilk
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
Hi Boris,
Thanks for the info. Unluckily, the _PDC method is not in these two SSDT tables, so let's search more place for the _PDC method:
# acpidump > all.dat # dump all acpi binary data
# acpixtract all.dat # extract the DSDT, SSDT tables etc.
For each extracted table , please disassemble them:
# iasl -d xxxx.dat # e.g. iasl -d DSDT.dat
# grep "PDC" *.dsl #search _PDC in those disassemble files
If still no PDC is found, please search the "Load" command in those *.dsl files, usually the Load command has the following form:
OperationRegion (XXXX, SystemMemory, <address>, <length>)
Load(XXXX, handle)
Where XXXX indicates memory block of [address , address+length], in which _PDS is possibly in.
Then use acpidump to get those memory block:
# acpidump --addr <address> --length <length> --binary --output xxxx.dat
# iasl -d xxxx.dat
# grep "PDC" *.dsl # again find the _PDC"
Once find the _PDC, please send out the *.dsl files.
Best Regards
Ke
-----Original Message-----
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Saturday, April 24, 2010 9:08 PM
To: Konrad Rzeszutek Wilk; Yu, Ke
Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
First dump obtained in previous message.
Second dump re-executed ( there was mistake at first run - 0x cff7e350 ):-
root@ServerLucid:~# acpidump --addr 0xcff7e350 --length 0x277 --binary --output ssdt2.dat
root@ServerLucid:~# iasl -d ssdt2.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt2.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "ssdt2.dsl"
root@ServerLucid:~# cat ssdt2.dsl
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt2.dat, Sat Apr 24 17:04:06 2010
*
*
* Original Table Header:
* Signature "SSDT"
* Length 0x00000277 (631)
* Revision 0x01
* Checksum 0x97
* OEM ID "DpgPmm"
* OEM Table ID "P002Ist"
* OEM Revision 0x00000012 (18)
* Compiler ID "INTL"
* Compiler Version 0x20060113 (537264403)
*/
DefinitionBlock ("ssdt2.aml", "SSDT", 1, "DpgPmm", "P002Ist", 0x00000012)
{
External (NCPU)
External (NPCP, IntObj)
External (PDC1)
External (CFGD)
External (\_PR_.P002, DeviceObj)
Scope (\_PR.P002)
{
Method (_PPC, 0, NotSerialized)
{
Return (Zero)
}
Method (_PCT, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
},
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
}
})
}
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000900, // Address
,)
},
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000902, // Address
,)
}
})
}
Method (_PSD, 0, NotSerialized)
{
Name (DOMN, 0x00)
Name (CRTP, 0x00)
Name (NOPR, 0x00)
If (And (PDC1, 0x0800))
{
Store (0xFE, CRTP)
}
Else
{
Store (0xFC, CRTP)
}
Divide (0x02, NPCP, Local1, Local2)
If (LEqual (Local1, 0x00))
{
Store (NPCP, Local1)
}
Decrement (Local1)
Store (Local1, DOMN)
Divide (NCPU, NPCP, Local2, Local3)
Store (Local3, NOPR)
Return (Package (0x01)
{
Package (0x05)
{
0x05,
0x00,
DOMN,
CRTP,
NOPR
}
})
}
Method (_PSS, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (NPSS)
}
Return (SPSS)
}
Name (SPSS, Package (0x04)
{
Package (0x06)
{
0x00000BB8,
0x00015BA8,
0x000000A0,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6B,
0x00013880,
0x000000A0,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x0000091D,
0x00011940,
0x000000A0,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D0,
0x0000FDE8,
0x000000A0,
0x0000000A,
0x0000061A,
0x0000061A
}
})
Name (NPSS, Package (0x04)
{
Package (0x06)
{
0x00000BBB,
0x00015BA8,
0x0000000A,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6E,
0x00013880,
0x0000000A,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x00000920,
0x00011940,
0x0000000A,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D3,
0x0000FDE8,
0x0000000A,
0x0000000A,
0x0000061A,
0x0000061A
}
})
}
}
--- On Fri, 4/23/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 10:09 PM
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-26 9:32 ` Yu, Ke
@ 2010-04-26 10:44 ` Boris Derzhavets
0 siblings, 0 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-26 10:44 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, KeYu
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 17519 bytes --]
root@ServerKoala:~/acpi# acpidump > all.dat
Wrong checksum for OEMB
Wrong checksum for OEMB!
That is for start.
Boris.
--- On Mon, 4/26/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Monday, April 26, 2010, 5:32 AM
Hi Boris,
Thanks for the info. Unluckily, the _PDC method is not in these two SSDT tables, so let's search more place for the _PDC method:
# acpidump > all.dat # dump all acpi binary data
# acpixtract all.dat # extract the DSDT, SSDT tables etc.
For each extracted table , please disassemble them:
# iasl -d xxxx.dat # e.g. iasl -d DSDT.dat
# grep "PDC" *.dsl #search _PDC in those disassemble files
If still no PDC is found, please search the "Load" command in those *.dsl files, usually the Load command has the following form:
OperationRegion (XXXX, SystemMemory, <address>, <length>)
Load(XXXX, handle)
Where XXXX indicates memory block of [address , address+length], in which _PDS is possibly in.
Then use acpidump to get those memory block:
# acpidump --addr <address> --length <length> --binary --output xxxx.dat
# iasl -d xxxx.dat
# grep "PDC" *.dsl # again find the _PDC"
Once find the _PDC, please send out the *.dsl files.
Best Regards
Ke
-----Original Message-----
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Saturday, April 24, 2010 9:08 PM
To: Konrad Rzeszutek Wilk; Yu, Ke
Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
First dump obtained in previous message.
Second dump re-executed ( there was mistake at first run - 0x cff7e350 ):-
root@ServerLucid:~# acpidump --addr 0xcff7e350 --length 0x277 --binary --output ssdt2.dat
root@ServerLucid:~# iasl -d ssdt2.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt2.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "ssdt2.dsl"
root@ServerLucid:~# cat ssdt2.dsl
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt2.dat, Sat Apr 24 17:04:06 2010
*
*
* Original Table Header:
* Signature "SSDT"
* Length 0x00000277 (631)
* Revision 0x01
* Checksum 0x97
* OEM ID "DpgPmm"
* OEM Table ID "P002Ist"
* OEM Revision 0x00000012 (18)
* Compiler ID "INTL"
* Compiler Version 0x20060113 (537264403)
*/
DefinitionBlock ("ssdt2.aml", "SSDT", 1, "DpgPmm", "P002Ist", 0x00000012)
{
External (NCPU)
External (NPCP, IntObj)
External (PDC1)
External (CFGD)
External (\_PR_.P002, DeviceObj)
Scope (\_PR.P002)
{
Method (_PPC, 0, NotSerialized)
{
Return (Zero)
}
Method (_PCT, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
},
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
}
})
}
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000900, // Address
,)
},
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000902, // Address
,)
}
})
}
Method (_PSD, 0, NotSerialized)
{
Name (DOMN, 0x00)
Name (CRTP, 0x00)
Name (NOPR, 0x00)
If (And (PDC1, 0x0800))
{
Store (0xFE, CRTP)
}
Else
{
Store (0xFC, CRTP)
}
Divide (0x02, NPCP, Local1, Local2)
If (LEqual (Local1, 0x00))
{
Store (NPCP, Local1)
}
Decrement (Local1)
Store (Local1, DOMN)
Divide (NCPU, NPCP, Local2, Local3)
Store (Local3, NOPR)
Return (Package (0x01)
{
Package (0x05)
{
0x05,
0x00,
DOMN,
CRTP,
NOPR
}
})
}
Method (_PSS, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (NPSS)
}
Return (SPSS)
}
Name (SPSS, Package (0x04)
{
Package (0x06)
{
0x00000BB8,
0x00015BA8,
0x000000A0,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6B,
0x00013880,
0x000000A0,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x0000091D,
0x00011940,
0x000000A0,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D0,
0x0000FDE8,
0x000000A0,
0x0000000A,
0x0000061A,
0x0000061A
}
})
Name (NPSS, Package (0x04)
{
Package (0x06)
{
0x00000BBB,
0x00015BA8,
0x0000000A,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6E,
0x00013880,
0x0000000A,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x00000920,
0x00011940,
0x0000000A,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D3,
0x0000FDE8,
0x0000000A,
0x0000000A,
0x0000061A,
0x0000061A
}
})
}
}
--- On Fri, 4/23/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 10:09 PM
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 30562 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-26 10:50 Boris Derzhavets
0 siblings, 0 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-26 10:50 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, KeYu
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 21029 bytes --]
root@ServerKoala:~/acpi# acpixtract all.dat
Acpi table [DSDT] - 38462 bytes written to DSDT.dat
Acpi table [SSDT] - 2684 bytes written to SSDT.dat
root@ServerKoala:~/acpi# iasl -d DSDT.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file DSDT.dat
Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Parsing completed
Disassembly completed, written to "DSDT.dsl"
root@ServerKoala:~/acpi# iasl -d SSDT.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file SSDT.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "SSDT.dsl"
root@ServerKoala:~/acpi# ls -l
total 580
-rw-r--r-- 1 root root 196196 2010-04-26 14:42 all.dat
-rw-r--r-- 1 root root 38462 2010-04-26 14:44 DSDT.dat
-rw-r--r-- 1 root root 332331 2010-04-26 14:46 DSDT.dsl
-rw-r--r-- 1 root root 2684 2010-04-26 14:44 SSDT.dat
-rw-r--r-- 1 root root 14199 2010-04-26 14:46 SSDT.dsl
root@ServerKoala:~/acpi# vi DSDT.dsl
root@ServerKoala:~/acpi# grep "PDC" *.dsl
SSDT.dsl: Name (PDC0, 0x80000000)
SSDT.dsl: Name (PDC1, 0x80000000)
SSDT.dsl: Name (PDC2, 0x80000000)
SSDT.dsl: Name (PDC3, 0x80000000)
SSDT.dsl: Name (PDC4, 0x80000000)
SSDT.dsl: Name (PDC5, 0x80000000)
SSDT.dsl: Name (PDC6, 0x80000000)
SSDT.dsl: Name (PDC7, 0x80000000)
SSDT.dsl: Method (_PDC, 1, NotSerialized)
SSDT.dsl: Or (And (PDC0, 0x7FFFFFFF), CAP0, PDC0)
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC0, 0x09), 0x09), LEqual (
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC0, 0x18), 0x18), LEqual (
SSDT.dsl: Method (_PDC, 1, NotSerialized)
SSDT.dsl: Or (And (PDC1, 0x7FFFFFFF), CAP0, PDC1)
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC1, 0x09), 0x09), LEqual (
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC1, 0x18), 0x18), LEqual (
SSDT.dsl: Method (_PDC, 1, NotSerialized)
SSDT.dsl: Or (And (PDC2, 0x7FFFFFFF), CAP0, PDC2)
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC2, 0x09), 0x09), LEqual (
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC2, 0x18), 0x18), LEqual (
SSDT.dsl: Method (_PDC, 1, NotSerialized)
SSDT.dsl: Or (And (PDC3, 0x7FFFFFFF), CAP0, PDC3)
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC3, 0x09), 0x09), LEqual (
SSDT.dsl: If (LAnd (LAnd (LEqual (And (PDC3, 0x18), 0x18), LEqual (
Boris.
--- On Mon, 4/26/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Monday, April 26, 2010, 5:32 AM
Hi Boris,
Thanks for the info. Unluckily, the _PDC method is not in these two SSDT tables, so let's search more place for the _PDC method:
# acpidump > all.dat # dump all acpi binary data
# acpixtract all.dat # extract the DSDT, SSDT tables etc.
For each extracted table , please disassemble them:
# iasl -d xxxx.dat # e.g. iasl -d DSDT.dat
# grep "PDC" *.dsl #search _PDC in those disassemble files
If still no PDC is found, please search the "Load" command in those *.dsl files, usually the Load command has the following form:
OperationRegion (XXXX, SystemMemory, <address>, <length>)
Load(XXXX, handle)
Where XXXX indicates memory block of [address , address+length], in which _PDS is possibly in.
Then use acpidump to get those memory block:
# acpidump --addr <address> --length <length> --binary --output xxxx.dat
# iasl -d xxxx.dat
# grep "PDC" *.dsl # again find the _PDC"
Once find the _PDC, please send out the *.dsl files.
Best Regards
Ke
-----Original Message-----
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Saturday, April 24, 2010 9:08 PM
To: Konrad Rzeszutek Wilk; Yu, Ke
Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
First dump obtained in previous message.
Second dump re-executed ( there was mistake at first run - 0x cff7e350 ):-
root@ServerLucid:~# acpidump --addr 0xcff7e350 --length 0x277 --binary --output ssdt2.dat
root@ServerLucid:~# iasl -d ssdt2.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt2.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "ssdt2.dsl"
root@ServerLucid:~# cat ssdt2.dsl
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt2.dat, Sat Apr 24 17:04:06 2010
*
*
* Original Table Header:
* Signature "SSDT"
* Length 0x00000277 (631)
* Revision 0x01
* Checksum 0x97
* OEM ID "DpgPmm"
* OEM Table ID "P002Ist"
* OEM Revision 0x00000012 (18)
* Compiler ID "INTL"
* Compiler Version 0x20060113 (537264403)
*/
DefinitionBlock ("ssdt2.aml", "SSDT", 1, "DpgPmm", "P002Ist", 0x00000012)
{
External (NCPU)
External (NPCP, IntObj)
External (PDC1)
External (CFGD)
External (\_PR_.P002, DeviceObj)
Scope (\_PR.P002)
{
Method (_PPC, 0, NotSerialized)
{
Return (Zero)
}
Method (_PCT, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
},
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
}
})
}
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000900, // Address
,)
},
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000902, // Address
,)
}
})
}
Method (_PSD, 0, NotSerialized)
{
Name (DOMN, 0x00)
Name (CRTP, 0x00)
Name (NOPR, 0x00)
If (And (PDC1, 0x0800))
{
Store (0xFE, CRTP)
}
Else
{
Store (0xFC, CRTP)
}
Divide (0x02, NPCP, Local1, Local2)
If (LEqual (Local1, 0x00))
{
Store (NPCP, Local1)
}
Decrement (Local1)
Store (Local1, DOMN)
Divide (NCPU, NPCP, Local2, Local3)
Store (Local3, NOPR)
Return (Package (0x01)
{
Package (0x05)
{
0x05,
0x00,
DOMN,
CRTP,
NOPR
}
})
}
Method (_PSS, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC1,
0x09), 0x09)))
{
Return (NPSS)
}
Return (SPSS)
}
Name (SPSS, Package (0x04)
{
Package (0x06)
{
0x00000BB8,
0x00015BA8,
0x000000A0,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6B,
0x00013880,
0x000000A0,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x0000091D,
0x00011940,
0x000000A0,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D0,
0x0000FDE8,
0x000000A0,
0x0000000A,
0x0000061A,
0x0000061A
}
})
Name (NPSS, Package (0x04)
{
Package (0x06)
{
0x00000BBB,
0x00015BA8,
0x0000000A,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6E,
0x00013880,
0x0000000A,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x00000920,
0x00011940,
0x0000000A,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D3,
0x0000FDE8,
0x0000000A,
0x0000000A,
0x0000061A,
0x0000061A
}
})
}
}
--- On Fri, 4/23/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 10:09 PM
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 35317 bytes --]
[-- Attachment #2: DSDT.dsl.gz --]
[-- Type: application/x-gzip, Size: 30160 bytes --]
[-- Attachment #3: SSDT.dsl.gz --]
[-- Type: application/x-gzip, Size: 1650 bytes --]
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-24 7:29 Boris Derzhavets
0 siblings, 0 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-24 7:29 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, KeYu
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 10923 bytes --]
Done
apt-get install acpidump
root@ServerLucid:~# apt-get install acpidump
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
acpidump
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 16.5kB of archives.
After this operation, 94.2kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/universe acpidump 20071116-1 [16.5kB]
Fetched 16.5kB in 0s (27.8kB/s)
Selecting previously deselected package acpidump.
(Reading database ... 160357 files and directories currently installed.)
Unpacking acpidump (from .../acpidump_20071116-1_amd64.deb) ...
Processing triggers for man-db ...
Setting up acpidump (20071116-1) ...
root@ServerLucid:~# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
root@ServerLucid:~# iasl -d ssdt1.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt1.dat
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
......................
Parsing completed
Disassembly completed, written to "ssdt1.dsl"
root@ServerLucid:~# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
Wrong checksum for OEMB
Wrong checksum for OEMB!
root@ServerLucid:~# iasl -d ssdt2.dat
Intel ACPI Component Architecture
AML Disassembler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a
Loading Acpi table from file ssdt2.dat
Acpi Data Table [ ] decoded, written to "ssdt2.dsl"
Boris.
--- On Fri, 4/23/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 10:09 PM
It shows acpi_processor_set_pdc trying to access one BIOS memory or MMIO, but hypervisor fail to make the page mapping for this. But I still have no idea why this would happen.
When I try to find what the physical address is, I am a bit confused:
According to the src code
acpi_ex_system_memory_space_handler(u32 function,
acpi_physical_address address,
u32 bit_width,
acpi_integer * value,
void *handler_context, void *region_context)
and the asm code
000000000024be4e <acpi_ex_system_memory_space_handler>:
24be4e: 55 push %rbp
24be4f: 48 89 e5 mov %rsp,%rbp
24be52: 41 57 push %r15
24be54: 49 89 cf mov %rcx,%r15
24be57: 41 56 push %r14
24be59: 41 89 d6 mov %edx,%r14d
24be5c: 41 55 push %r13
24be5e: 4d 89 cd mov %r9,%r13
24be61: 41 54 push %r12
24be63: 49 89 f4 mov %rsi,%r12 <------ R12 preserve RSI
24be66: 53 push %rbx
24be67: 48 83 ec 08 sub $0x8,%rsp
24be6b: 83 fa 10 cmp $0x10,%edx
the R12 preserve the RSI value, which is the second parameter "acpi_physical_address address". However, the log shows R12=ffffc900117e0000 and it is more like a virtual address rather than a physical address.
or is it possible my asm code is different from Boris?
BTW, Boris, could you please also dump the ACPI SSDT table by:
# acpidump --addr 0xcff7e0d0 --length 0x277 --binary --output ssdt1.dat
# iasl -d ssdt1.dat # will generate ssdt1.asl
# acpidump --addr 0x cff7e350 --length 0x277 --binary --output ssdt2.dat
# iasl -d ssdt2.dat # will generate ssdt2.asl
And send out the ssdt1.asl and ssdt2.asl. in this case, we may be able to see which address the ACPI _PDC method want to access.
You can get iasl and acpidump from the following URL, in case you don't have it
acpidump: http://kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20100416.tar.gz
Iasl: http://www.acpica.org/downloads/
Best Regards
Ke
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Konrad Rzeszutek Wilk
> Sent: Saturday, April 24, 2010 5:36 AM
> To: Boris Derzhavets
> Cc: xen-devel@lists.xensource.com; Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ]
> Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10
> ( xen/stable) under Xen 4.0 on F12 (serial log)
>
> On Fri, Apr 23, 2010 at 02:25:04PM -0700, Boris Derzhavets wrote:
> > I've sent you dmesg output twice (as attachment) and it matches serial
> log trace log. It's attached to this message also. Serial log was sent to Yu Ke
> per
> > his request, that messade was cc'd to you and Jeremy as well.
>
> You are right. I completly failed to see it. Thank you for sending it
> and sorry about the duplicate request.
> >
> > What you mean as a console log ?
>
> Serial log or anything that has a stack trace of the problem. The
> attachment you sent contains that, so that is good.
>
> The bug looks to be:
>
> calling acpi_processor_init+0x0/0x136 [processor] @ 812
> ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011
> INTL 20060113)
> ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012
> INTL 20060113)
> BUG: unable to handle kernel paging request at ffffc900117e0000
> IP: [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> PGD 1f1887067 PUD 1f1888067 PMD 1e88e6067 PTE 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> /sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth2/type
> CPU 1
> Modules linked in: processor(+) soundcore snd_page_alloc acpi_processor
> asus_atk0110 fuse skge r8169 mii floppy sky2 thermal
> Pid: 812, comm: modprobe Not tainted 2.6.32.10 #7 P5Q-E
> RIP: e030:[<ffffffff81287f28>] [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP: e02b:ffff8801dd34b858 EFLAGS: 00010246
> RAX: 00000000ffffffff RBX: ffff8801e43b2bc0 RCX: ffffffff81524e20
> RDX: ffffffff81524ef0 RSI: 00000000000000ca RDI: 0000000000000004
> RBP: ffff8801dd34b8b8 R08: 0000000000000080 R09: ffffffff816b88f3
> R10: ffffffff816bc098 R11: 0000000000000001 R12: ffffc900117e0000
> R13: ffff8801dd34b9b0 R14: 0000000000000000 R15: 0000000000000008
> FS: 00007f62694606f0(0000) GS:ffff880028055000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffc900117e0000 CR3: 00000001e57e8000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process modprobe (pid: 812, threadinfo ffff8801dd34a000, task
> ffff8801e1b74700)
> Stack:
> 0000000000000008 ffff880100000000 ffff880100000000
> ffff880180000000
> <0> 0000000000000000 0000000000000000 ffff8801dd34b8a8
> ffff8801e573a780
> <0> ffff8801e9ee8348 ffff8801e573a7c8 0000000000000000
> ffffffff81287d0a
> Call Trace:
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff8127b3bd>] acpi_ev_address_space_dispatch+0x272/0x2e1
> [<ffffffff81287d0a>] ? acpi_ex_system_memory_space_handler+0x0/0x2ba
> [<ffffffff812807ac>] ? acpi_os_allocate+0x2a/0x2c
> [<ffffffff81280a00>] acpi_ex_load_op+0x140/0x4e8
> [<ffffffff81284d52>] acpi_ex_opcode_1A_1T_0R+0x5b/0xac
> [<ffffffff81275bc4>] acpi_ds_exec_end_op+0x138/0x64c
> [<ffffffff81296080>] acpi_ps_parse_loop+0xc6d/0xf49
> [<ffffffff81276ea4>] ? acpi_ds_call_control_method+0x339/0x34b
> [<ffffffff8129494c>] acpi_ps_parse_aml+0x167/0x483
> [<ffffffff8129facb>] ? acpi_ut_create_internal_object_dbg+0x10d/0x11c
> [<ffffffff81296dc2>] acpi_ps_execute_method+0x293/0x3dd
> [<ffffffff8129ba94>] ? acpi_ut_exit+0x36/0x3e
> [<ffffffff8128f8e6>] acpi_ns_evaluate+0x23a/0x3bb
> [<ffffffff8128ed37>] acpi_evaluate_object+0x1a7/0x309
> [<ffffffff8102688c>] ? init_intel_pdc+0x11f/0x20c
> [<ffffffffa005e0e0>] acpi_processor_set_pdc+0x46/0x7e [processor]
> [<ffffffffa0063cc3>] xen_acpi_processor_add+0x376/0x4c5 [processor]
> [<ffffffff811722d4>] ? sysfs_do_create_link+0xe9/0x13e
> [<ffffffff8126a479>] acpi_device_probe+0x50/0x18a
> [<ffffffff8117234e>] ? sysfs_create_link+0x13/0x15
> [<ffffffff81360412>] driver_probe_device+0xdb/0x1fb
> [<ffffffff8136058f>] __driver_attach+0x5d/0x81
> [<ffffffff81360532>] ? __driver_attach+0x0/0x81
> [<ffffffff8135f8d3>] bus_for_each_dev+0x53/0x88
> [<ffffffff813601b1>] driver_attach+0x1e/0x20
> [<ffffffff8135fdfe>] bus_add_driver+0xd5/0x23b
> [<ffffffff8136087c>] driver_register+0x9d/0x10e
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8126b01c>] acpi_bus_register_driver+0x43/0x45
> [<ffffffffa0061b70>] xen_acpi_processor_init+0x15/0x17 [processor]
> [<ffffffffa006c0b2>] acpi_processor_init+0xb2/0x136 [processor]
> [<ffffffffa006c000>] ? acpi_processor_init+0x0/0x136 [processor]
> [<ffffffff8100a069>] do_one_initcall+0x5e/0x159
> [<ffffffff8108ec0b>] sys_init_module+0xd6/0x237
> [<ffffffff81012cf2>] system_call_fastpath+0x16/0x1b
> Code: 00 00 00 eb 48 41 83 ff 10 49 c7 45 00 00 00 00 00 74 1f 77 08 41 83
> ff 08 75 77 eb 0e 41 83 ff 20 74 16 41 83 ff 40 75 69 eb 18 <41> 0f b6 04 24
> eb 15 41 0f b7 04 24
> udev: renamed network interface eth1 to eth2
> eb 0e 45 8b 24 24 4d 89 65
> RIP [<ffffffff81287f28>]
> acpi_ex_system_memory_space_handler+0x21e/0x2ba
> RSP <ffff8801dd34b858>
> CR2: ffffc900117e0000
> ---[ end trace 9f4c43facc7b61c1 ]---
>
> >
> > File ".config" of loaded 2.6.32.10 contained CONFIG_ACPI_DEBUG=y,
> > but i was unable to find
> > "CONFIG_ACPI_DEBUG_FUNC_TRACE not set".
> > Should i just add it :-
> > CONFIG_ACPI_DEBUG_FUNC_TRACE=y
>
> The kernel looks to have those config options built-in.?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 15250 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: ssdt1.dsl --]
[-- Type: text/x-dsl; name="ssdt1.dsl", Size: 5536 bytes --]
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt1.dat, Sat Apr 24 11:25:40 2010
*
*
* Original Table Header:
* Signature "SSDT"
* Length 0x00000277 (631)
* Revision 0x01
* Checksum 0x9E
* OEM ID "DpgPmm"
* OEM Table ID "P001Ist"
* OEM Revision 0x00000011 (17)
* Compiler ID "INTL"
* Compiler Version 0x20060113 (537264403)
*/
DefinitionBlock ("ssdt1.aml", "SSDT", 1, "DpgPmm", "P001Ist", 0x00000011)
{
External (NCPU)
External (NPCP, IntObj)
External (PDC0)
External (CFGD)
External (\_PR_.P001, DeviceObj)
Scope (\_PR.P001)
{
Method (_PPC, 0, NotSerialized)
{
Return (Zero)
}
Method (_PCT, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC0,
0x09), 0x09)))
{
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
},
ResourceTemplate ()
{
Register (FFixedHW,
0x00, // Bit Width
0x00, // Bit Offset
0x0000000000000000, // Address
,)
}
})
}
Return (Package (0x02)
{
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000900, // Address
,)
},
ResourceTemplate ()
{
Register (SystemIO,
0x10, // Bit Width
0x00, // Bit Offset
0x0000000000000902, // Address
,)
}
})
}
Method (_PSD, 0, NotSerialized)
{
Name (DOMN, 0x00)
Name (CRTP, 0x00)
Name (NOPR, 0x00)
If (And (PDC0, 0x0800))
{
Store (0xFE, CRTP)
}
Else
{
Store (0xFC, CRTP)
}
Divide (0x01, NPCP, Local1, Local2)
If (LEqual (Local1, 0x00))
{
Store (NPCP, Local1)
}
Decrement (Local1)
Store (Local1, DOMN)
Divide (NCPU, NPCP, Local2, Local3)
Store (Local3, NOPR)
Return (Package (0x01)
{
Package (0x05)
{
0x05,
0x00,
DOMN,
CRTP,
NOPR
}
})
}
Method (_PSS, 0, NotSerialized)
{
If (LAnd (LNot (And (CFGD, 0x4000)), LEqual (And (PDC0,
0x09), 0x09)))
{
Return (NPSS)
}
Return (SPSS)
}
Name (SPSS, Package (0x04)
{
Package (0x06)
{
0x00000BB8,
0x00015BA8,
0x000000A0,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6B,
0x00013880,
0x000000A0,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x0000091D,
0x00011940,
0x000000A0,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D0,
0x0000FDE8,
0x000000A0,
0x0000000A,
0x0000061A,
0x0000061A
}
})
Name (NPSS, Package (0x04)
{
Package (0x06)
{
0x00000BBB,
0x00015BA8,
0x0000000A,
0x0000000A,
0x00000920,
0x00000920
},
Package (0x06)
{
0x00000A6E,
0x00013880,
0x0000000A,
0x0000000A,
0x0000081E,
0x0000081E
},
Package (0x06)
{
0x00000920,
0x00011940,
0x0000000A,
0x0000000A,
0x0000071C,
0x0000071C
},
Package (0x06)
{
0x000007D3,
0x0000FDE8,
0x0000000A,
0x0000000A,
0x0000061A,
0x0000061A
}
})
}
}
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: ssdt2.dsl --]
[-- Type: text/x-dsl; name="ssdt2.dsl", Size: 305 bytes --]
/*
* Intel ACPI Component Architecture
* AML Disassembler version 20090521
*
* Disassembly of ssdt2.dat, Sat Apr 24 11:26:30 2010
*
* ACPI Data Table [ ]
*
* Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue
*/
**** ACPI table terminates in the middle of a data structure!
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 13:50 Boris Derzhavets
@ 2010-04-23 20:16 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 22+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-04-23 20:16 UTC (permalink / raw)
To: Boris Derzhavets
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
On Fri, Apr 23, 2010 at 06:50:06AM -0700, Boris Derzhavets wrote:
> Here it goes.
>
> Grub entry
>
> menuentry "Xen 4 / Ubuntu 9.10 kernel 2.6.32.10" {
> insmod ext2
> set root=(hd1,1)
> multiboot (hd1,1)/boot/xen.gz
> module (hd1,1)/boot/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb1 ro console=tty0 acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug
> module (hd1,1)/boot/initrd-2.6.32.10.img
> }
>
Where is the console output? Boris, you have to understand I can't help you
with debugging this out without some notion of what is going on.
Please send me the console output (and do have the CONFIG_ACPI_DEBUG=y,
CONFIG_ACPI_DEBUG_FUNC_TRACE=y set), or the motherboard.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-23 13:50 Boris Derzhavets
2010-04-23 20:16 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-23 13:50 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
[-- Attachment #1.1: Type: text/plain, Size: 1491 bytes --]
Here it goes.
Grub entry
menuentry "Xen 4 / Ubuntu 9.10 kernel 2.6.32.10" {
insmod ext2
set root=(hd1,1)
multiboot (hd1,1)/boot/xen.gz
module (hd1,1)/boot/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb1 ro console=tty0 acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug
module (hd1,1)/boot/initrd-2.6.32.10.img
}
Boris.
--- On Fri, 4/23/10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Date: Friday, April 23, 2010, 9:32 AM
On Fri, Apr 23, 2010 at 03:45:31AM -0700, Boris Derzhavets wrote:
> Mark,
> Thanks for instructions.
>
> root@ServerKoala:~# modprobe acpi-processor
> root@ServerKoala:~# modprobe processor
> ^C
>
> Second command hangs, first one comes back to command prompt cleanly.
Now send me your console output. You should have gotten a wealth of them
(you did compile your kernel with the debug option I asked, right?), and
also added the acpi.. debug option in the Linux kernel command line.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2093 bytes --]
[-- Attachment #2: dmesg.out.gz --]
[-- Type: application/x-gzip, Size: 18349 bytes --]
[-- Attachment #3: config.2.6.10-P5Q-E.gz --]
[-- Type: application/x-gzip, Size: 25686 bytes --]
[-- Attachment #4: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 10:45 ` Boris Derzhavets
2010-04-23 10:59 ` Boris Derzhavets
@ 2010-04-23 13:32 ` Konrad Rzeszutek Wilk
1 sibling, 0 replies; 22+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-04-23 13:32 UTC (permalink / raw)
To: Boris Derzhavets
Cc: xen-devel, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
On Fri, Apr 23, 2010 at 03:45:31AM -0700, Boris Derzhavets wrote:
> Mark,
> Thanks for instructions.
>
> root@ServerKoala:~# modprobe acpi-processor
> root@ServerKoala:~# modprobe processor
> ^C
>
> Second command hangs, first one comes back to command prompt cleanly.
Now send me your console output. You should have gotten a wealth of them
(you did compile your kernel with the debug option I asked, right?), and
also added the acpi.. debug option in the Linux kernel command line.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 10:45 ` Boris Derzhavets
@ 2010-04-23 10:59 ` Boris Derzhavets
2010-04-23 13:32 ` Konrad Rzeszutek Wilk
1 sibling, 0 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-23 10:59 UTC (permalink / raw)
To: Marc - A. Dahlhaus [ Administration | Westermann GmbH ]; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1991 bytes --]
root@ServerKoala:~# /sbin/lsmod |grep acpi
acpi_processor 5621 1 processor,[permanent]
Boris.
--- On Fri, 4/23/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Friday, April 23, 2010, 6:45 AM
Mark,
Thanks for instructions.
root@ServerKoala:~# modprobe acpi-processor
root@ServerKoala:~# modprobe processor
^C
Second command hangs, first one comes back to command prompt cleanly.
Boris.
--- On Fri, 4/23/10, Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de> wrote:
From: Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Friday, April 23, 2010, 5:12 AM
Am
Freitag, den 23.04.2010, 00:58 -0700 schrieb Boris Derzhavets:
> root@ServerKoala:~# modprobe acpi_processor.ko
> FATAL: Module acpi_processor.ko not found.
> root@ServerKoala:~# modprobe processor.ko
> FATAL: Module processor.ko not found.
Please replace the _ with - and remove the .ko when you try to load
modules without giving the full path to the file:
modprobe acpi-processor
modprobe processor
Marc
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 3271 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 9:12 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
@ 2010-04-23 10:45 ` Boris Derzhavets
2010-04-23 10:59 ` Boris Derzhavets
2010-04-23 13:32 ` Konrad Rzeszutek Wilk
0 siblings, 2 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-23 10:45 UTC (permalink / raw)
To: Marc - A. Dahlhaus [ Administration | Westermann GmbH ]; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1211 bytes --]
Mark,
Thanks for instructions.
root@ServerKoala:~# modprobe acpi-processor
root@ServerKoala:~# modprobe processor
^C
Second command hangs, first one comes back to command prompt cleanly.
Boris.
--- On Fri, 4/23/10, Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de> wrote:
From: Marc - A. Dahlhaus [ Administration | Westermann GmbH ] <mad@wol.de>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Date: Friday, April 23, 2010, 5:12 AM
Am Freitag, den 23.04.2010, 00:58 -0700 schrieb Boris Derzhavets:
> root@ServerKoala:~# modprobe acpi_processor.ko
> FATAL: Module acpi_processor.ko not found.
> root@ServerKoala:~# modprobe processor.ko
> FATAL: Module processor.ko not found.
Please replace the _ with - and remove the .ko when you try to load
modules without giving the full path to the file:
modprobe acpi-processor
modprobe processor
Marc
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 1815 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-23 7:58 Boris Derzhavets
@ 2010-04-23 9:12 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2010-04-23 10:45 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Marc - A. Dahlhaus [ Administration | Westermann GmbH ] @ 2010-04-23 9:12 UTC (permalink / raw)
To: Boris Derzhavets; +Cc: xen-devel
Am Freitag, den 23.04.2010, 00:58 -0700 schrieb Boris Derzhavets:
> root@ServerKoala:~# modprobe acpi_processor.ko
> FATAL: Module acpi_processor.ko not found.
> root@ServerKoala:~# modprobe processor.ko
> FATAL: Module processor.ko not found.
Please replace the _ with - and remove the .ko when you try to load
modules without giving the full path to the file:
modprobe acpi-processor
modprobe processor
Marc
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-23 7:58 Boris Derzhavets
2010-04-23 9:12 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-23 7:58 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: Jeremy Fitzhardinge, xen-devel, KeYu
[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]
root@ServerKoala:~# modprobe acpi_processor.ko
FATAL: Module acpi_processor.ko not found.
root@ServerKoala:~# modprobe processor.ko
FATAL: Module processor.ko not found.
However,
root@ServerKoala:~# find /lib/modules/2.6.32.10 -name "*processor.ko" -print
/lib/modules/2.6.32.10/kernel/drivers/xen/acpi_processor.ko
/lib/modules/2.6.32.10/kernel/drivers/acpi/processor.ko
dmesg report is attached.
Boris
--- On Thu, 4/22/10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "KeYu" <ke.yu@intel.com>
Date: Thursday, April 22, 2010, 5:09 PM
On Thu, Apr 22, 2010 at 01:32:02PM -0700, Boris Derzhavets wrote:
> Not sure which one of those :-
>
> LD [M] drivers/acpi/processor.ko
> LD [M] drivers/xen/acpi_processor.ko
Do both then.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 1830 bytes --]
[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/x-gzip, Size: 18354 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-22 20:32 ` Boris Derzhavets
@ 2010-04-22 21:09 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 22+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-04-22 21:09 UTC (permalink / raw)
To: Boris Derzhavets; +Cc: Jeremy Fitzhardinge, xen-devel, KeYu
On Thu, Apr 22, 2010 at 01:32:02PM -0700, Boris Derzhavets wrote:
> Not sure which one of those :-
>
> LD [M] drivers/acpi/processor.ko
> LD [M] drivers/xen/acpi_processor.ko
Do both then.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-22 19:23 ` Konrad Rzeszutek Wilk
@ 2010-04-22 20:32 ` Boris Derzhavets
2010-04-22 21:09 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-22 20:32 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: Jeremy Fitzhardinge, xen-devel, KeYu
[-- Attachment #1.1: Type: text/plain, Size: 2800 bytes --]
Not sure which one of those :-
LD [M] drivers/acpi/processor.ko
LD [M] drivers/xen/acpi_processor.ko
I believe second one causes issue under Xen 4.0 Hypervisor
Boris
--- On Thu, 4/22/10, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "KeYu" <ke.yu@intel.com>
Date: Thursday, April 22, 2010, 3:23 PM
On Thu, Apr 22, 2010 at 09:56:44AM -0700, Boris Derzhavets wrote:
> Disabling option <> processor allows to load 2.6.32.10 on ASUS P5Q-E :-
>
> [*] Power management and ACPI options --->
> [*] ACPI (Advanced Configuration and Power Interface) Support --->
> [*] Deprecated /proc/acpi files
> [*] Deprecated power /proc/acpi directories
> < > ACPI 4.0 power meter
> [*] Future power /sys interface
> [*] Deprecated /proc/acpi/event support
> <*> AC Adapter
> <*> Battery
> <*> Button
> <M> Video
> <*> Fan
> -*- Dock
> -> < > Processor
Can you make that be a module instead? And when the machine has booted
up, try to load the module (you might need to rename the modele to say
processor.ko.old so that udev won't automatically load it)?
And also compile the kernel with CONFIG_ACPI_DEBUG=y and
CONFIG_ACPI_DEBUG_FUNC_TRACE=y
Lastly, when you boot your machine, please add these flags
to your Linux kernel command line:
acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 8200 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-22 16:56 Boris Derzhavets
@ 2010-04-22 19:23 ` Konrad Rzeszutek Wilk
2010-04-22 20:32 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Konrad Rzeszutek Wilk @ 2010-04-22 19:23 UTC (permalink / raw)
To: Boris Derzhavets; +Cc: Jeremy Fitzhardinge, xen-devel, KeYu
On Thu, Apr 22, 2010 at 09:56:44AM -0700, Boris Derzhavets wrote:
> Disabling option <> processor allows to load 2.6.32.10 on ASUS P5Q-E :-
>
> [*] Power management and ACPI options --->
> [*] ACPI (Advanced Configuration and Power Interface) Support --->
> [*] Deprecated /proc/acpi files
> [*] Deprecated power /proc/acpi directories
> < > ACPI 4.0 power meter
> [*] Future power /sys interface
> [*] Deprecated /proc/acpi/event support
> <*> AC Adapter
> <*> Battery
> <*> Button
> <M> Video
> <*> Fan
> -*- Dock
> -> < > Processor
Can you make that be a module instead? And when the machine has booted
up, try to load the module (you might need to rename the modele to say
processor.ko.old so that udev won't automatically load it)?
And also compile the kernel with CONFIG_ACPI_DEBUG=y and
CONFIG_ACPI_DEBUG_FUNC_TRACE=y
Lastly, when you boot your machine, please add these flags
to your Linux kernel command line:
acpi.debug_level=0xffffffff acpi.debug_layer=0x2 initcall_debug
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-22 16:56 Boris Derzhavets
2010-04-22 19:23 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-22 16:56 UTC (permalink / raw)
To: KeYu; +Cc: Jeremy Fitzhardinge, xen-devel, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 11731 bytes --]
Disabling option <> processor allows to load 2.6.32.10 on ASUS P5Q-E :-
[*] Power management and ACPI options --->
[*] ACPI (Advanced Configuration and Power Interface) Support --->
[*] Deprecated /proc/acpi files
[*] Deprecated power /proc/acpi directories
< > ACPI 4.0 power meter
[*] Future power /sys interface
[*] Deprecated /proc/acpi/event support
<*> AC Adapter
<*> Battery
<*> Button
<M> Video
<*> Fan
-*- Dock
-> < > Processor
-*- NUMA support
[ ] Debug Statements
<*> PCI slot detection driver
<*> Container and Module Devices
<M> Smart Battery System
dmesg reports :-
ACPI: RSDP 00000000000fb030 00024 (v02 ACPIAM)
ACPI: XSDT 00000000cff70100 0005C (v01 A_M_I_ OEMXSDT 07000809 MSFT 00000097)
ACPI: FACP 00000000cff70290 000F4 (v03 A_M_I_ OEMFACP 07000809 MSFT 00000097)
ACPI: DSDT 00000000cff70440 0963E (v01 A0986 A0986000 00000000 INTL 20060113)
ACPI: FACS 00000000cff7e000 00040
ACPI: APIC 00000000cff70390 0006C (v01 A_M_I_ OEMAPIC 07000809 MSFT 00000097)
ACPI: MCFG 00000000cff70400 0003C (v01 A_M_I_ OEMMCFG 07000809 MSFT 00000097)
ACPI: OEMB 00000000cff7e040 00081 (v01 A_M_I_ AMI_OEM 07000809 MSFT 00000097)
ACPI: HPET 00000000cff79a80 00038 (v01 A_M_I_ OEMHPET 07000809 MSFT 00000097)
ACPI: OSFR 00000000cff79ac0 000B0 (v01 A_M_I_ OEMOSFR 07000809 MSFT 00000097)
ACPI: SSDT 00000000cff7e5d0 00A7C (v01 DpgPmm CpuPm 00000012 INTL 20060113)
ACPI: Local APIC address 0xfee00000
No NUMA configuration found
Faking a node at 0000000000000000-00000001f1f47000
Bootmem setup node 0 0000000000000000-00000001f1f47000
NODE_DATA [0000000000010000 - 0000000000025fff]
bootmap [0000000000026000 - 00000000000643ef] pages 3f
(9 early reservations) ==> bootmem [0000000000 - 01f1f47000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [000e4c9000 - 000e540000] XEN PAGETABLES ==> [000e4c9000 - 000e540000]
#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#3 [0001000000 - 0001b34788] TEXT DATA BSS ==> [0001000000 - 0001b34788]
#4 [0001b55000 - 000d537e00] RAMDISK ==> [0001b55000 - 000d537e00]
#5 [000d538000 - 000e4c9000] XEN START INFO ==> [000d538000 - 000e4c9000]
#6 [0001b35000 - 0001b35280] BRK ==> [0001b35000 - 0001b35280]
#7 [0000100000 - 000070b000] PGTABLE ==> [0000100000 - 000070b000]
#8 [000e540000 - 000ecd4000] PGTABLE ==> [000e540000 - 000ecd4000]
Boris.
--- On Thu, 4/22/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, April 22, 2010, 7:32 AM
On ASIS P5Q3 :-
[ 0.403515] ACPI: SSDT 00000000cfe7e0d0 00235 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
[ 0.405055] ACPI: SSDT 00000000cfe7e310 00235 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
[ 0.406589] ACPI: SSDT 00000000cfe7e550 00235 (v01 DpgPmm P003Ist 00000012 INTL 20051117)
[ 0.409424] ACPI: SSDT 00000000cfe7e790 00235 (v01 DpgPmm P004Ist 00000012 INTL 20051117)
[ 0.414290] Event-channel device installed.
[ 0.414339] pciback: pcistub_init_devices_late
On ASUS P5Q-E right after SSDT lines issue raises up. It happens on regular
basis at Xen 4.0 Dom0 on top of F12 and Ubuntu 9.10 Server, located on
different drives and dual booting on the same box.
[ 14.275834]
ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 14.375923] ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012 INTL 20060113)
(XEN) mm.c:859:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 8000000080000473 for l1e_owner=0, pg_owner=32753
[ 14.484819] BUG: unable to handle kernel paging request at ffffc9000003a000
Boris
--- On Thu, 4/22/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com"
<xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, April 22, 2010, 5:58 AM
Why it happens on ASUS P5Q-E ( 8 GB DDR2 Kingston) and doesn't on ASUS P5Q3 ( 8 GB DDR3 Kingston) ?
(XEN) mm.c:859:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 8000000080000473 for l1e_owner=0, pg_owner=32753
[ 14.484819] BUG: unable to handle kernel paging request at ffffc9000003a000
[ 14.484819] IP: [<ffffffff812aba22>] acpi_ex_system_memory_space_handler+0x16d/0x1df
[ 14.484819] PGD 3f86b067 PUD 3f86c067
PMD 3f86d067 PTE 0
[ 14.484819] Oops: 0000 [#1] SMP
[ 14.484819] last sysfs file:
[ 14.484819] CPU 0
[ 14.484819] Modules linked in:
[ 14.484819] Pid: 1, comm: swapper Not tainted 2.6.32.11 #5 P5Q-E
Boris.
--- On Wed, 4/21/10, Boris Derzhavets
<bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, April 21, 2010, 9:25 AM
Serial log for 2.6.32.11 loading under Xen 4.0 on top of
Fedora 12 (ASUS P5Q-E)
Boris.
--- On Wed, 4/21/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@goop.org>
Date: Wednesday, April 21, 2010, 4:05 AM
Yes, it would be helpful if you can provide more complete serial console log. From the below log, I can see
acpi_processor_set_pdc-> acpi_evaluate_object(pr->handle, "_PDC", pdc_in, NULL) cause the system panic. However, it cannot tell why _PDC evaluation cause panic. It may be BIOS issue as you suggested, but we need more log to decide if this is true. And if true, ASUS should be the right place to get updated BIOS.
Also, how is the 2.6.32.11 kernel working in bare mental environment? acpi_processor_set_pdc is not xen specific code, so this issue is likely also occurring in bare mental environment.
And according to your test result, 2.6.32.9 works while 2.6.32.10 not. This remind me change we made recently made, i.e. "re-enable mwait for xen cpuidle", I am not sure if this cause the panic. So could you please try the grub kernel option "idle=nomwait"? This option will revert the effect of that patch. If "idle=nomwait" works, then we can dig more in this direction.
Best
Regards
Ke
===============================
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Wednesday, April 21, 2010 5:26 AM
To: Yu, Ke
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com; Yu, Ke; Jeremy Fitzhardinge
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
If it would not help, i will set up serial console ( a bit painful for me to move boxes )
Tail of sreen output on ASUS P5Q-E +C2D E8400 for 2.6.32.11 kernel :-
acpi_processor_set_pdc + 0x3c/0x3e
xen_acpi_processor_add + 0x2ef/0x426
acpi_device_probe + 0x4b/0x11d
driver_probe_device + 0x86/0x180
__diver_attach + 0x86/0x180
__diver_attach +
0x86/0xa0
bus_for_each_dev 0x64/0x90
driver_attach + 0x71/0x140
bus_add_driver + 0x3e/0x140
driver_register + 0x71/0x140
?acpi_processor_init 0x3e/0x140
?acpi_processor_init 0x71/0x140
acpi_bus_register_driver +0x3e/0x12
xen_acpi_processor_init 0xae/0x128
acpi_processor_init + 0x3e/0x12
? acpi_pci_slot_init 0x0/0x20
? acpi_pci_slot_init 0x0/0x20
do_one_init_call + 0x37/0x1xa0
kernel_init 0x148/0x196
child_rip + 0xa/0x20
? init_ret_from_sys_call 0x7/0x16
? retint_restore_args 0x5/0x5
? child_rip 0x0/0x20
Screen output stopped.
Thanks.
Boris.
P.S. Nothing similar happens on ASUS P5Q3 + Q9550
Dom0 loads smoothly. Tested on F12 and Ubuntu 9.10.
Same picture.
--- On Tue, 4/20/10, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Failure to
load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Yu, Ke" <ke.yu@intel.com>
Date: Tuesday, April 20, 2010, 2:21 PM
On
04/20/2010 03:44 AM, Boris Derzhavets wrote:
> ASUS P5Q-E 2.6.31.13 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.9 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.10 under Xen 4.0 doesn't load
>
> ASUS P5Q3 all kernels work fine
>
> I believe that the issue is connected with outdated ( ACPI 2 Enabled) BIOS
> on first board. This question is mostly addressed to Yu Ke. What BIOS
> upgrade is required (exact version) , if ever possible.
>
It would probably help him if you 1. address your mail to him, and 2.
provide more specific information about what the failure is, beyond
``Before child_rip word "acpi" shows pretty often. In particular
"acpi_xen_processor"''.
J
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 21692 bytes --]
[-- Attachment #2: dmesg.2.6.32.10.gz --]
[-- Type: application/x-gzip, Size: 11084 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-22 9:58 ` Boris Derzhavets
@ 2010-04-22 11:32 ` Boris Derzhavets
0 siblings, 0 replies; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-22 11:32 UTC (permalink / raw)
To: KeYu; +Cc: Jeremy Fitzhardinge, xen-devel, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 7298 bytes --]
On ASIS P5Q3 :-
[ 0.403515] ACPI: SSDT 00000000cfe7e0d0 00235 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
[ 0.405055] ACPI: SSDT 00000000cfe7e310 00235 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
[ 0.406589] ACPI: SSDT 00000000cfe7e550 00235 (v01 DpgPmm P003Ist 00000012 INTL 20051117)
[ 0.409424] ACPI: SSDT 00000000cfe7e790 00235 (v01 DpgPmm P004Ist 00000012 INTL 20051117)
[ 0.414290] Event-channel device installed.
[ 0.414339] pciback: pcistub_init_devices_late
On ASUS P5Q-E right after SSDT lines issue raises up. It happens on regular
basis at Xen 4.0 Dom0 on top of F12 and Ubuntu 9.10 Server, located on
different drives and dual booting on the same box.
[ 14.275834] ACPI: SSDT 00000000cff7e0d0 00277 (v01 DpgPmm P001Ist 00000011 INTL 20060113)
[ 14.375923] ACPI: SSDT 00000000cff7e350 00277 (v01 DpgPmm P002Ist 00000012 INTL 20060113)
(XEN) mm.c:859:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 8000000080000473 for l1e_owner=0, pg_owner=32753
[ 14.484819] BUG: unable to handle kernel paging request at ffffc9000003a000
Boris
--- On Thu, 4/22/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Thursday, April 22, 2010, 5:58 AM
Why it happens on ASUS P5Q-E ( 8 GB DDR2 Kingston) and doesn't on ASUS P5Q3 ( 8 GB DDR3 Kingston) ?
(XEN) mm.c:859:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 8000000080000473 for l1e_owner=0, pg_owner=32753
[ 14.484819] BUG: unable to handle kernel paging request at ffffc9000003a000
[ 14.484819] IP: [<ffffffff812aba22>] acpi_ex_system_memory_space_handler+0x16d/0x1df
[ 14.484819] PGD 3f86b067 PUD 3f86c067 PMD 3f86d067 PTE 0
[ 14.484819] Oops: 0000 [#1] SMP
[ 14.484819] last sysfs file:
[ 14.484819] CPU 0
[ 14.484819] Modules linked in:
[ 14.484819] Pid: 1, comm: swapper Not tainted 2.6.32.11 #5 P5Q-E
Boris.
--- On Wed, 4/21/10, Boris Derzhavets
<bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, April 21, 2010, 9:25 AM
Serial log for 2.6.32.11 loading under Xen 4.0 on top of
Fedora 12 (ASUS P5Q-E)
Boris.
--- On Wed, 4/21/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@goop.org>
Date: Wednesday, April 21, 2010, 4:05 AM
Yes, it would be helpful if you can provide more complete serial console log. From the below log, I can see
acpi_processor_set_pdc-> acpi_evaluate_object(pr->handle, "_PDC", pdc_in, NULL) cause the system panic. However, it cannot tell why _PDC evaluation cause panic. It may be BIOS issue as you suggested, but we need more log to decide if this is true. And if true, ASUS should be the right place to get updated BIOS.
Also, how is the 2.6.32.11 kernel working in bare mental environment? acpi_processor_set_pdc is not xen specific code, so this issue is likely also occurring in bare mental environment.
And according to your test result, 2.6.32.9 works while 2.6.32.10 not. This remind me change we made recently made, i.e. "re-enable mwait for xen cpuidle", I am not sure if this cause the panic. So could you please try the grub kernel option "idle=nomwait"? This option will revert the effect of that patch. If "idle=nomwait" works, then we can dig more in this direction.
Best
Regards
Ke
===============================
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Wednesday, April 21, 2010 5:26 AM
To: Yu, Ke
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com; Yu, Ke; Jeremy Fitzhardinge
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
If it would not help, i will set up serial console ( a bit painful for me to move boxes )
Tail of sreen output on ASUS P5Q-E +C2D E8400 for 2.6.32.11 kernel :-
acpi_processor_set_pdc + 0x3c/0x3e
xen_acpi_processor_add + 0x2ef/0x426
acpi_device_probe + 0x4b/0x11d
driver_probe_device + 0x86/0x180
__diver_attach + 0x86/0x180
__diver_attach +
0x86/0xa0
bus_for_each_dev 0x64/0x90
driver_attach + 0x71/0x140
bus_add_driver + 0x3e/0x140
driver_register + 0x71/0x140
?acpi_processor_init 0x3e/0x140
?acpi_processor_init 0x71/0x140
acpi_bus_register_driver +0x3e/0x12
xen_acpi_processor_init 0xae/0x128
acpi_processor_init + 0x3e/0x12
? acpi_pci_slot_init 0x0/0x20
? acpi_pci_slot_init 0x0/0x20
do_one_init_call + 0x37/0x1xa0
kernel_init 0x148/0x196
child_rip + 0xa/0x20
? init_ret_from_sys_call 0x7/0x16
? retint_restore_args 0x5/0x5
? child_rip 0x0/0x20
Screen output stopped.
Thanks.
Boris.
P.S. Nothing similar happens on ASUS P5Q3 + Q9550
Dom0 loads smoothly. Tested on F12 and Ubuntu 9.10.
Same picture.
--- On Tue, 4/20/10, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Failure to
load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Yu, Ke" <ke.yu@intel.com>
Date: Tuesday, April 20, 2010, 2:21 PM
On
04/20/2010 03:44 AM, Boris Derzhavets wrote:
> ASUS P5Q-E 2.6.31.13 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.9 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.10 under Xen 4.0 doesn't load
>
> ASUS P5Q3 all kernels work fine
>
> I believe that the issue is connected with outdated ( ACPI 2 Enabled) BIOS
> on first board. This question is mostly addressed to Yu Ke. What BIOS
> upgrade is required (exact version) , if ever possible.
>
It would probably help him if you 1. address your mail to him, and 2.
provide more specific information about what the failure is, beyond
``Before child_rip word "acpi" shows pretty often. In particular
"acpi_xen_processor"''.
J
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 9822 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
2010-04-21 13:25 Boris Derzhavets
@ 2010-04-22 9:58 ` Boris Derzhavets
2010-04-22 11:32 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-22 9:58 UTC (permalink / raw)
To: KeYu; +Cc: Jeremy Fitzhardinge, xen-devel, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 5493 bytes --]
Why it happens on ASUS P5Q-E ( 8 GB DDR2 Kingston) and doesn't on ASUS P5Q3 ( 8 GB DDR3 Kingston) ?
(XEN) mm.c:859:d0 Error getting mfn 80000 (pfn 5555555555555555) from L1 entry 8000000080000473 for l1e_owner=0, pg_owner=32753
[ 14.484819] BUG: unable to handle kernel paging request at ffffc9000003a000
[ 14.484819] IP: [<ffffffff812aba22>] acpi_ex_system_memory_space_handler+0x16d/0x1df
[ 14.484819] PGD 3f86b067 PUD 3f86c067 PMD 3f86d067 PTE 0
[ 14.484819] Oops: 0000 [#1] SMP
[ 14.484819] last sysfs file:
[ 14.484819] CPU 0
[ 14.484819] Modules linked in:
[ 14.484819] Pid: 1, comm: swapper Not tainted 2.6.32.11 #5 P5Q-E
Boris.
--- On Wed, 4/21/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
To: "KeYu" <ke.yu@intel.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Date: Wednesday, April 21, 2010, 9:25 AM
Serial log for 2.6.32.11 loading under Xen 4.0 on top of Fedora 12 (ASUS P5Q-E)
Boris.
--- On Wed, 4/21/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@goop.org>
Date: Wednesday, April 21, 2010, 4:05 AM
Yes, it would be helpful if you can provide more complete serial console log. From the below log, I can see
acpi_processor_set_pdc-> acpi_evaluate_object(pr->handle, "_PDC", pdc_in, NULL) cause the system panic. However, it cannot tell why _PDC evaluation cause panic. It may be BIOS issue as you suggested, but we need more log to decide if this is true. And if true, ASUS should be the right place to get updated BIOS.
Also, how is the 2.6.32.11 kernel working in bare mental environment? acpi_processor_set_pdc is not xen specific code, so this issue is likely also occurring in bare mental environment.
And according to your test result, 2.6.32.9 works while 2.6.32.10 not. This remind me change we made recently made, i.e. "re-enable mwait for xen cpuidle", I am not sure if this cause the panic. So could you please try the grub kernel option "idle=nomwait"? This option will revert the effect of that patch. If "idle=nomwait" works, then we can dig more in this direction.
Best
Regards
Ke
===============================
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Wednesday, April 21, 2010 5:26 AM
To: Yu, Ke
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com; Yu, Ke; Jeremy Fitzhardinge
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
If it would not help, i will set up serial console ( a bit painful for me to move boxes )
Tail of sreen output on ASUS P5Q-E +C2D E8400 for 2.6.32.11 kernel :-
acpi_processor_set_pdc + 0x3c/0x3e
xen_acpi_processor_add + 0x2ef/0x426
acpi_device_probe + 0x4b/0x11d
driver_probe_device + 0x86/0x180
__diver_attach + 0x86/0x180
__diver_attach +
0x86/0xa0
bus_for_each_dev 0x64/0x90
driver_attach + 0x71/0x140
bus_add_driver + 0x3e/0x140
driver_register + 0x71/0x140
?acpi_processor_init 0x3e/0x140
?acpi_processor_init 0x71/0x140
acpi_bus_register_driver +0x3e/0x12
xen_acpi_processor_init 0xae/0x128
acpi_processor_init + 0x3e/0x12
? acpi_pci_slot_init 0x0/0x20
? acpi_pci_slot_init 0x0/0x20
do_one_init_call + 0x37/0x1xa0
kernel_init 0x148/0x196
child_rip + 0xa/0x20
? init_ret_from_sys_call 0x7/0x16
? retint_restore_args 0x5/0x5
? child_rip 0x0/0x20
Screen output stopped.
Thanks.
Boris.
P.S. Nothing similar happens on ASUS P5Q3 + Q9550
Dom0 loads smoothly. Tested on F12 and Ubuntu 9.10.
Same picture.
--- On Tue, 4/20/10, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Yu, Ke" <ke.yu@intel.com>
Date: Tuesday, April 20, 2010, 2:21 PM
On
04/20/2010 03:44 AM, Boris Derzhavets wrote:
> ASUS P5Q-E 2.6.31.13 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.9 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.10 under Xen 4.0 doesn't load
>
> ASUS P5Q3 all kernels work fine
>
> I believe that the issue is connected with outdated ( ACPI 2 Enabled) BIOS
> on first board. This question is mostly addressed to Yu Ke. What BIOS
> upgrade is required (exact version) , if ever possible.
>
It would probably help him if you 1. address your mail to him, and 2.
provide more specific information about what the failure is, beyond
``Before child_rip word "acpi" shows pretty often. In particular
"acpi_xen_processor"''.
J
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 7190 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log)
@ 2010-04-21 13:25 Boris Derzhavets
2010-04-22 9:58 ` Boris Derzhavets
0 siblings, 1 reply; 22+ messages in thread
From: Boris Derzhavets @ 2010-04-21 13:25 UTC (permalink / raw)
To: KeYu; +Cc: Jeremy Fitzhardinge, xen-devel, Konrad Rzeszutek Wilk
[-- Attachment #1.1: Type: text/plain, Size: 4136 bytes --]
Serial log for 2.6.32.11 loading under Xen 4.0 on top of Fedora 12 (ASUS P5Q-E)
Boris.
--- On Wed, 4/21/10, Yu, Ke <ke.yu@intel.com> wrote:
From: Yu, Ke <ke.yu@intel.com>
Subject: RE: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@goop.org>
Date: Wednesday, April 21, 2010, 4:05 AM
Yes, it would be helpful if you can provide more complete serial console log. From the below log, I can see acpi_processor_set_pdc-> acpi_evaluate_object(pr->handle, "_PDC", pdc_in, NULL) cause the system panic. However, it cannot tell why _PDC evaluation cause panic. It may be BIOS issue as you suggested, but we need more log to decide if this is true. And if true, ASUS should be the right place to get updated BIOS.
Also, how is the 2.6.32.11 kernel working in bare mental environment? acpi_processor_set_pdc is not xen specific code, so this issue is likely also occurring in bare mental environment.
And according to your test result, 2.6.32.9 works while 2.6.32.10 not. This remind me change we made recently made, i.e. "re-enable mwait for xen cpuidle", I am not sure if this cause the panic. So could you please try the grub kernel option "idle=nomwait"? This option will revert the effect of that patch. If "idle=nomwait" works, then we can dig more in this direction.
Best Regards
Ke
===============================
From: Boris Derzhavets [mailto:bderzhavets@yahoo.com]
Sent: Wednesday, April 21, 2010 5:26 AM
To: Yu, Ke
Cc: Konrad Rzeszutek Wilk; xen-devel@lists.xensource.com; Yu, Ke; Jeremy Fitzhardinge
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
If it would not help, i will set up serial console ( a bit painful for me to move boxes )
Tail of sreen output on ASUS P5Q-E +C2D E8400 for 2.6.32.11 kernel :-
acpi_processor_set_pdc + 0x3c/0x3e
xen_acpi_processor_add + 0x2ef/0x426
acpi_device_probe + 0x4b/0x11d
driver_probe_device + 0x86/0x180
__diver_attach + 0x86/0x180
__diver_attach + 0x86/0xa0
bus_for_each_dev 0x64/0x90
driver_attach + 0x71/0x140
bus_add_driver + 0x3e/0x140
driver_register + 0x71/0x140
?acpi_processor_init 0x3e/0x140
?acpi_processor_init 0x71/0x140
acpi_bus_register_driver +0x3e/0x12
xen_acpi_processor_init 0xae/0x128
acpi_processor_init + 0x3e/0x12
? acpi_pci_slot_init 0x0/0x20
? acpi_pci_slot_init 0x0/0x20
do_one_init_call + 0x37/0x1xa0
kernel_init 0x148/0x196
child_rip + 0xa/0x20
? init_ret_from_sys_call 0x7/0x16
? retint_restore_args 0x5/0x5
? child_rip 0x0/0x20
Screen output stopped.
Thanks.
Boris.
P.S. Nothing similar happens on ASUS P5Q3 + Q9550
Dom0 loads smoothly. Tested on F12 and Ubuntu 9.10.
Same picture.
--- On Tue, 4/20/10, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [Xen-devel] Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on Ubuntu 9.10
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "Yu, Ke" <ke.yu@intel.com>
Date: Tuesday, April 20, 2010, 2:21 PM
On 04/20/2010 03:44 AM, Boris Derzhavets wrote:
> ASUS P5Q-E 2.6.31.13 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.9 under Xen 4.0 loads fine
> ASUS P5Q-E 2.6.32.10 under Xen 4.0 doesn't load
>
> ASUS P5Q3 all kernels work fine
>
> I believe that the issue is connected with outdated ( ACPI 2 Enabled) BIOS
> on first board. This question is mostly addressed to Yu Ke. What BIOS
> upgrade is required (exact version) , if ever possible.
>
It would probably help him if you 1. address your mail to him, and 2.
provide more specific information about what the failure is, beyond
``Before child_rip word "acpi" shows pretty often. In particular
"acpi_xen_processor"''.
J
[-- Attachment #1.2: Type: text/html, Size: 5580 bytes --]
[-- Attachment #2: serial.2.6.32.11.gz --]
[-- Type: application/x-gzip, Size: 36368 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2010-04-26 10:50 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-23 21:25 Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log) Boris Derzhavets
2010-04-23 21:35 ` Konrad Rzeszutek Wilk
2010-04-24 2:09 ` Yu, Ke
2010-04-24 13:07 ` Boris Derzhavets
2010-04-26 9:32 ` Yu, Ke
2010-04-26 10:44 ` Boris Derzhavets
-- strict thread matches above, loose matches on Subject: below --
2010-04-26 10:50 Boris Derzhavets
2010-04-24 7:29 Boris Derzhavets
2010-04-23 13:50 Boris Derzhavets
2010-04-23 20:16 ` Konrad Rzeszutek Wilk
2010-04-23 7:58 Boris Derzhavets
2010-04-23 9:12 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2010-04-23 10:45 ` Boris Derzhavets
2010-04-23 10:59 ` Boris Derzhavets
2010-04-23 13:32 ` Konrad Rzeszutek Wilk
2010-04-22 16:56 Boris Derzhavets
2010-04-22 19:23 ` Konrad Rzeszutek Wilk
2010-04-22 20:32 ` Boris Derzhavets
2010-04-22 21:09 ` Konrad Rzeszutek Wilk
2010-04-21 13:25 Boris Derzhavets
2010-04-22 9:58 ` Boris Derzhavets
2010-04-22 11:32 ` Boris Derzhavets
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.