Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp809227ybt; Tue, 7 Jul 2020 00:24:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwqgiaGZOFM46Xh1ZfD79tqJ6v9tdlhd3xZOaAR7qERIPHGZOC1wXdgQxiBCf5+aV7GyE1A X-Received: by 2002:a50:d8c2:: with SMTP id y2mr51783360edj.114.1594106685646; Tue, 07 Jul 2020 00:24:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594106685; cv=none; d=google.com; s=arc-20160816; b=AgFiMz66Avc6rk01CHUsvgwXXCq1jhYe5jqE+FgpV3BcVmbA8FTu8eyy9FxxP0LKFm a1uAkMal02qBAJLlGqaU6+lscPuE1g0InaHW14deu3z4ZyGWFBkRl4mtUb5VjtP8sf7Q q5QMWknpIeMfEMtUqWsEfIIWS9Rxxr3BddskF/pXVDZcCNe/Xjs2UhxuG0P+zibDvCXr 4sYilMTmyWnnFdvua7h8iwd9xO1Ua+Yb68Yxnr5qYGq8g5VBG7uSlEEY7vo0EAk01YYm cn9v9pSyL6Yd9gcMN+qijItW9NKSKAhidlItumvTEG7SEloO6niYFIz67+SD/dR9NNVX Pg2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc:ironport-sdr:ironport-sdr; bh=kWqfJ34jCZVr6yENN9Fz5Z9hBl4QnXZ+6HwzyXRZC1c=; b=h1VMj3kI6ctib0TLIhp9753sKACJ4DQ+i//oeRW/NbjQgXCDXI4N3E9+WcJG4andXN vsI8Td6DXNVHgh762nyRUZSGkgkZCzNj72OUBloZR6L3hzdyyzfp55zhdq2r+F9bP4PT tagPVkHJwRGCbA11jKLfuS+G7P+vZQqKPMt4a1AWn/v7WlSf2oKc1Vff3FBfLeYjYRbO 2F4Z3CpMVoz+8H+EHPtzjZl6/a88XFMyWXd93UaL6ZGIAgnU8f+PndgWU002TzKF9sRc SGhCHicZkJE9TTzXH93EG8A8CSzfsN3oEgvZckPwSd+QlFbu+q5mqZI/mexplNBUPalT zUOA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a19si14567455edy.575.2020.07.07.00.24.22; Tue, 07 Jul 2020 00:24:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728321AbgGGHYD (ORCPT + 99 others); Tue, 7 Jul 2020 03:24:03 -0400 Received: from mga06.intel.com ([134.134.136.31]:46333 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725825AbgGGHYC (ORCPT ); Tue, 7 Jul 2020 03:24:02 -0400 IronPort-SDR: GomxtYGTMp9nhhNCZZgOBmd3uitn0olFRjumTfUJb4fQfWguwGgp4BLrpfq3CgMlY+GvdcnIU2 E3m6LIYD6WdA== X-IronPort-AV: E=McAfee;i="6000,8403,9674"; a="209073720" X-IronPort-AV: E=Sophos;i="5.75,323,1589266800"; d="scan'208";a="209073720" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jul 2020 00:24:01 -0700 IronPort-SDR: 7lweS80P5ckMtp50mbg/VWoNPyMhE1JXIAcCTP7xmfNweRPorTbuXso1wFZuqw7JY7k/BIyFQx XPJxxdHE0MdQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,323,1589266800"; d="scan'208";a="357701412" Received: from blu2-mobl3.ccr.corp.intel.com (HELO [10.249.170.85]) ([10.249.170.85]) by orsmga001.jf.intel.com with ESMTP; 07 Jul 2020 00:23:58 -0700 Cc: baolu.lu@linux.intel.com, David Woodhouse , Joerg Roedel , iommu@lists.linux-foundation.org, Linux Kernel Mailing List , Kai Heng Feng , "Raj, Ashok" , "Sun, Jian" Subject: Re: [Issue]platform/x86: iommu: System can't shutdown because iommu driver keeps checking the status of DMA_GSTS_TES To: Koba Ko References: <111dde48-8018-6d74-5df8-1534143f4de6@linux.intel.com> <66cacbab-b04d-33f3-053e-4d554ac7c662@linux.intel.com> From: Lu Baolu Message-ID: <1b559268-5bf7-a185-4492-c34023b78689@linux.intel.com> Date: Tue, 7 Jul 2020 15:23:57 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; 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 Koba KO, On 2020/7/7 11:27, Koba Ko wrote: > Dear Baolu, > On Tue, Jun 30, 2020 at 3:52 PM Lu Baolu wrote: >> >> Hi Koba, >> >> On 2020/6/30 15:31, Koba Ko wrote: >>> On Mon, Jun 15, 2020 at 3:20 PM Lu Baolu wrote: >>>> >>>> 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 >>> Hi Baolu, >>> Sorry, i missed your email. >>> I'm running on TGL. >>> My colleague has reported this on bugzilla. >>> Have tested your patch and it works fine. >>> https://bugzilla.kernel.org/show_bug.cgi?id=208363 >>> >>> Could you explain more about these patches!? Why do we need a flag >>> for active iommu!? >>> >> >> We're still investigating this issue. If we find out more, I'll let you >> know. Thanks a lot for the reporting. >> >> Best regards, >> baolu >> > Sorry for disturbing, > Do you have any updates for this issue?! > https://bugzilla.kernel.org/show_bug.cgi?id=208363 We are in process of collecting what kind of platforms are affected. I will push the workaround patch to the community as soon as we are done. Best regards, baolu