#asahi-dev · 2026-06-07 17:35
svenwhich macos version? you should also see some serial output from xnu at that point i think#asahi-dev · 2026-06-07 17:34
aites[m]Ahh right, I'm currently trying to boot with the t6020 and it's stuck on the rainbow logo with no progress bar#asahi-dev · 2026-06-07 17:33
svenand t6022 is then just 2x t6021 dies with a very high speed connection inbetween so that one likely uses the same kernel as well#asahi-dev · 2026-06-07 17:33
svent6020 and t6021 are rather similar, one is a effectively a cut-down version of the other#asahi-dev · 2026-06-07 17:32
yukaiirc t6032 and t6034 also use the t6031 kernel#asahi-dev · 2026-06-07 17:32
svenit probably uses the t6020 kernel#asahi-dev · 2026-06-07 17:30
aites[m]available for use. What should be the way to approach things from here?#asahi-dev · 2026-06-07 17:30
aites[m]Heya all! I've been trying to set up the m1n1 hypervisor on my Macbook M2 Max and I've been following the guide (https://asahilinux.org/docs/sw/m1n1-hypervisor/), but when creating the kernel cache and finding the debug dwarf, you need to have the kernel from the kernels directory match exactly with your SoC, right? I think that the M2 Max uses the t6021 kernel but from the KDK I found on the apple website I couldn't find a t6021 kernel#asahi-dev · 2026-06-07 14:42
sveni guess we really should add apple,firmware-abi to any new thing we upstream to prevent this nvme mess :(#asahi-dev · 2026-06-07 14:22
nickchanokay so the status is still the same, optional linear sq on T8103, on T6000 it became required#asahi-dev · 2026-06-07 14:22
nickchan"assert failed: [7442]:cmd fetch error for host Admin SQ, rresp code 2, status_reg: 0x1000000"#asahi-dev · 2026-06-07 14:21
sveni still don't get why they had to change those MMIO locations with a firmware update :/#asahi-dev · 2026-06-07 14:18
sventrue#asahi-dev · 2026-06-07 14:17
nickchanit wouldn't know which thread did what, so it panics#asahi-dev · 2026-06-07 14:17
nickchanSError exception should be a kernel panic; it's async and all linux knows is that it came from "somewhere"#asahi-dev · 2026-06-07 14:16
svenbtw. what exactly happens when the nvme driver SErrors because we try to access the pre-15 MMIO registers? does that only crash that one thread or does the kernel stop completely then?#asahi-dev · 2026-06-07 14:15
nickchanthe a11 driver is broke-ish until the patch that is still on the list so i do want to test again#asahi-dev · 2026-06-07 14:15
svenlinear sq, nvmmu is mandatory on M2 iirc#asahi-dev · 2026-06-07 14:15
svener, yeah, other way around#asahi-dev · 2026-06-07 14:14
nickchananyways nvmmu/linear sq is all there on M2+ still#asahi-dev · 2026-06-07 14:14
nickchani need to do some additional testing on how the t8015-nvme-ans2 compatible behave if used on like t6000#asahi-dev · 2026-06-07 14:13
sven*then#asahi-dev · 2026-06-07 14:13
svenand hen M2 dropped the linear sq, nvmmu stuff and apple still called that ans3, didn't they?#asahi-dev · 2026-06-07 14:12
nickchanso the ans2 driver does support ans2 :)#asahi-dev · 2026-06-07 14:11
nickchan"ANS3" is the one found in A14/M1+ that had linear sq, nvmmu stuff#asahi-dev · 2026-06-07 14:11
nickchan"ANS2" is on Apple A11-A13 and T2, it's roughly similar to the m1 device but it doesn't have linear SQ or nvmmu#asahi-dev · 2026-06-07 14:10
nickchan"ANS" is the pcie nvme device in Apple A9 and Apple A10#asahi-dev · 2026-06-07 14:09
svendon't remember what ans2 was, maybe the t2 macs?#asahi-dev · 2026-06-07 14:09
sveniirc last time we came to the conclusion that m1 was already ans3#asahi-dev · 2026-06-07 13:20
chaos_princessAppleANS3NVMeController. But apple themselves are inconsistent since that same device is RTBuddy(ANS2)#asahi-dev · 2026-06-07 13:19
yukawhere did you get the ANS3 from?#asahi-dev · 2026-06-07 13:04
kettenismaybe, but either way you end up with an unusable system#asahi-dev · 2026-06-07 13:03
svenother alternative would be to add apple,firmware-version but we also need to change the compatible because the old driver will SError very early#asahi-dev · 2026-06-07 13:03
svenit's actually called ANS3, that ANS2 was wrong all along#asahi-dev · 2026-06-07 13:01
kettenis(in the end it doesn't matter, but t8103-fw15-nvme-ans2 is a bit of a mouthful)#asahi-dev · 2026-06-07 12:59
kettenisand Apple still calls it ANS2 with the new firmware?#asahi-dev · 2026-06-07 12:34
sveni don't think so :(#asahi-dev · 2026-06-07 12:33
kettenissven: there is no way to find this out from the "hardware" itself?#asahi-dev · 2026-06-07 11:40
svenhttps://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git/log/?h=b4/nvme-m3 something like that would be nvme support for macos 15+ if we go with the "new compatible" path#asahi-dev · 2026-06-07 10:15
jannauerr, no. it doesn't. I was looking at the wrong tag#asahi-dev · 2026-06-07 10:13
jannauand the non-upstream driver in 6.17 makes the same calls anyway with the lock held#asahi-dev · 2026-06-07 10:07
svenme neither#asahi-dev · 2026-06-07 10:05
jannauthe register calls all look sane. I don't see how they could indirectly call back into atc#asahi-dev · 2026-06-07 09:55
svenno idea, can't find anything by just reading the code :/#asahi-dev · 2026-06-07 09:54
svenhmmmm#asahi-dev · 2026-06-07 09:51
jannaulockdep and kasan are clean for me (excluding lockdep issues in asahi and apple drm)#asahi-dev · 2026-06-07 09:49
svenwould be interesting if this reproduces with lockdep with hopefully some splat as well#asahi-dev · 2026-06-07 09:48
svenbeats me as well#asahi-dev · 2026-06-07 09:48
jannauI have no idea how the i2c timeout could fit into this#asahi-dev · 2026-06-07 09:46
jannauatc probe doesn't appear to fail from yesterday's post