From: "Oliver Lin" <oliver@liuxiaozhen.dev>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"Baolu Lu" <baolu.lu@linux.intel.com>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"will@kernel.org" <will@kernel.org>
Subject: Re: [PATCH v3] iommu/vt-d: Disable IOMMU by default on Lenovo ThinkPad P50s
Date: Mon, 27 Jul 2026 11:21:56 +0800 [thread overview]
Message-ID: <19be3c19-9711-4cac-bc6e-c2b020588ec8@liuxiaozhen.dev> (raw)
In-Reply-To: <CO1PR11MB48354FC225C295EFC745EEF48CCC2@CO1PR11MB4835.namprd11.prod.outlook.com>
On 27/7/2026 09:31, Tian, Kevin wrote:
> This needs an official erratum disclosure from the vendor...
Thanks for the clarification.
Could you please advise whether this issue should be treated as an Intel
VT-d erratum or a Lenovo firmware issue?
The symptom is:
- ThinkPad P50s with VT-d enabled cannot fully power off.
- Adding intel_iommu=off resolves the issue.
- The issue is reproducible on this platform.
If Intel erratum is not applicable, would a Lenovo firmware confirmation
be sufficient for adding a platform quirk?
next prev parent reply other threads:[~2026-07-27 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 19:22 [PATCH] iommu/vt-d: Disable IOMMU " Oliver Lin
2026-06-21 1:29 ` Baolu Lu
[not found] ` <e4deced7-aabf-44d2-859c-d0b0add48d76@liuxiaozhen.dev>
2026-07-01 17:03 ` Oliver Lin
2026-07-02 10:31 ` [PATCH] iommu/vt-d: respect user override for intel_iommu=on " Oliver Lin
2026-07-03 1:26 ` Baolu Lu
2026-07-03 9:23 ` [PATCH v3] iommu/vt-d: Disable IOMMU by default " Oliver Lin
2026-07-13 1:55 ` Baolu Lu
2026-07-13 2:27 ` Oliver Lin
2026-07-25 2:44 ` Oliver Lin
2026-07-27 1:31 ` Tian, Kevin
2026-07-27 3:21 ` Oliver Lin [this message]
2026-07-27 4:03 ` Tian, Kevin
2026-07-27 4:48 ` Oliver Lin
2026-07-27 5:05 ` Tian, Kevin
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=19be3c19-9711-4cac-bc6e-c2b020588ec8@liuxiaozhen.dev \
--to=oliver@liuxiaozhen.dev \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®