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@xxxxxxxxx]
Sent: Wednesday, April 21, 2010 5:26 AM
To: Yu, Ke
Cc: Konrad Rzeszutek Wilk;
xen-devel@xxxxxxxxxxxxxxxxxxx; 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@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <
jeremy@xxxxxxxx>
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@xxxxxxxxx>
Cc: "Konrad Rzeszutek Wilk" <
konrad.wilk@xxxxxxxxxx>, "
xen-devel@xxxxxxxxxxxxxxxxxxx" <
xen-devel@xxxxxxxxxxxxxxxxxxx>, "Yu, Ke" <
ke.yu@xxxxxxxxx>
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
Home
