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 4B470C433FE for ; Wed, 16 Nov 2022 17:19:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237798AbiKPRTw (ORCPT ); Wed, 16 Nov 2022 12:19:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36946 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234369AbiKPRTl (ORCPT ); Wed, 16 Nov 2022 12:19:41 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 14431112E for ; Wed, 16 Nov 2022 09:19:39 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id CF76268AA6; Wed, 16 Nov 2022 18:19:35 +0100 (CET) Date: Wed, 16 Nov 2022 18:19:35 +0100 From: Christoph Hellwig To: August Wikerfors Cc: Keith Busch , Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G Message-ID: <20221116171935.GA24524@lst.de> References: <20221116171727.4083-1-git@augustwikerfors.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221116171727.4083-1-git@augustwikerfors.se> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 16, 2022 at 06:17:27PM +0100, August Wikerfors wrote: > The Samsung PM9B1 512G SSD found in some Lenovo Yoga 7 14ARB7 laptop units > reports eui as 0001000200030004 when resuming from s2idle, causing the > device to be removed with this error in dmesg: > > nvme nvme0: identifiers changed for nsid 1 What EUI did it report before? Is the identifier stable after multiple resume cycles? Can some of the Samsung folks here reach out to the relevant firmware team to see if they have any clues?