All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
	"Li, Xin" <xin.li@intel.com>,
	"Li, Haicheng" <haicheng.li@intel.com>,
	"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: Critical bug: VT-d fault causes disk corruption orDom0 kernel panic.
Date: Thu, 22 Jan 2009 18:40:45 +0900	[thread overview]
Message-ID: <66C97C757FFC56takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <C59DEB76.21B5B%keir.fraser@eu.citrix.com>

Hi, Keir

Is compute_dom0_nr_pages() OK?
The number of available pages seems to be increase.
What do you think?

Best Regards,

Akio Takebe

>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@intel.com> 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@lists.xensource.com
>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
>>> Sent: Thursday, January 22, 2009 3:40 PM
>>> To: Li, Haicheng; 'xen-devel@lists.xensource.com'
>>> 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@intel.com> 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@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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

  reply	other threads:[~2009-01-22  9:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  3:42 Critical bug: VT-d fault causes disk corruption or Dom0 kernel panic Li, Haicheng
2009-01-22  7:40 ` Keir Fraser
2009-01-22  8:58   ` Li, Xin
2009-01-22  9:23     ` Keir Fraser
2009-01-22  9:40       ` Akio Takebe [this message]
2009-01-22  9:47         ` Critical bug: VT-d fault causes disk corruption orDom0 " Keir Fraser
2009-01-23  1:01       ` Critical bug: VT-d fault causes disk corruption or Dom0 " Kay, Allen M
2009-01-23  8:33         ` Keir Fraser
2009-01-23 17:30           ` Kay, Allen M
2009-01-23 18:41             ` Keir Fraser
2009-01-23 18:44               ` Keir Fraser
2009-01-23 23:40                 ` Kay, Allen M
2009-01-24  0:34                   ` Cihula, Joseph
2009-01-24  9:15                   ` Keir Fraser
2009-01-24  9:26                     ` Keir Fraser
2009-01-24 19:07                       ` Cihula, Joseph
2009-01-24 19:58                         ` Keir Fraser
2009-01-24  2:19               ` Cihula, Joseph

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66C97C757FFC56takebe_akio@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=haicheng.li@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xin.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.