From: Qian Cai <cai@lca.pw>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Joerg Roedel <jroedel@suse.de>,
Shivasharan S <shivasharan.srikanteshwara@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
iommu@lists.linux-foundation.org
Subject: "iommu/vt-d: Delegate DMA domain to generic iommu" series breaks megaraid_sas
Date: Fri, 07 Jun 2019 17:08:37 -0400 [thread overview]
Message-ID: <1559941717.6132.63.camel@lca.pw> (raw)
The linux-next series "iommu/vt-d: Delegate DMA domain to generic iommu" [1]
causes a system with the rootfs on megaraid_sas card unable to boot.
Reverted the whole series on the top of linux-next (next-20190607) fixed the
issue.
The information regards this storage card is,
[ 116.466810][ T324] megaraid_sas 0000:06:00.0: FW provided supportMaxExtLDs:
0 max_lds: 32
[ 116.476052][ T324] megaraid_sas 0000:06:00.0: controller type :
iMR(0MB)
[ 116.483646][ T324] megaraid_sas 0000:06:00.0: Online Controller Reset(OCR)
: Enabled
[ 116.492403][ T324] megaraid_sas 0000:06:00.0: Secure JBOD support :
Yes
[ 116.499887][ T324] megaraid_sas 0000:06:00.0: NVMe passthru support :
No
[ 116.507480][ T324] megaraid_sas 0000:06:00.0: FW provided
[ 116.612523][ T324] megaraid_sas 0000:06:00.0: NVME page size : (0)
[ 116.629991][ T324] megaraid_sas 0000:06:00.0: INIT adapter done
[ 116.714789][ T324] megaraid_sas 0000:06:00.0: pci id :
(0x1000)/(0x0017)/(0x1d49)/(0x0500)
[ 116.724228][ T324] megaraid_sas 0000:06:00.0: unevenspan support : no
[ 116.731518][ T324] megaraid_sas 0000:06:00.0: firmware crash dump :
no
[ 116.738981][ T324] megaraid_sas 0000:06:00.0: jbod sync map :
yes
[ 116.787433][ T324] scsi host0: Avago SAS based MegaRAID driver
[ 117.081088][ T324] scsi 0:0:0:0: Direct-
Access LENOVO ST900MM0168 L587 PQ: 0 ANSI: 6
[1] https://lore.kernel.org/patchwork/cover/1078960/
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Qian Cai <cai@lca.pw>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: James Sewart <jamessewart@arista.com>,
Joerg Roedel <jroedel@suse.de>,
iommu@lists.linux-foundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Shivasharan S <shivasharan.srikanteshwara@broadcom.com>
Subject: "iommu/vt-d: Delegate DMA domain to generic iommu" series breaks megaraid_sas
Date: Fri, 07 Jun 2019 17:08:37 -0400 [thread overview]
Message-ID: <1559941717.6132.63.camel@lca.pw> (raw)
The linux-next series "iommu/vt-d: Delegate DMA domain to generic iommu" [1]
causes a system with the rootfs on megaraid_sas card unable to boot.
Reverted the whole series on the top of linux-next (next-20190607) fixed the
issue.
The information regards this storage card is,
[ 116.466810][ T324] megaraid_sas 0000:06:00.0: FW provided supportMaxExtLDs:
0 max_lds: 32
[ 116.476052][ T324] megaraid_sas 0000:06:00.0: controller type :
iMR(0MB)
[ 116.483646][ T324] megaraid_sas 0000:06:00.0: Online Controller Reset(OCR)
: Enabled
[ 116.492403][ T324] megaraid_sas 0000:06:00.0: Secure JBOD support :
Yes
[ 116.499887][ T324] megaraid_sas 0000:06:00.0: NVMe passthru support :
No
[ 116.507480][ T324] megaraid_sas 0000:06:00.0: FW provided
[ 116.612523][ T324] megaraid_sas 0000:06:00.0: NVME page size : (0)
[ 116.629991][ T324] megaraid_sas 0000:06:00.0: INIT adapter done
[ 116.714789][ T324] megaraid_sas 0000:06:00.0: pci id :
(0x1000)/(0x0017)/(0x1d49)/(0x0500)
[ 116.724228][ T324] megaraid_sas 0000:06:00.0: unevenspan support : no
[ 116.731518][ T324] megaraid_sas 0000:06:00.0: firmware crash dump :
no
[ 116.738981][ T324] megaraid_sas 0000:06:00.0: jbod sync map :
yes
[ 116.787433][ T324] scsi host0: Avago SAS based MegaRAID driver
[ 117.081088][ T324] scsi 0:0:0:0: Direct-
Access LENOVO ST900MM0168 L587 PQ: 0 ANSI: 6
[1] https://lore.kernel.org/patchwork/cover/1078960/
next reply other threads:[~2019-06-07 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 21:08 Qian Cai [this message]
2019-06-07 21:08 ` "iommu/vt-d: Delegate DMA domain to generic iommu" series breaks megaraid_sas Qian Cai
2019-06-09 2:43 ` Lu Baolu
2019-06-09 2:43 ` Lu Baolu
2019-06-10 13:44 ` Qian Cai
2019-06-10 13:44 ` Qian Cai
2019-06-10 14:54 ` Qian Cai
2019-06-10 14:54 ` Qian Cai
2019-06-11 1:41 ` Lu Baolu
2019-06-11 1:41 ` Lu Baolu
2019-06-11 14:00 ` Qian Cai
2019-06-11 14:00 ` Qian Cai
2019-06-11 23:20 ` Lu Baolu
2019-06-11 23:20 ` Lu Baolu
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=1559941717.6132.63.camel@lca.pw \
--to=cai@lca.pw \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.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.