I think detailed output of dmesg (both xen and dom0) will be helpful.
I checked the log again, and noticed following output. Seems there is IRQ
source override for timer in the platform and dom0/xen have different idea of
timer source in check_timer().
>> (XEN) ioapic_guest_write: apic=0, pin=2, old_irq=0, new_irq=-1
>> (XEN) ioapic_guest_write: old_entry=000009f0, new_entry=00010900
>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
>> (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=-1
>> (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=00010900
>> (XEN) ioapic_guest_write: Attempt to remove IO-APIC pin of in-use IRQ!
>> (XEN) ioapic_guest_write: apic=0, pin=0, old_irq=-1, new_irq=0
>> (XEN) ioapic_guest_write: old_entry=00010900, new_entry=000009f0
Thanks
Yunhong Jiang
>-----Original Message-----
>From: Patrick Colp [mailto:Patrick.Colp@xxxxxxxxxx]
>Sent: 2009年6月26日 17:38
>To: Jiang, Yunhong
>Cc: Christian Tramnitz; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Re: Xen cannot boot with pvops dom0
>
>I tried reverting those two changesets with no real effect (I
>got an extra error
>message from Xen to do with something about the timer).
>
>I still have a sneaking suspicion the problem is with the
>Linux kernel and not
>Xen, but I could be wrong.
>
>
>Patrick
>
>
>Jiang, Yunhong wrote:
>> hi, all, can you try to revert following two patches to see
>if any help?
>> If it do fix the issue, I will look it tomorrow when back to office.
>>
>> --jyh
>>
>>
>> changeset: 19809:16c2806b09c6
>> user: Keir Fraser <keir.fraser@xxxxxxxxxx>
>> date: Tue Jun 23 11:11:46 2009 +0100
>> files: xen/arch/x86/irq.c
>> description:
>> x86: Another assign_irq_vector() cleanup.
>>
>> Signed-off-by: Yunhong Jiang <yunhong.jiang@xxxxxxxxx>
>>
>>
>> changeset: 19804:07fea69baadc
>> user: Keir Fraser <keir.fraser@xxxxxxxxxx>
>> date: Fri Jun 19 08:43:58 2009 +0100
>> files: xen/arch/x86/irq.c
>> description:
>> x86: Fix legacy irq allocation issue
>>
>> When try to assign vector for irq, we should not assign vector for
>> legacy irq, which has fixed mapped irq<->vector relationship.
>>
>> Signed-off-by: Jiang, Yunhong <yunhong.jiang@xxxxxxxxx>
>>> -----Original Message-----
>>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>>> Christian Tramnitz
>>> Sent: 2009年6月25日 20:09
>>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>>> Subject: [Xen-devel] Re: Xen cannot boot with pvops dom0
>>>
>>> Patrick Colp wrote:
>>>>> I found the boot issue on my Q35, it can boot on my Nehalem.
>>>> What are the motherboard chipsets?
>>> Q35 *is* the chipset, for Nehalem its a Tylersburg chipset
>(either X58
>>> or 55x0)
>>>
>>> Best regards,
>>> Christian
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>
>>
>>
>---------------------------------------------------------------
>---------
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> _______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home