Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp729183iog; Mon, 13 Jun 2022 11:36:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzEn+0yktDXeUPr+l0FMvk7kjUyRtgSQRmkmnZbcYpkxpA82p7rVEkWw5N4NRzYXE6E6zzt X-Received: by 2002:a05:6a00:15c9:b0:51c:178:ac7e with SMTP id o9-20020a056a0015c900b0051c0178ac7emr307473pfu.64.1655145382045; Mon, 13 Jun 2022 11:36:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655145382; cv=none; d=google.com; s=arc-20160816; b=e5Fnrd41oKu95RCi396Po3p54t556taZHXzocXBbVlodU21GXJf/9JFd8Ia+Gvs6PP ScVwcYEyARwJb3MCC7h+8gpGlwjzkOuU/zMCOG9uJvS0b6mhl3wcDT6NZwrfI2Lh05G1 4XgOysWpCTKeX4eB3O96W9XWCCopNnAcO4X46BrIFab2GO5TnYp0jON2yn87/R/m4l9T AOVBtLvWs+wbDlRmF1r9MyEVcr5U5CERBSQMJMRSwlyi+MvEwjiAH8dZ6T0NJsX351gj r8+5b2XtuZ3JNSLtBBujTPHzqDVOmgnSnp78E8eVNY4haGAda47JurL9VKSx1XKEvfAH 8q1w== 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-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=7On3vAvzaXzEqX5m3G9llzX4j7Vxl3+0OPcXmBWDKNk=; b=mhG8GF/EJw3v1lQPiHDFYAjF1IBbTMhUjYXiL9qxWZ1O6Ht4/7f8lCFm5uLVeaQHc7 3D/rOgeu+3+OhS05P+/kGYiXCsvvEpK2X/SMif6h4ucYk2FArNblT9C0bYQ2yvMJQaVi a9c10JHVOOSqQBhiC6pF0zjvWqZ5Fc8w95aO46yg51/M22yyqKEqydjdmsnnr9IYxP2H BB8d7fTP9IJ7jqK1JOFlkmVEJMEc6edgozgqLORliNKF6VQv6koqHu218FB6ZLVz4WCC q2Dg9IcI0oZFvl52/++CO1JZIVLHVEdDsw3n6vX1f7SGe8AKeIcS6NAYLEsjcdozkhf0 zWTg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u18-20020a632352000000b0040500f60fa6si10006932pgm.791.2022.06.13.11.36.10; Mon, 13 Jun 2022 11:36:22 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240258AbiFMSI6 (ORCPT + 99 others); Mon, 13 Jun 2022 14:08:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50332 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244908AbiFMSIR (ORCPT ); Mon, 13 Jun 2022 14:08:17 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52E0542EEB for ; Mon, 13 Jun 2022 06:55:54 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id E1E6A68AA6; Mon, 13 Jun 2022 15:55:49 +0200 (CEST) Date: Mon, 13 Jun 2022 15:55:49 +0200 From: Christoph Hellwig To: "Jason A. Donenfeld" Cc: Christoph Hellwig , "R, Monish Kumar" , "open list:NVM EXPRESS DRIVER" , Sagi Grimberg , "alan.adamson@oracle.com" , LKML , Yi Zhang , Keith Busch , "axboe@fb.com" , "Rao, Abhijeet" Subject: Re: 2 second nvme initialization delay regression in 5.18 [Was: Re: [bug report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed during blktests] Message-ID: <20220613135549.GA1714@lst.de> References: <20220610061449.GD24331@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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 Fri, Jun 10, 2022 at 11:19:31AM +0200, Jason A. Donenfeld wrote: > Right, that seems like the set of variance we're dealing with. If it's a > firmware version issue, then we revert because people can update? Or can > we quirk firmware version numbers too? We can quirk on firmware version and model number as well. Those quirks need to go into the core nvme module and not just the PCI driver, though. > If it's ASIC stepping, I guess we > need to quirk that. And likewise thunderbolt, but that seems more > awkward to quirk around, because afaik, it all just appears as PCIe? It all appears as PCIe, but the pci_dev has an is_thunderbolt flag. Thanks to both of you for the information. I'd like to wait until the end of the week or so if we can hear something from Samsung, and if we don't we'll have to quirk based on the model number.