From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from va-2-46.ptr.blmpb.com (va-2-46.ptr.blmpb.com [209.127.231.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C0ED2F9C0 for ; Mon, 27 Jul 2026 03:24:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.127.231.46 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785122662; cv=none; b=rLxXPVGWSmopUIiv1IT7UhWvuEGAqLbNMm/lhqqc6oUQkwbD/nyupDXhXRxJ58gxNQwXqF3/PAm2kreweC1l6IA7e+KQ7599sFXMMypdxme+z642czs08g2AxVWud2oFRRosBraFOVgvcb3EmNteTvtfUWgQO1G2yO70IPGgxA4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785122662; c=relaxed/simple; bh=X8s9Mvf+ZvdPQ+lHl9f5VgjmWxvXtAWDQMTe5fx7U+E=; h=Message-Id:To:Subject:Content-Type:Cc:Date:Mime-Version:From: References:In-Reply-To; b=oTTUddKP5/7GVFB2ZruictkABe0uP8h2DuUOP4k928/5rEbRwI3Hfr+15Af1/N/wOKP0BdVSAVLKKydAR9ju0XreHqq71A4KM6Nb9uHR2uYhsb/E1upQRvHyPzA1bDYQWjo4WgwwNAdlcoaMIVJFdfttttHahjJRFARUmHGz+eY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=liuxiaozhen.dev; spf=pass smtp.mailfrom=liuxiaozhen.dev; dkim=pass (2048-bit key) header.d=liuxiaozhen.dev header.i=@liuxiaozhen.dev header.b=OQAzmGHO; arc=none smtp.client-ip=209.127.231.46 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=liuxiaozhen.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=liuxiaozhen.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=liuxiaozhen.dev header.i=@liuxiaozhen.dev header.b="OQAzmGHO" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=feishu2602171341; d=liuxiaozhen.dev; t=1785122528; h=from:subject:mime-version:from:date:message-id:subject:to:cc: reply-to:content-type:mime-version:in-reply-to:message-id; bh=t/z/pxfR5KleXe1fUrVt/D1onEzd18y4VdvHLYUNNC4=; b=OQAzmGHOpemguEEkngLzr4v2wf49L8zfkzQWZLzzGkMFPQqyoJBF0FpuGIj9dbCVDq5Uhk 01pEuulfHU/UangoKlVrq8wS6BpMLdRjbM4xjKrZ5rzQgE7VLRqR2Lqgr1pu6U+43TRQVS ERekJUE2M5wBqi46OqUnY3fZSpgBfTE6eDSpYDnfXrCs9Xsy5XYNqsWipZhzhM+teAHI4S 28PPoyohNnY+0rR8Q6p+ZJQFqXSHSPrFYRf+16+qlbQjqgWcToeoX91l0FXQzgdC6CntB/ kKF/FdDzTJxl/LHyWMkAsuDAQJKkjnVnTaM3FmBfeGxWdilCYv32GuRiH/qPtg== Message-Id: <19be3c19-9711-4cac-bc6e-c2b020588ec8@liuxiaozhen.dev> User-Agent: Mozilla Thunderbird Content-Transfer-Encoding: 7bit X-Lms-Return-Path: To: "Tian, Kevin" , "Baolu Lu" Subject: Re: [PATCH v3] iommu/vt-d: Disable IOMMU by default on Lenovo ThinkPad P50s Received: from [172.16.0.2] ([104.28.165.131]) by smtp.feishu.cn with ESMTPS; Mon, 27 Jul 2026 11:22:05 +0800 Content-Type: text/plain; charset=UTF-8 Cc: "iommu@lists.linux.dev" , "linux-kernel@vger.kernel.org" , "joro@8bytes.org" , "robin.murphy@arm.com" , "will@kernel.org" Date: Mon, 27 Jul 2026 11:21:56 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 From: "Oliver Lin" References: <20260703092348.17583-1-oliver@liuxiaozhen.dev> <775d3d16-f43d-4a5f-9629-4912a4cabd91@linux.intel.com> <0c9256b0-19ad-4d1d-baea-0ccd3b827d0f@liuxiaozhen.dev> In-Reply-To: Content-Language: en-US X-Original-From: Oliver Lin 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?