Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp114834pxk; Tue, 15 Sep 2020 22:50:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyQV9i3fGaxns4Rk8Ud4jl0JmnHN3jwIxWJwB9PeYW3pW8C7pu3CJf/HF8bg8xAhZ1CeewG X-Received: by 2002:aa7:d4d2:: with SMTP id t18mr25449722edr.55.1600235417904; Tue, 15 Sep 2020 22:50:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600235417; cv=none; d=google.com; s=arc-20160816; b=eD5n7OrjImLT2s1jVvit6x/6j4latyotkeeBe0WtXIwGWC6q2dG1/wq3gUgSBXGkPA PPOOLNzkVDw9zsAvBNMHqEyXtogX+/5nOLTTAcBpFdNn2NUcV+dQEFQ0dscy2PZSwWGI LPKAqZWdn3lVxIybXRf0dASAOwXo9CvzTqbokrncAtfwI3dSGkFdXVIxWMqyRyw/v5sX Q39IFyq7Ge1VpYS38G/RoOJVdEnTw5DTIt0CIuOI7dTBvGUzHI85BOW+Km4PMZGhF3CG F/KfOMe2VHvZItAoUKpWMtf7uyMndoIrrPLbnxdbsQVHCiMfg/XLPO8Nn5Cxf1EkU5Qw y53A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=X8KNFfLrZ1sC2zJvltmwzjfflZscPQu4axbg2SCWK9w=; b=XtKWspq3e2cJwdzYgm25ocyDMgMVbNlc9wt1+wsVFrKxrE3WjTV4l9DqFWo/8Eppz9 k57w4od9klv+ABe+PW/vt6SHyyf7Q374zoyFNX59fag7BfKScFYDvGC+Whzmranc1eaX CCoKLL/iWzBM77VkAP2ugOQQD//I21tLDUCMZeMMTW1NX3hqg+eNp9qyiJOE8EpWHWeN 5o1JkmAOCCnEEIzSVbLd2C3c3Mg5zvwTs8UIFCoLcnHYkV+cJw5+6GquAGMKLYWcteFA kh4sApHVXdbz3Mc2y3sNlKBpHfVj39suDYD+g0ZDOLV7nJxl9MxZVhb1bgVlx5l5F1v7 lQsg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u6si11878381ejf.115.2020.09.15.22.49.54; Tue, 15 Sep 2020 22:50:17 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726132AbgIPFsY (ORCPT + 99 others); Wed, 16 Sep 2020 01:48:24 -0400 Received: from bmailout2.hostsharing.net ([83.223.78.240]:44017 "EHLO bmailout2.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726068AbgIPFsX (ORCPT ); Wed, 16 Sep 2020 01:48:23 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [IPv6:2a01:37:1000::53df:5f1c:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout2.hostsharing.net (Postfix) with ESMTPS id BFF4828004EDC; Wed, 16 Sep 2020 07:48:20 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 875701FBF; Wed, 16 Sep 2020 07:48:20 +0200 (CEST) Date: Wed, 16 Sep 2020 07:48:20 +0200 From: Lukas Wunner To: Jinpu Wang Cc: linux-pci@vger.kernel.org, Bjorn Helgaas , linux-kernel@vger.kernel.org Subject: Re: [RFC] pcie hotplug doesn't work with kernel 4.19 Message-ID: <20200916054820.GA853@wunner.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 15, 2020 at 04:15:15PM +0200, Jinpu Wang wrote: > We are testing PCIe nvme SSD hotplug, it works out of box with kernel 5.4.62, > dmesg during the hotplug: [...] > But with kernel 4.19.133, pcieport core doesn't print anything, is > there known problem with kernel 4.19 support for pcie hotplug, do we > need to backport some fixes from newer kernel to make it work? No known problem. Please open a bug on bugzilla.kernel.org and attach full dmesg output for 5.4.62 and 4.19.133, as well as lspci -vv output. You may want to add the following to the kernel command line: ignore_loglevel log_bug_len=10M "dyndbg=file drivers/pci/* +p" pciehp.pciehp_debug=1 > [ 683.218554] pcieport 0000:16:00.0: pciehp: Slot(0-3): Card present > [ 683.218555] pcieport 0000:16:00.0: pciehp: Slot(0-3): Link Up > [ 683.271702] pcieport 0000:16:00.0: pciehp: Timeout on hotplug > command 0x17e1 (issued 73280 msec ago) > [ 686.301874] pcieport 0000:16:00.0: pciehp: Timeout on hotplug > command 0x13e1 (issued 3030 msec ago) > [ 686.361894] pcieport 0000:16:00.0: pciehp: Timeout on hotplug > command 0x13e1 (issued 3090 msec ago) Those timeouts look suspicious. Perhaps the hotplug controller claims to support Command Completed Support, but in reality does not? > CONFIG_HOTPLUG_PCI=y > CONFIG_HOTPLUG_PCI_ACPI=y > CONFIG_HOTPLUG_PCI_ACPI_IBM=m > CONFIG_HOTPLUG_PCI_CPCI=y > CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m > CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m > CONFIG_HOTPLUG_PCI_SHPC=y > CONFIG_HOTPLUG_PCI_PCIE=y You may not need ACPI_IBM, CPCI, SHPC. Thanks, Lukas