All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: yingbin wang <yingbin.wangyb@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: disk offline with xen4.0+pvops2.6.31.13
Date: Wed, 28 Apr 2010 09:50:21 -0400	[thread overview]
Message-ID: <20100428135021.GA29504@phenom.dumpdata.com> (raw)
In-Reply-To: <j2uacd07b8d1004280627v7dc1be17x8909b8f11b09fab4@mail.gmail.com>

On Wed, Apr 28, 2010 at 09:27:30PM +0800, yingbin wang wrote:
> we found some info from xen wiki:
> 
> Enabling MSI/MSI-X for Assigned Devices
> As of Xen 3.4.0 MSI/MSI-X is always on.
> 	This change was made in changeset: 18454:65dc37be0443
> In Xen 3.3.0, MSI/MSI-X could be enabled using the xen boot parameter "msi=1".
> 	This change was made in changeset: 18127:89d05940cc1c
> 	The following snippet from a grub configuration enables MSI/MSI-X
> 		kernel xen.gz msi=1
> 
> does it mean that we should also Enable MSI Support for SAS in mptbase module?

First try the iommu option (iommu=off for example) and also the x2apic=off

Do include your serial log so we can see what kind of error you are
getting. And also include you /proc/interrupts output please.

  reply	other threads:[~2010-04-28 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 13:42 disk offline with xen4.0+pvops2.6.31.13 yingbin wang
2010-04-26 20:34 ` Jeremy Fitzhardinge
     [not found]   ` <i2g6d64dfd91004270110v83687db1ye66da8bafb0eead3@mail.gmail.com>
2010-04-27  8:12     ` Fwd: " tsk
2010-04-27 19:32     ` Jeremy Fitzhardinge
2010-04-28  6:03       ` tsk
2010-04-28 13:27         ` yingbin wang
2010-04-28 13:50           ` Konrad Rzeszutek Wilk [this message]
2010-05-03  8:07             ` tsk
2010-05-03 16:54               ` Jeremy Fitzhardinge
2010-04-29  2:56           ` Zhang, Xiantao

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=20100428135021.GA29504@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yingbin.wangyb@gmail.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.