[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] AMD IOMMU disabled - No Perdev Intremap



Tuesday, October 8, 2013, 6:39:13 PM, you wrote:

> On 10/06/2013 08:03 PM, Sander Eikelenboom wrote:
>> 
>> Sunday, October 6, 2013, 7:57:42 PM, you wrote:
>> 
>>> On 10/06/2013 07:45 PM, Sander Eikelenboom wrote:
>>>> 
>>>> Sunday, October 6, 2013, 7:28:03 PM, you wrote:
>>>> 
>>>>> On 10/06/2013 04:38 PM, Sander Eikelenboom wrote:
>>>>>> 
>>>>>> Sunday, October 6, 2013, 3:09:54 PM, you wrote:
>>>>>> 
>>>>>>> On 10/06/2013 02:58 PM, Andrew Cooper wrote:
>>>>>>>> On 06/10/2013 13:56, Ferdinand Nölscher wrote:
>>>>>>>>> Hi Sander,
>>>>>>>>> 
>>>>>>>>> Thanks for your reply.
>>>>>>>>> 
>>>>>>>>> On 10/06/2013 02:10 PM, Sander Eikelenboom wrote:
>>>>>>>>>> Sunday, October 6, 2013, 1:36:33 PM, you wrote:
>>>>>>>>>> 
>>>>>>>>>>> Hi!
>>>>>>>>>>>> From other people posting to this list, I know 
>>>>>>>>>>>> that there has been a
>>>>>>>>>>> bug related to the issue described in Xen
>>>>>>>>>>> Security Advisory 36 that disables iommu for some
>>>>>>>>>>> AMD users like me.
>>>>>>>>>> What motherboard do you have ?
>>>>>>>>> I have an ASUS M5A99X EVO Rev 1.01
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> It depends if it's the north or southbridge ioapic
>>>>>>>>>> but try using the new xen boot parameter: (add it
>>>>>>>>>> to the xen.gz line in grub)
>>>>>>>>>> 
>>>>>>>>>> ivrs_ioapic[0]=00:14.0
>>>>>>>>>> 
>>>>>>>>>> or
>>>>>>>>>> 
>>>>>>>>>> ivrs_ioapic[0]=00:00.1
>>>>>>>>> I tried both, it still fails to enable i/o 
>>>>>>>>> virtualisation.
>>>>>>>> 
>>>>>>>> Can you post a full xl dmesg, booting with 
>>>>>>>> iommu=debug,verbose as well?
>>>>>>>> 
>>>>>>>> ~Andrew
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> Ah it seems i got the id's mixed up :-)
>>>>>> 
>>>>>> ivrs_ioapic[9]=00:00.1 ivrs_ioapic[10]=00:14.0
>>>>>> 
>>>>>> Should do it i guess .. or should the ioapic handle be in
>>>>>> hex .. (then the last should be ivrs_ioapic[a]=00:14.0 )
>>>>>> 
>>>>>> -- Sander
>>>>>> 
>>>> 
>>>>> Booting with this parameters I can see "I/O Virtualisation 
>>>>> Enabled" but shortly after that, I get a CPU Panic:
>>>> 
>>>>> Xen Call Trace: amd_iommu_ioapic_update_ire ... 
>>>>> iommu_update_ire_from_apic ... set_ioapic_affinity_irq ... 
>>>>> smp_cpus_done ... __start_xen ...
>>>> 
>>>>> Panic on CPU 0: Assertion "get_rte_index(rte) == offset"
>>>>> failed at iommu_intr.c:188
>>>> 
>>>> 
>>>> Hmm, could you check if you can get a recent linux kernel to
>>>> boot on baremetal (so without xen) with the iommu enabled ?
>>>> (that would most certainly require one or both of the
>>>> ivrs_ioapic overrides as well)
>>>> 
>>>> I assumed but don't know for sure, did you previously had 
>>>> successfully used the iommu with the 
>>>> iommu=no-amd-iommu-perdev-intremap boot option ? And i
>>>> understand you upgraded your bios, if the previous answer was
>>>> yes .. did you try to revert to your previous bios version ?
>>>> 
>>>> Also added Jan and Suravee to the CC.
>>>> 
>>>> -- Sander
>>>> 
>>>> BTW: please keep everyone that was in the CC listed in
>>>> replies.
>>>> 
>>>> 
>>>> _______________________________________________ Xen-devel
>>>> mailing list Xen-devel@xxxxxxxxxxxxx
>>>> http://lists.xen.org/xen-devel
>>>> 
>>>> 
>> 
>>> What "recent" version? Currently, I'm using 3.10-3, is that ok?
>> 
>> I think so, you will need this patchset in the kernel: 
>> http://lkml.indiana.edu/hypermail/linux/kernel/1304.1/01567.html 
>> which implemented the overrides for linux.
>> 
>> 
>>> I have used iommu successfully before they added the new
>>> checking stuff, so I can't tell for sure. I just tried the new
>>> xen version because it kept panicking after some changes half a
>>> year ago. Now it's working again but without iommu. That's why I
>>> updated my bios, sadly, without any success.
>> 
>> I know the pain :-)
>> 
>>> I'll try booting with Andrews patch now.
>> 
>>> kind regards
>> 
>> 
>> 
>> 

> Today, I tested booting with the latest 3.12 kernel only, without xen,
> and it panicked after complaining about faulty remaps - sadly it
> didn't write any logs.

> I will look into this further the next days and I will post the
> information you asked for.

One other thing i would also try is to revert to your older bios with which you 
had
a working iommu in the past on a older xen version (with the 
no-amd-iommu-perdev-intremap option)

It could very well be you more recent bios is actually worse than your previous 
was ..

--
Sander

> kind regards



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.