From: Qian Cai <cai@lca.pw>
To: jroedel@suse.de
Cc: iommu@lists.linux-foundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: "iommu/amd: Set exclusion range correctly" causes smartpqi offline
Date: Fri, 26 Apr 2019 10:52:28 -0400 [thread overview]
Message-ID: <1556290348.6132.6.camel@lca.pw> (raw)
Applying some memory pressure would causes smartpqi offline even in today's
linux-next. This can always be reproduced by a LTP test cases [1] or sometimes
just compiling kernels.
Reverting the commit "iommu/amd: Set exclusion range correctly" fixed the issue.
[ 213.437112] smartpqi 0000:23:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x1000 flags=0x0000]
[ 213.447659] smartpqi 0000:23:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0000 address=0x1800 flags=0x0000]
[ 233.362013] smartpqi 0000:23:00.0: controller is offline: status code 0x14803
[ 233.369359] smartpqi 0000:23:00.0: controller offline
[ 233.388915] print_req_error: I/O error, dev sdb, sector 3317352 flags 2000001
[ 233.388921] sd 0:0:0:0: [sdb] tag#95 UNKNOWN(0x2003) Result: hostbyte=0x01
driverbyte=0x00
[ 233.388931] sd 0:0:0:0: [sdb] tag#95 CDB: opcode=0x2a 2a 00 00 55 89 00 00 01
08 00
[ 233.389003] Write-error on swap-device (254:1:4474640)
[ 233.389015] Write-error on swap-device (254:1:2190776)
[ 233.389023] Write-error on swap-device (254:1:8351936)
[1] /opt/ltp/testcases/bin/mtest01 -p80 -w
next reply other threads:[~2019-04-26 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 14:52 Qian Cai [this message]
2019-04-26 15:26 ` "iommu/amd: Set exclusion range correctly" causes smartpqi offline Joerg Roedel
2019-04-26 15:55 ` Qian Cai
2019-04-29 14:23 ` Joerg Roedel
2019-05-01 1:41 ` Qian Cai
2019-05-03 20:38 ` Qian Cai
2019-05-06 2:56 ` Qian Cai
2019-05-06 12:29 ` Joerg Roedel
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=1556290348.6132.6.camel@lca.pw \
--to=cai@lca.pw \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.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