From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ward Vandewege <ward@gnu.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: AMD_IOV: IO_PAGE_FALT trying to pass through Mellanox ConnectX HCA (debian testing)
Date: Fri, 28 Jan 2011 14:27:42 -0500 [thread overview]
Message-ID: <20110128192742.GB23494@dumpdata.com> (raw)
In-Reply-To: <20110128185809.GA24465@countzero.vandewege.net>
> The mlx4_core driver in the domU is not happy:
>
> [ 0.411867] mlx4_core: Mellanox ConnectX core driver v0.01 (May 1, 2007)
> [ 0.411879] mlx4_core: Initializing 0000:00:00.0
> [ 0.412027] mlx4_core 0000:00:00.0: enabling device (0000 -> 0002)
> [ 0.412027] mlx4_core 0000:00:00.0: Xen PCI enabling IRQ: 19
> [ 1.417477] mlx4_core 0000:00:00.0: Installed FW has unsupported command
> interface revision 0.
> [ 1.417509] mlx4_core 0000:00:00.0: (Installed FW version is 0.0.000)
> [ 1.417527] mlx4_core 0000:00:00.0: This driver version supports only
> revisions 2 to 3.
> [ 1.417549] mlx4_core 0000:00:00.0: QUERY_FW command failed, aborting.
>
> When trying to boot a PV domU with kernel options iommu=soft and
> swiotlb=force, the output is slightly different. The full bootlog is attached
Don't use swiotlb=force unless neccessary.
> (testsqueeze.bootlog.txt). Here's the relevant excerpt:
That is b/c you are missing iommu=pv on Xen hypervisor line, and
you might need to make sure your driver is using the VM_IO flag.
There was some discussion on LKML about this and they proposed
a patch that wasn't neccessary. Don't remember the details but I can
look that up next week.
>
> [ 0.441684] mlx4_core: Mellanox ConnectX core driver v1.0-ofed1.5.2
> (August 4, 2010)
> [ 0.441696] mlx4_core: Initializing 0000:00:00.0
> [ 0.442044] mlx4_core 0000:00:00.0: enabling device (0000 -> 0002)
> [ 0.442741] mlx4_core 0000:00:00.0: Xen PCI enabling IRQ: 19
> [ 2.752125] mlx4_core 0000:00:00.0: NOP command failed to generate MSI-X
> interrupt IRQ 54).
> [ 2.752158] mlx4_core 0000:00:00.0: Trying again without MSI-X.
> [ 2.884105] mlx4_core 0000:00:00.0: NOP command failed to generate
> interrupt (IRQ 54), aborting.
> [ 2.884138] mlx4_core 0000:00:00.0: BIOS or ACPI interrupt routing
next prev parent reply other threads:[~2011-01-28 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 18:58 AMD_IOV: IO_PAGE_FALT trying to pass through Mellanox ConnectX HCA (debian testing) Ward Vandewege
2011-01-28 19:27 ` Konrad Rzeszutek Wilk [this message]
2011-01-28 20:38 ` Ward Vandewege
2011-01-31 18:45 ` Konrad Rzeszutek Wilk
2011-01-31 19:51 ` Ward Vandewege
2011-01-31 20:03 ` Konrad Rzeszutek Wilk
2011-02-03 23:24 ` Ward Vandewege
2011-02-07 16:41 ` Konrad Rzeszutek Wilk
2011-02-07 17:03 ` Roedel, Joerg
2011-02-07 17:42 ` Ward Vandewege
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=20110128192742.GB23494@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ward@gnu.org \
--cc=xen-devel@lists.xensource.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.