xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Keith Busch <keith.busch@intel.com>
Cc: xen-devel@lists.xenproject.org,
	Andreas Pflug <pgadmin@pse-consulting.de>,
	linux-nvme@lists.infradead.org
Subject: Re: kernel BUG at nvme/host/pci.c
Date: Sat, 15 Jul 2017 01:51:41 -0700	[thread overview]
Message-ID: <20170715085141.GC25753@infradead.org> (raw)
In-Reply-To: <20170714170846.GA24365@localhost.localdomain>

On Fri, Jul 14, 2017 at 01:08:47PM -0400, Keith Busch wrote:
> > So LVM2 backed by md raid1 isn't compatible with newer hardware... Any
> > suggestions?
> 
> It's not that LVM2 or RAID isn't compatible. Either the IOMMU isn't
> compatible if can use different page offsets for DMA addresses than the
> physical aaddresses, or the driver for it is broken. The DMA addresses
> in this mapped SGL look completely broken, at least, since the last 4
> entries are all the same address. That'll corrupt data.

Given that this is a Xen system I wonder if swiotlb-xen is involved
here, which does some odd chunking of dma translations?

> 
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
---end quoted text---

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

       reply	other threads:[~2017-07-15  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28fcb21a-35b6-61c1-29e0-9adcc954c98c@pse-consulting.de>
     [not found] ` <20170710190818.GA13671@localhost.localdomain>
     [not found]   ` <64da8c4d-2d69-22fa-06a0-aa4f11903e39@pse-consulting.de>
     [not found]     ` <20170711194523.GD4604@localhost.localdomain>
     [not found]       ` <458f2115-4a07-e23c-2f1f-a90a95668f74@pse-consulting.de>
     [not found]         ` <20170712195012.GA8388@localhost.localdomain>
     [not found]           ` <5ac79312-b9e3-7cbb-8a82-382fb99705b5@pse-consulting.de>
     [not found]             ` <20170713134754.GD8388@localhost.localdomain>
     [not found]               ` <39459fb9-ea2c-0718-10a1-a7e96b9ec21f@pse-consulting.de>
     [not found]                 ` <20170714170846.GA24365@localhost.localdomain>
2017-07-15  8:51                   ` Christoph Hellwig [this message]
2017-07-15 13:34                     ` kernel BUG at nvme/host/pci.c Andreas Pflug

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=20170715085141.GC25753@infradead.org \
    --to=hch@infradead.org \
    --cc=keith.busch@intel.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=pgadmin@pse-consulting.de \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).