Re: nvme trouble on MacBookPro13,1 after updating -current; PCI 0x2003106b

The Mac you have is a T1 model. It’s the only variant we didn’t fully test.

If you revert `5e0ba47aa00e`, it should boot again.

The good news is that I bought a MacBookPro13,1, a 16" model, and a 16~ Touch Bar model. I will compare the hardware between them to figure out a reliable way to detect T1 machines.

Once i open the diff, you can use it.

On Tue, 4 Aug 2026, at 19:39, Marcin Cieslak wrote:
> Hello,
> 
> this is just a quick report that I seem to have trouble booting
> my MacBookPro13,1 after updating from 822366134658 to 1c0d2f0b1a98
> 
> The machine has this nvme controller:
> 
> nvme0@pci0:1:0:0: class=0x018002 rev=0x11 hdr=0x00 vendor=0x106b device=0x2003 subvendor=0x106b subdevice=0x2003
> 
> and after the kernel update the booting seems to be lagging with some
> nvme namespace error messages being spit out every few seconds.
> 
> The EFI console text is very small so I can't read the messages but this has
> been working before.
> 
> Will try to get the exact messages out.
> 
> I can see some quirks got added to a newer NVMe controller from Apple but should
> not affect the one I have.
> 
> 14f5fd2395e3 nvme: Add quirk for Amazon EBS NVMe Controller
> 954098103ee2 nvme: Add quirk for broken namespace-change log
> bd30d1ad78e1 nvme: Explicitly cast caddr_t values
> 64b805d52eec nvme: Move default is_storage method to nvme_private.h
> 949804c81909 nvme: Use newbus to ask if a device is storage
> 5e0ba47aa00e nvme: add Apple T2 ANS2 NVMe quirks
> fb4e7898a359 Revert "nvme: Only attach to storage NVMe devices"
>