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 X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8EC6BC433E0 for ; Mon, 4 Jan 2021 21:37:18 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8B13421BE5 for ; Mon, 4 Jan 2021 21:37:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8B13421BE5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ens-lyon.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe :List-Id:In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=A4NU/DTMywF/nT/k6hauqgIgWEE8L6qewyHUA+94HYM=; b=zUOWrnpHelP92CtLd/ehqrNgIC Z8zJOz2MYqLA2KMAW2lgDXPbesqFTElqX3YPyIRxSkwRG0rIkVE19D+9r+QTovhqHHiwUFZQkIqNe p8sm/9d6sa8Ox9Va2GQrFV1HMJ+uvdv8vHHXMuuit5fa6mboXAVVcUiok2tNMCvty6sV2KUnwUmdc BHYQUAerAEAdSzUA2sxjHGqzHlHJ3qw1TKfOhyv5OSWlyBCYtpMbN9sEFQxk17XVb3cT/pqkZbJQ0 t0OwlLkiIc457Jyw7LjqJPR6iIuQvehS1W7Sjt/eglEXwkjBIY1DBeWW79B+bFeYOCbjqaCQpiYmL V4FNrB3A==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kwXX7-0005XU-FR; Mon, 04 Jan 2021 21:36:57 +0000 Received: from hera.aquilenet.fr ([185.233.100.1]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kwXX3-0005WK-D3 for linux-nvme@lists.infradead.org; Mon, 04 Jan 2021 21:36:54 +0000 Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id 01E663A8; Mon, 4 Jan 2021 22:36:51 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at aquilenet.fr Received: from hera.aquilenet.fr ([127.0.0.1]) by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxTrKyMHSvw3; Mon, 4 Jan 2021 22:36:50 +0100 (CET) Received: from function.youpi.perso.aquilenet.fr (lfbn-bor-1-56-204.w90-50.abo.wanadoo.fr [90.50.148.204]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 39DE0BE; Mon, 4 Jan 2021 22:36:50 +0100 (CET) Received: from samy by function.youpi.perso.aquilenet.fr with local (Exim 4.94) (envelope-from ) id 1kwXWz-000Mqb-07; Mon, 04 Jan 2021 22:36:49 +0100 Date: Mon, 4 Jan 2021 22:36:48 +0100 From: Samuel Thibault To: Keith Busch , Vidya Sagar , linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org Subject: Re: Are AER corrected errors worrying? Message-ID: <20210104213648.enkuq5e2o6adbiur@function> Mail-Followup-To: Samuel Thibault , Keith Busch , Vidya Sagar , linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org References: <20210101224028.4akud7meibjavvtf@function> <20210104184435.GE1024941@dhcp-10-100-145-180.wdc.com> <20210104201247.5k47gueib3cw4sfr@function> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20210104201247.5k47gueib3cw4sfr@function> Organization: I am not organized User-Agent: NeoMutt/20170609 (1.8.3) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210104_163653_630937_4F7E5A6C X-CRM114-Status: GOOD ( 16.00 ) X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org Samuel Thibault, le lun. 04 janv. 2021 21:12:47 +0100, a ecrit: > Vidya Sagar wrote: > > Since this is a laptop, I'm suspecting that ASPM states might have > > been enabled which could be causing these errors. > > Keith Busch, le lun. 04 janv. 2021 10:44:35 -0800, a ecrit: > > Sometimes these types of errors occur from low power settings, so you > > can try disabling the automatic management of these (assuming the > > hardware supports it). To disable nvme specific power state transitions, > > the kernel parameter is "nvme_core.default_ps_max_latency_us=0". > > I have tried to add it, > > I'll watch in the coming > hours/days to see if that avoided the issue. I did get one Jan 4 22:34:53 begin kernel: [ 7165.207562] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:02:00.0 Jan 4 22:34:53 begin kernel: [ 7165.213891] nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jan 4 22:34:53 begin kernel: [ 7165.216949] nvme 0000:02:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Jan 4 22:34:53 begin kernel: [ 7165.219995] nvme 0000:02:00.0: [ 0] RxErr > > PCI also has automatic link power savings that you can disable with > > parameter "pcie_aspm=off". > > I'll try that if I still see errors with the nvme_core parameter. I'm on it. Samuel _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme