[bug report] nvme4: inconsistent AWUPF, controller not added (0/7).

[alan.adamson at oracle.com]

On 7/2/25 4:13 AM, Yi Zhang wrote:
> Hi Christoph
>
> I found this failure on one Samsung NVMe disk[1] with the latest
> linux-block/for-next. Here is the reproducer and dmesg log.
> Please help check it and let me know if you need any info/test. Thanks.
>
> [1]
> SAMSUNG MZQL2960HCJR-00A07 (PM9A3)
> [2]
> + nvme format -l1 -f /dev/nvme4n1
> Success formatting namespace:1
> + nvme reset /dev/nvme4
> Reset: Network dropped connection on reset
>
> dmesg:
> [  751.872864] nvme nvme4: rescanning namespaces.
> [  752.177475] nvme nvme4: resetting controller
> [  752.221030] nvme nvme4: inconsistent AWUPF, controller not added (0/7).
> [  752.227653] nvme nvme4: Disabling device after reset failure: -22
>
Looks like the device isn't reporting AWUPF after the format/reset.

Can you try:

nvme id-ctrl /dev/nvme4 | grep awupf
nvme id-ns  /dev/nvme4n1 | grep nawupf
nvme format -l1 -f /dev/nvme4n1
nvme id-ctrl /dev/nvme4 | grep awupf
nvme id-ns  /dev/nvme4n1 | grep nawupf
nvme reset /dev/nvme4
nvme id-ctrl /dev/nvme4 | grep awupf


Alan