Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp1763448pxp; Mon, 7 Mar 2022 01:44:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJw82FZsJRB4jm4gfQIUeiGXDZik4o4qDWw+4C0qkUb+xr7vRrM5RxE/5SpyHNZoys5+VARg X-Received: by 2002:a17:907:8a04:b0:6b7:ebf1:efbe with SMTP id sc4-20020a1709078a0400b006b7ebf1efbemr8223572ejc.488.1646646242458; Mon, 07 Mar 2022 01:44:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646646242; cv=none; d=google.com; s=arc-20160816; b=fmR4jgGE8pzOE+JJudc+EzliJ/56GwTRennS0iiauue28nihsG2chTwEaD1fMbaOtb 1f8XXbrdZ9YrTTj05/LE+Zme7oiDftvmOiQooH1EghUCPbOaQ2BMFVjz6KiwSWcjkVEq ZSQBYqhsbqT4zpn4prFvq5/30tV8FfQWP8Z/AVwI9V2c6DzcFwKY7dEWWU5YfUbddWQi OYqg4tHuERQ2gGINBFJRYsP8Z0C9jaALLKxqwbPCwC+I9qiTdaXOE5TU0Sgyy0Wsih3R dnXosQxZG0wD4AGDtvj45wWGE0T4fgf1u+/iPySXOakMs21uiqqhMoT6fUza1nk9Ry2j ZMIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject:from :references:cc:to:dkim-signature; bh=6JRON1QQYntlKNmAV/pHrf0bKLsUUoOrxSkWQC6CsLA=; b=YI85yUWU5rQxowkx+8ewHP7DCUsveLNAqDX1QcJTNEWeAVCTCccAzrmi/jcBpD8Uk+ 3URy036G0tLjSUYb3xnhXbuLaCzgZ24lmlqvTLpX2emhVn6IgeGYyuqM82svVS0IlIAo S56LEcQzdmdgSxvFosi3boaLF3S1ilyziqocSWlT+hsgfBcVHcttIiy4Gp63hv/6YkWZ UExXlqUhf2uBzqsiXKFVXlWbdoL9YOrNAmTMpoPTc3Bgxd5CfpBo4YfYDyQlToYIgnqt 9Q6sV1Vb7oVwkDl48NeOfWDKpCIn1ddy18y6zVXsX1T2gFejfj3KI42W3PxVOsJ7kaQI lUNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Iot3qmYn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gb1-20020a170907960100b006db0a308b97si3722618ejc.660.2022.03.07.01.43.40; Mon, 07 Mar 2022 01:44:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Iot3qmYn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233549AbiCGIsp (ORCPT + 99 others); Mon, 7 Mar 2022 03:48:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233385AbiCGIso (ORCPT ); Mon, 7 Mar 2022 03:48:44 -0500 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A24BEE0A; Mon, 7 Mar 2022 00:47:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646642869; x=1678178869; h=to:cc:references:from:subject:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=xt/3R0lQEI5gTKOyK1+eaIjn7pr4giAio4UXAW6KfRk=; b=Iot3qmYni8Y0TZbUMQSi7hJoNUxGueUGdgF8FO94rpK1oDDEDAvzcYkJ 5T2DiZGm/hEvBvnofcRyjKz0FYPc6gpT/DVPO00GHkJYNBoLMDJNzd+xH 0eDVZyazqH5/xsxu19BgEUxiPXEDrBAPx3xHs5iWWxJSsMJs69DU9nebU YghUzAv1QzxSo3Y7/x93CnNxCLGWrCYi9f02Dh0hJZWI1lGTbRL2eo1n8 rZQyJ33hXByaWNMh7N1S3bLQjMXje1yGUINIo5lcdIe5PUw9ICyQlEezL YCAuuGq8xX263zFJ8qZVbniz+/zDio6taQWQnJ+8BStB2KlYcrt3uBJwM Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10278"; a="317571629" X-IronPort-AV: E=Sophos;i="5.90,161,1643702400"; d="scan'208";a="317571629" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Mar 2022 00:47:43 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,161,1643702400"; d="scan'208";a="577527667" Received: from mattu-haswell.fi.intel.com (HELO [10.237.72.199]) ([10.237.72.199]) by orsmga001.jf.intel.com with ESMTP; 07 Mar 2022 00:47:41 -0800 To: Greg KH , Martin Kepplinger Cc: mathias.nyman@intel.com, kernel@puri.sm, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220304113057.1477958-1-martin.kepplinger@puri.sm> From: Mathias Nyman Subject: Re: [PATCH] usb: xhci: make XHCI_STOP_EP_CMD_TIMEOUT a module parameter Message-ID: <835b3990-43a6-a985-81b4-b86bddfe951f@linux.intel.com> Date: Mon, 7 Mar 2022 10:49:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4.3.2022 16.17, Greg KH wrote: > On Fri, Mar 04, 2022 at 12:30:57PM +0100, Martin Kepplinger wrote: >> On the Librem 5 imx8mq system we've seen the stop endpoint command >> time out regularly which results in the hub dying. >> >> While on the one hand we see "Port resume timed out, port 1-1: 0xfe3" >> before this and on the other hand driver-comments suggest that the driver >> might be able to recover instead of dying here, Sarah seemed to have a >> workaround for this particulator problem in mind already: >> >> Make it a module parameter. So while it might not be the root cause for >> the problem, do this to give users a workaround. > > This is not the 1990's, sorry, please do not add new module parameters. > They modify code, when you want to modify an individual device. > Agree, I think we really need to find the rootcause here. There's a known problem with this stop endpoint timeout timer. For all other commands we start the timer when the controller starts processing the command, but the stop endpoint timer is started immediately when command is queued. So it might timeout if some other commend before it failed. I have a patchseries for this. It's still work in progress but should be testable. Pushed to a branch named stop_endpoint_fixes git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git stop_endpoint_fixes https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/log/?h=stop_endpoint_fixes Can you try it out and see if it helps? Thanks -Mathias