Re: nvme trouble on MacBookPro13,1 after updating -current; PCI 0x2003106b
"Abdelkader Boudih" <[email protected]> Tue, 04 Aug 2026 19:48:49 +0100
| Newsgroups | gmane.os.freebsd.current |
|---|---|
| Message-ID | <[email protected]> |
--2aada4031c33de13c4f05c6dd36ddd739e89a913 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The Mac you have is a T1 model. It=E2=80=99s the only variant we didn=E2= =80=99t 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, >=20 > this is just a quick report that I seem to have trouble booting > my MacBookPro13,1 after updating from 822366134658 to 1c0d2f0b1a98 >=20 > The machine has this nvme controller: >=20 > nvme0@pci0:1:0:0: class=3D0x018002 rev=3D0x11 hdr=3D0x00 vendor=3D0x10= 6b device=3D0x2003 subvendor=3D0x106b subdevice=3D0x2003 >=20 > and after the kernel update the booting seems to be lagging with some > nvme namespace error messages being spit out every few seconds. >=20 > The EFI console text is very small so I can't read the messages but th= is has > been working before. >=20 > Will try to get the exact messages out. >=20 > I can see some quirks got added to a newer NVMe controller from Apple = but should > not affect the one I have. >=20 > 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" >=20 --2aada4031c33de13c4f05c6dd36ddd739e89a913 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title></head><body><div class=3D"ali= gn-start" style=3D"text-align:start;">The Mac you have is a T1 model. It= =E2=80=99s the only variant we didn=E2=80=99t fully test.</div><div clas= s=3D"align-start" style=3D"text-align:start;"><br></div><div class=3D"al= ign-start" style=3D"text-align:start;">If you revert <code style=3D= "border-top-width:1px;border-right-width:1px;border-bottom-width:1px;bor= der-left-width:1px;border-top-style:solid;border-right-style:solid;borde= r-bottom-style:solid;border-left-style:solid;border-top-color:#ccc;borde= r-right-color:#ccc;border-bottom-color:#ccc;border-left-color:#ccc;borde= r-image-source:none;border-image-slice:100%;border-image-width:1;border-= image-outset:0;border-image-repeat:stretch;border-top-left-radius:3px;bo= rder-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-l= eft-radius:3px;background-image:none;background-position-x:0%;background= -position-y:0%;background-size:auto;background-repeat:repeat;background-= attachment:scroll;background-origin:padding-box;background-clip:border-b= ox;background-color:#f6f6f6;font-family:menlo, consolas, monospace;font-= size:90%;padding-top:1px;padding-right:3px;padding-bottom:1px;padding-le= ft:3px;">5e0ba47aa00e</code>, it should boot again.</div><div class=3D"a= lign-start" style=3D"text-align:start;"><br></div><div class=3D"align-st= art" style=3D"text-align:start;">The good news is that I bought a MacBoo= kPro13,1, a 16" model, and a 16~ Touch Bar model. I will compare the har= dware between them to figure out a reliable way to detect T1 machines.</= div><div class=3D"align-start" style=3D"text-align:start;"><br></div><di= v class=3D"align-start" style=3D"text-align:start;">Once i open the diff= , you can use it.</div><div class=3D"align-start" style=3D"text-align:st= art;"><br></div><div>On Tue, 4 Aug 2026, at 19:39, Marcin Cieslak wrote:= </div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>Hello,</div><d= iv><br></div><div>this is just a quick report that I seem to have troubl= e booting</div><div>my MacBookPro13,1 after updating from 822366134658 t= o 1c0d2f0b1a98</div><div><br></div><div>The machine has this nvme contro= ller:</div><div><br></div><div>nvme0@pci0:1:0:0: class=3D0x018002 rev=3D= 0x11 hdr=3D0x00 vendor=3D0x106b device=3D0x2003 subvendor=3D0x106b subde= vice=3D0x2003</div><div><br></div><div>and after the kernel update the b= ooting seems to be lagging with some</div><div>nvme namespace error mess= ages being spit out every few seconds.</div><div><br></div><div>The EFI = console text is very small so I can't read the messages but this has</di= v><div>been working before.</div><div><br></div><div>Will try to get the= exact messages out.</div><div><br></div><div>I can see some quirks got = added to a newer NVMe controller from Apple but should</div><div>not aff= ect the one I have.</div><div><br></div><div>14f5fd2395e3 nvme: Add quir= k for Amazon EBS NVMe Controller</div><div>954098103ee2 nvme: Add quirk = for broken namespace-change log</div><div>bd30d1ad78e1 nvme: Explicitly = cast caddr_t values</div><div>64b805d52eec nvme: Move default is_storage= method to nvme_private.h</div><div>949804c81909 nvme: Use newbus to ask= if a device is storage</div><div>5e0ba47aa00e nvme: add Apple T2 ANS2 N= VMe quirks</div><div>fb4e7898a359 Revert "nvme: Only attach to storage N= VMe devices"</div><div><br></div></blockquote><div><br></div></body></ht= ml> --2aada4031c33de13c4f05c6dd36ddd739e89a913--