From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D5AC9C433E1 for ; Wed, 22 Jul 2020 02:45:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B54A320792 for ; Wed, 22 Jul 2020 02:45:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731832AbgGVCpH (ORCPT ); Tue, 21 Jul 2020 22:45:07 -0400 Received: from mga01.intel.com ([192.55.52.88]:47877 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731614AbgGVCpG (ORCPT ); Tue, 21 Jul 2020 22:45:06 -0400 IronPort-SDR: 8UbQCrr7550MDX6THsk15UgbiZSPcwoXH8ZT23pp9jca74yWvVq6usBNGOKk7C6lO6+jxQuwxF 2ez1RE+t5UlQ== X-IronPort-AV: E=McAfee;i="6000,8403,9689"; a="168406624" X-IronPort-AV: E=Sophos;i="5.75,381,1589266800"; d="scan'208";a="168406624" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jul 2020 19:45:06 -0700 IronPort-SDR: RmFrsz1pSqV972rnpbM1aylP3SgTt9vSuztKszdJZg4PSgL0Fca7zEH2cHTU+JIBJOV9MRyXS9 gPOevvMW1Rsw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,381,1589266800"; d="scan'208";a="392541736" Received: from allen-box.sh.intel.com (HELO [10.239.159.139]) ([10.239.159.139]) by fmsmga001.fm.intel.com with ESMTP; 21 Jul 2020 19:45:05 -0700 Cc: baolu.lu@linux.intel.com, "linux-kernel@vger.kernel.org" , "iommu@lists.linux-foundation.org" , "stable@vger.kernel.org" Subject: Re: Subject: Re: [PATCH 1/1] iommu/vt-d: Skip TE disabling on quirky gfx dedicated iommu To: "Miao, Jun" References: From: Lu Baolu Message-ID: <0f4b6760-bb8f-ebd3-ab9d-4ecba819883c@linux.intel.com> Date: Wed, 22 Jul 2020 10:40:17 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=gbk; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jun, On 7/22/20 10:26 AM, Miao, Jun wrote: >>> Kernel panic - not syncing: DMAR hardware is malfunctioning >>> CPU: 0 PID: 347 Comm: rtcwake Not tainted 5.4.0-yocto-standard #124 >>> Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 >>> SODIMM PD RVP TLC, BIOS ICLSFWR1.R00.3162.A00.1904162000 04/16/2019 >>> Call Trace: >>> dump_stack+0x59/0x75 >>> panic+0xff/0x2d4 >>> iommu_disable_translation+0x88/0x90 >>> iommu_suspend+0x12f/0x1b0 >>> syscore_suspend+0x6c/0x220 >>> suspend_devices_and_enter+0x313/0x840 >>> pm_suspend+0x30d/0x390 >>> state_store+0x82/0xf0 >>> kobj_attr_store+0x12/0x20 >>> sysfs_kf_write+0x3c/0x50 >>> kernfs_fop_write+0x11d/0x190 >>> __vfs_write+0x1b/0x40 >>> vfs_write+0xc6/0x1d0 >>> ksys_write+0x5e/0xe0 >>> __x64_sys_write+0x1a/0x20 >>> do_syscall_64+0x4d/0x150 >>> entry_SYSCALL_64_after_hwframe+0x44/0xa9 >>> RIP: 0033:0x7f97b8080113 >>> Code: 8b 15 81 bd 0c 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 >>> 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff >>> 77 55 c3 0f 1f 40 00 48 83 ec 28 48 89 54 24 18 >>> RSP: 002b:00007ffcfa6f48b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 >>> RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f97b8080113 >>> RDX: 0000000000000004 RSI: 000055e7db03b700 RDI: 0000000000000004 >>> RBP: 000055e7db03b700 R08: 000055e7db03b700 R09: 0000000000000004 >>> R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000004 >>> R13: 000055e7db039380 R14: 0000000000000004 R15: 00007f97b814d700 >>> Kernel Offset: 0x38a00000 from 0xffffffff81000000 (relocation range: >>> 0xffffffff80000000-0xffffffffbfffffff) >>> ---[ end Kernel panic - not syncing: DMAR hardware is malfunctioning ]--- > Do you mean that system hangs in iommu_disable_translation() without this fix. > [S3 successfully with the patch] And, this failure disappeared after you applied this fix? Best regards, baolu