From: Lu Baolu <baolu.lu@linux.intel.com>
To: Koba Ko <koba.ko@canonical.com>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kai Heng Feng <kai.heng.feng@canonical.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Sun, Jian" <jian.sun@intel.com>
Subject: Re: [Issue]platform/x86: iommu: System can't shutdown because iommu driver keeps checking the status of DMA_GSTS_TES
Date: Mon, 15 Jun 2020 15:20:02 +0800 [thread overview]
Message-ID: <111dde48-8018-6d74-5df8-1534143f4de6@linux.intel.com> (raw)
In-Reply-To: <CAJB-X+Ww=bZN2qZ=e=4EkN_RUTiZxHxkdnHh50y9iVqZmT_XQg@mail.gmail.com>
Hi Koba Ko,
On 2020/6/15 11:19, Koba Ko wrote:
> hi All,
> I have a machine and there's only intel gpu.
> the secureboot and vt-d is enabled in BIOS.
> On the Ubuntu desktop, I do s2idle first and restart the machine.
> The machine can't restart successfully, so I need to press the
> power button to shutdown.
> I tried each of the following and the issue can't be triggered.
> 1. disable secure boot in BIOS.
> 2. intel_iommu=off.
> 3. intel_iomm=igfx_off.
> 4. nomodeset
> 5. i915.modeset=0.
>
> After I investigate further, find inte_iommu keeps checking the status
> of DMA_GSTS_TES.
> During the procedure of restart, the driver would disable iommu
> translation and
> check status of DMA_GSTS_TES until status of DMA_GSTS_TES is 0.
>
> If you need more information, I can provide it.
Do you mind telling what platform is it?
Best regards,
baolu
next parent reply other threads:[~2020-06-15 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJB-X+Ww=bZN2qZ=e=4EkN_RUTiZxHxkdnHh50y9iVqZmT_XQg@mail.gmail.com>
2020-06-15 7:20 ` Lu Baolu [this message]
2020-06-30 7:31 ` [Issue]platform/x86: iommu: System can't shutdown because iommu driver keeps checking the status of DMA_GSTS_TES Koba Ko
2020-06-30 7:52 ` Lu Baolu
2020-07-07 3:27 ` Koba Ko
2020-07-07 7:23 ` Lu Baolu
2020-06-15 3:46 Koba Ko
2020-07-09 20:58 ` Limonciello, Mario
2020-07-10 2:03 ` Koba Ko
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=111dde48-8018-6d74-5df8-1534143f4de6@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jian.sun@intel.com \
--cc=joro@8bytes.org \
--cc=kai.heng.feng@canonical.com \
--cc=koba.ko@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).