WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Critical bug: VT-d fault causes disk corruption or Dom0

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic.
From: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Date: Thu, 22 Jan 2009 17:01:49 -0800
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Thu, 22 Jan 2009 17:02:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C59DEB76.21B5B%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <E88DD564E9DC5446A76B2B47C3BCCA1548C9974C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C59DEB76.21B5B%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl8Q3YVs3niaMuxT1CPWgfSc0ZGCwAITqg5AAKyJXAAAOMrHgAfiHeg
Thread-topic: [Xen-devel] Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic.
Looks like the problem is caused by xen_in_range() call in 
vtd/iommu.c/intel_iommu_domain_init().  Definition of xen_in_range() was 
changed as part of the heap patch.

I'm looking into change intel_iommu_domain_init() to just map pages in 
dom0->page_list.  However this looks to be more complicated as d->page_list is 
not initialized at this stage of the boot yet.

Allen

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Thursday, January 22, 2009 1:23 AM
To: Li, Xin; Li, Haicheng; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: Re: [Xen-devel] Critical bug: VT-d fault causes disk corruption or 
Dom0 kernel panic.

Mmm well not really. :-)

Is there any assumption in the VT-d setup about preventing access to the Xen
heap, and could that be broken?

Perhaps the VT-d pagetables are broken causing bad DMAs leading to data
corruption and bad command packets?

 -- Keir

On 22/01/2009 08:58, "Li, Xin" <xin.li@xxxxxxxxx> wrote:

> We are looking into the issue too. If you have any idea on how it's caused,
> please tell us :-)
> Thanks!
> -Xin
> 
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
>> Sent: Thursday, January 22, 2009 3:40 PM
>> To: Li, Haicheng; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
>> Subject: Re: [Xen-devel] Critical bug: VT-d fault causes disk corruption or
>> Dom0
>> kernel panic.
>> 
>> Thanks,
>> 
>> I haven't seen any problems outside of VT-d since c/s 19057, btw.
>> 
>> -- Keir
>> 
>> On 22/01/2009 03:42, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
>> 
>>> All,
>>> 
>>> We met several system failures on different hardware platforms, which are
>>> all
>>> caused by VT-d fault.
>>> err 1: disk is corrupted by VT-d fault on SATA.
>>> err 2: Dom0 kernel panics at booting, which is caused VT-d fault on UHCI.
>>> err 3, Dom0 complains disk errors while creating HVM guests.
>>> 
>>> The culprit would be changeset 19054 "x86_64: Remove statically-partitioned
>>> Xen heap.".
>>> 
>>> Detailed error logs can be found via BZ#,
>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1409.
>>> 
>>> 
>>> -haicheng
>>> _______________________________________________
>>> 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

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

<Prev in Thread] Current Thread [Next in Thread>