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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 22C32C433F5 for ; Mon, 28 Feb 2022 20:59:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229745AbiB1VAg (ORCPT ); Mon, 28 Feb 2022 16:00:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229733AbiB1VAf (ORCPT ); Mon, 28 Feb 2022 16:00:35 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A98624F464 for ; Mon, 28 Feb 2022 12:59:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646081994; x=1677617994; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=9xl2b40hzO4JRtT5sjr752FQcYhwowPk6zQQxSWYUDk=; b=Q1+A7N/QWdKM2bw2DQpDuth4r7XR68k6XDMDgKD+gGsehGqUr/Vnx6N4 +Pg/56DM/29DcdSJZyp90SqsGQQgziwMNEocGRDYCObEkTTj/0agYE+ba MGYAEBkeby7u3th2aMFywLdrpZz+bm2FbpGmV9wTjDYvhmtvbdZ+YWlSk H9UIctsgGVwcsgZ9rjJDUFIIz4quOgHW24lXZlSF3jsl+E+OCAq/35SKZ uV9h6THPoLkY9HGPlga4r658F+wt/jIuY6Rr8knigUMAgsKL8N2jcO2t2 i1YGoL9F28UmpqElyBQ3vvJf+hIyXJoBYi3KK8LatNqxdKtvO39p7+OuQ w==; X-IronPort-AV: E=McAfee;i="6200,9189,10272"; a="253178587" X-IronPort-AV: E=Sophos;i="5.90,144,1643702400"; d="scan'208";a="253178587" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Feb 2022 12:59:54 -0800 X-IronPort-AV: E=Sophos;i="5.90,144,1643702400"; d="scan'208";a="593358352" Received: from smile.fi.intel.com ([10.237.72.59]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Feb 2022 12:59:52 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nOn6m-009b5a-T9; Mon, 28 Feb 2022 22:59:04 +0200 Date: Mon, 28 Feb 2022 22:59:04 +0200 From: "andriy.shevchenko@linux.intel.com" To: micklorain Cc: "gregkh@linuxfoundation.org" , "linux-usb@vger.kernel.org" , "mathias.nyman@intel.com" Subject: Re: [PATCH v1] usb: hcd: Try MSI interrupts on PCI devices Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Mon, Feb 28, 2022 at 08:12:47PM +0000, micklorain wrote: > Hi, > > This patch breaks USB for me. I noticed when I upgraded from debian's 4.19.0-18 (working) to 5.10.0-10 (broken). I git bisect'ed until I found that this patch is the culprit. Upstream 5.17.0-rc2 is still broken, but 5.17.0-rc2 with this patch reverted works. > > lsusb when things work : > https://paste.debian.net/hidden/2a964425/ > > lsusb when things are broken : > https://paste.debian.net/hidden/0376920c/ > > dmesg when things are broken : > https://paste.debian.net/hidden/780ca112/ > > dmesg when things work : > https://paste.debian.net/hidden/4d1bfc0f/ > > Let me know if you need anything else from me. Thanks for your report! Last time I have got something similar it becomes that PCI bridge which is used to connect USB controller to the PCI Root Bridge was not capable of MSI, while advertising that capability. I.o.w. HW bug. To understand if it's something similar, please run (under the root) each of the following commands: lspci -nk -vvv cat /proc/interrupts in both cases, i.e. working and non-working. And then share the output (all 4 files). -- With Best Regards, Andy Shevchenko