Received: by 10.192.165.148 with SMTP id m20csp3961515imm; Tue, 8 May 2018 00:01:01 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrWLwttXiQ8W+4CsTGzmkM3QDZKzgKFdKiZ35Cnju64ghZ+JecquPQfIqvUCGh3GI2j63xY X-Received: by 2002:a63:6a08:: with SMTP id f8-v6mr30122520pgc.363.1525762861408; Tue, 08 May 2018 00:01:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525762861; cv=none; d=google.com; s=arc-20160816; b=W7OcYzASb/Zr2BUDmxNuX0tO4REvt0qSzJcGWc3BaSyS4vGTqyKCbUUDRIOY05xReU XASeoOpgHqUF28qvLNlkdyCDhrvprRJXt0kNrG10Pg89Q6Sb7qbXBC92O5kRq4B5gSv5 txP+04rAF5kzUvHEabl50NMiEggNK2/j/MdodKa5idkZQa/0LRTmPkwtSL3Hlw6uS5wc bSLs6iuF0+RCNqzWZwhOYcf7GkffQlfewLEQQf862OnATnJE+b155kBiQx5QgTPjVgyf gW/2vD2qSdwZLJ8Z3ZPtUzFj7pFbGL1G8hCp+DXOZD6mXWyEz3zFY3UgJ3QeGi8g6L6D 5YZA== 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:cc:to:subject:arc-authentication-results; bh=MKnX6ImLWJfVPc1CW65aOt2agDqZuR7Jfjkxh+hgGU4=; b=hN42GItrnVWVvAbNDXTDV/cy4JHbDzk81l040D++JM8X5LckmmDhFs6UFSkl2vtujf DNx8owRZoMGyIHsCmDfMKCPdICX+wM56S6/N8XL/rMvLnvoeDHrAnZmaTB4MOVNejex2 6U0b/iEHWr0fWYgo/qpjHyHSSJv1Ia81JshSEN7fwCNP45XF9QV9OhcsraeB6aMaMdz1 lvm3O2eI2aiwb/giHvxkcv4fP42h7wWaT0xw1Zl9c2lA9GzZPZbY17LqLw0TDq/VX1t4 OtD3U0CDgo6RAlkX48prtvKL+DEg9Rg1KqEKQzzKcBzE6BflOit04CmYetn64takePB+ QLiQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w16-v6si10650090plq.141.2018.05.08.00.00.46; Tue, 08 May 2018 00:01:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754495AbeEHG7j (ORCPT + 99 others); Tue, 8 May 2018 02:59:39 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:52021 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754479AbeEHG7i (ORCPT ); Tue, 8 May 2018 02:59:38 -0400 Received: from [192.168.0.2] (ip5f5ae9d1.dynamic.kabel-deutschland.de [95.90.233.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 6809C2012BA056; Tue, 8 May 2018 08:59:35 +0200 (CEST) Subject: Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago) To: Bjorn Helgaas , okaya@codeaurora.org Cc: Bjorn Helgaas , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Wunner References: <8770820b-85a0-172b-7230-3a44524e6c9f@molgen.mpg.de> <20180427192207.GG8199@bhelgaas-glaptop.roam.corp.google.com> <43b8ab4a-f8ee-dc96-40ec-e6fdfedd8309@molgen.mpg.de> <20180504024527.GE15790@bhelgaas-glaptop.roam.corp.google.com> <20180504133327.GF15790@bhelgaas-glaptop.roam.corp.google.com> <20180507213344.GA133147@bhelgaas-glaptop.roam.corp.google.com> From: Paul Menzel Message-ID: <903e7c20-fdd7-9cbf-debb-a90e70240c7c@molgen.mpg.de> Date: Tue, 8 May 2018 08:59:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180507213344.GA133147@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Bjorn, Am 07.05.2018 um 23:33 schrieb Bjorn Helgaas: > On Fri, May 04, 2018 at 08:33:27AM -0500, Bjorn Helgaas wrote: >> commit b0d6f2230e12c85ae3b65a854a53c67c7c1f6406 >> Author: Bjorn Helgaas >> Date: Thu May 3 18:39:38 2018 -0500 >> >> PCI: pciehp: Add quirk for Intel Command Completed erratum >> >> The Intel CF118 erratum means the controller does not set the Command >> Completed bit unless writes to the Slot Command register change "Control" >> bits. Command Completed is never set for writes that only change software >> notification "Enable" bits. This results in timeouts like this: >> >> pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago) >> >> When this erratum is present, avoid these timeouts by marking commands >> "completed" immediately unless they change the "Control" bits. >> >> Here's the text of the erratum from the Intel document: >> >> CF118 PCIe Slot Status Register Command Completed bit not always >> updated on any configuration write to the Slot Control >> Register >> >> Problem: For PCIe root ports (devices 0 - 10) supporting hot-plug, >> the Slot Status Register (offset AAh) Command Completed >> (bit[4]) status is updated under the following condition: >> IOH will set Command Completed bit after delivering the new >> commands written in the Slot Controller register (offset >> A8h) to VPP. The IOH detects new commands written in Slot >> Control register by checking the change of value for Power >> Controller Control (bit[10]), Power Indicator Control >> (bits[9:8]), Attention Indicator Control (bits[7:6]), or >> Electromechanical Interlock Control (bit[11]) fields. Any >> other configuration writes to the Slot Control register >> without changing the values of these fields will not cause >> Command Completed bit to be set. >> >> The PCIe Base Specification Revision 2.0 or later describes >> the “Slot Control Register” in section 7.8.10, as follows >> (Reference section 7.8.10, Slot Control Register, Offset >> 18h). In hot-plug capable Downstream Ports, a write to the >> Slot Control register must cause a hot-plug command to be >> generated (see Section 6.7.3.2 for details on hot-plug >> commands). A write to the Slot Control register in a >> Downstream Port that is not hotplug capable must not cause a >> hot-plug command to be executed. >> >> The PCIe Spec intended that every write to the Slot Control >> Register is a command and expected a command complete status >> to abstract the VPP implementation specific nuances from the >> OS software. IOH PCIe Slot Control Register implementation >> is not fully conforming to the PCIe Specification in this >> respect. >> >> Implication: Software checking on the Command Completed status after >> writing to the Slot Control register may time out. >> >> Workaround: Software can read the Slot Control register and compare the >> existing and new values to determine if it should check the >> Command Completed status after writing to the Slot Control >> register. >> >> Link: http://www.intel.com/content/www/us/en/processors/xeon/xeon-e7-v2-spec-update.html >> Link: https://lkml.kernel.org/r/8770820b-85a0-172b-7230-3a44524e6c9f@molgen.mpg.de >> Reported-by: Paul Menzel >> Signed-off-by: Bjorn Helgaas > > I applied this with Paul's tested-by on pci/hotplug for v4.18. Thank you very much. Will this also be picked up by the stable Linux kernel series? […] Kind regards, Paul