Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp426578pxy; Wed, 5 May 2021 05:45:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJydTua83KDjsXODUrCm+wJveQEXnV5iVSdX77rz0l4MVKh0slMIT44Xe+Hq1JKN/FpZjGOh X-Received: by 2002:a63:150c:: with SMTP id v12mr28377805pgl.344.1620218746571; Wed, 05 May 2021 05:45:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620218746; cv=none; d=google.com; s=arc-20160816; b=FhV58vstmMj9REv+VmC4UFIDW0IB0n2/56Puse9kOTh9bnztymZNIGNDnSeQeTB5kO h+8DcDJPJ622S4CLXP+s3iB+Pbwt00x4W5lU+y+ERSiciuxcxfWF/hG9a/SOLyro9klo uhAzOEfloIkAtn958L2SYqh53f0alfyZq4EXntlN0DDAp8Q7KcE3uMGQq9JMuEgFbe2x Oi4QBVeqG3K8c9xcDCOwrqNdRZ1KlGZ6tDiLauU1xw+vcnQKNPB/uMrnLWILITUp5wUq SsdkjL2IpvN6XqR/s2tq/orhRtkexmRz6YyvDhDhyJYqrS7PIYOJBf3vfhgkXGKBFcrD 0SrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6r9hzsEjhFXCxXyKN8DMPBpgK8it6W/ugYOp6pdwaWI=; b=ewfMKvWkp4LmoYrS0OuOR1RUTe20oCnOutlqhg8AtYthebQ4l8ghO2q/oN0BCvSEhc AT0VMjY7730hrPqhfEK8wGxJ0G/odNIiFapXhlrwmStOK1N7MMcD7DkwKQu4gASkaRN9 SgxUoIgTO9aT12B1rdOHb7fnzLRkP7GP5j+wjbCHm4mT1l3hbgtcbOBL0Rk9PZlqGp3z kYlpY2I9MFIYAEIdBlFlOy8146IUmBw0fNGeCzt/p8jeRab4Vtnn62wo+wq7lE4a34gt crFFA4hIIsYsv3ojOWK0E1u4YQJ1goHVEQBP4DAIM+RKffhmZ5yP7u5jPlZLIy47J8lu wnqQ== 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 j70si21105916pfd.2.2021.05.05.05.45.31; Wed, 05 May 2021 05:45:46 -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 S233349AbhEEMpA (ORCPT + 99 others); Wed, 5 May 2021 08:45:00 -0400 Received: from bmailout2.hostsharing.net ([83.223.78.240]:40265 "EHLO bmailout2.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232057AbhEEMpA (ORCPT ); Wed, 5 May 2021 08:45:00 -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 "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by bmailout2.hostsharing.net (Postfix) with ESMTPS id DE0802800B6C9; Wed, 5 May 2021 14:44:02 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id CFD67DF725; Wed, 5 May 2021 14:44:02 +0200 (CEST) Date: Wed, 5 May 2021 14:44:02 +0200 From: Lukas Wunner To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Greg KH , linux-usb@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Marek =?iso-8859-1?Q?Beh=FAn?= Subject: Re: xhci_pci & PCIe hotplug crash Message-ID: <20210505124402.GB29101@wunner.de> References: <20210505120117.4wpmo6fhvzznf3wv@pali> <20210505123346.kxfpumww5i4qmhnk@pali> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210505123346.kxfpumww5i4qmhnk@pali> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 05, 2021 at 02:33:46PM +0200, Pali Roh?r wrote: > I just spotted this crash during debugging PCIe controller driver > pci-aardvark.c with trying to expose its link down events via "hot plug" > interrupt and corresponding link layer state flags. > > And because in whole call trace I see only generic PCIe and USB code > path without any driver specific parts, I suspect that this is not PCIe > controller-specific issue but rather something "wrong" in genetic PCIe > (or USB) code. That is why I sent this email, so maybe somebody else > find something suspicious here. > > But still there is a chance that issue can be also in pci-aardvark.c > driver and somehow it masked its issue and propagated it into generic > PCIe hot plug code path. If you hot-remove the XHCI controller, accesses to its MMIO space will fail. xhci_irq() seems to perform such MMIO accesses. Normally this should happen silently and MMIO accesses just return with a fabricated "all ones" response. Chances are however that the Aardvark controller raises a synchronous external abort instead. Perhaps you can teach it not to do that. Thanks, Lukas