[PATCH] fix: nvme_update_ns_info method should be called even if nvme_ms_ids_equal return false
Keith Busch
kbusch at kernel.org
Fri Apr 8 08:18:19 PDT 2022
On Fri, Apr 08, 2022 at 10:07:21AM +0200, Christoph Hellwig wrote:
> On Fri, Apr 08, 2022 at 03:56:49PM +0800, 金韬 wrote:
> > This is output from dmesg. Seems that "eui" has changed.
> >
> > [ 2.086226] loop0: detected capacity change from 0 to 8
> > [ 26.577001] eui changed from 0100000000000000 to 0000000000000001
> > [ 26.577003] nvme nvme0: identifiers changed for nsid 1
>
> Ok, looks like the device is broken and changes the EUID after power
> cycles. Can you send the output of lspci -v?
>
> Also just out of curiousity, does the ID keep changing if you do more
> suspend cycles?
The eui isn't legit in the first place (no OUI), and appears to be swqpping the
byte order during resume. This should be reported to the vendor.
More information about the Linux-nvme
mailing list