Comment # 9 on bug 1208944 from Jiri Slaby

Other than mmconfig disabled and lockdown changes, I see nothing obvious:
+efi: Remove mem92: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
+e820: remove [mem 0xc0000000-0xcfffffff] reserved

-LSM: Security Framework initializing
+LSM: initializing lsm=lockdown,capability,integrity,apparmor

-PCI: MMCONFIG at [mem 0xc0000000-0xce0fffff] reserved in E820
+PCI: not using MMCONFIG

-ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
+ata1: SATA link down (SStatus 4 SControl 300)

But lockdown was enabled only with 6.2.1 and this failed for you in 6.2.0
already.

Is 6.1.x broken the same way if you artificially disable mmconfig using
nommconf kernel parameter?

There could be also a scsi/block layer bug, of course.