#
✕ nick:sven
#asahi-dev · 2025-06-04 07:30
sven*offsets
#asahi-dev · 2025-06-04 07:29
svenI just don’t trust the ADT at all
#asahi-dev · 2025-06-04 07:29
svenI’d really double check if any of the offers actually changed
#asahi-dev · 2025-06-04 07:26
sveniirc robh also suggested that he would NAK aic3 because if the hw is changing once per generation anyway we may as well only use tXXXX-aic
#asahi-dev · 2025-06-03 13:27
svenI know that v3 introduced some more properties for register offsets but they seems similar to v2
#asahi-dev · 2025-06-03 13:27
sventhe adt node e.g. has a version property somewhere
#asahi-dev · 2025-06-03 13:27
sventhey work differently there
#asahi-dev · 2025-06-03 13:27
svenreally, don’t trust the ADT for stuff like compatibles
#asahi-dev · 2025-06-03 13:26
svenit’s at least v2 for m3, maybe even v3
#asahi-dev · 2025-06-02 19:00
svenADT had many weird hacks and cannot be trusted but at least address/size cells have been consistent everywhere I looked fwiw
#asahi-dev · 2025-06-01 17:23
svenif someone's looking for a yak to shave: we should get rid of all the "default ARCH_APPLE" that snuck into various Kconfig files and instead move them with m (and only y if required) to arm64 defconfig
#asahi-dev · 2025-06-01 14:50
svenno. those names more or less come from xnus debug output so your guess is as good as mine
#asahi-dev · 2025-06-01 12:32
svenhttps://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git/log/?h=wip/atcphy mostly happy with it now except for commit descriptions
#asahi-dev · 2025-06-01 11:08
sven(either that or people have a bootrom exploit which is much less likely)
#asahi-dev · 2025-06-01 11:08
svenwe actually know that these must've escaped containment because that's usually where those iboot keys come from
#asahi-dev · 2025-06-01 11:07
svenprobably, but i really don't want touch those devices
#asahi-dev · 2025-06-01 11:06
svenit only works on debug fused development SoCs
#asahi-dev · 2025-06-01 11:05
svenoh, you get swd via usb ports. it's just completely useless
#asahi-dev · 2025-06-01 11:04
svennow I wish I actually had SWD. would be interesting to see what the other cores are up to just when the one core tries to jump to 0x20...
#asahi-dev · 2025-06-01 11:00
svenit's also unrelated to deep wfi messing some state up - i commented out the wfi instruction and that doesn't make any difference either
#asahi-dev · 2025-06-01 10:57
svenadding dc_civac_range there still results in that crash
#asahi-dev · 2025-06-01 10:16
svenso core #2 entering deep_wfi and then overwriting core #1's stack would explain this but I just don't see any evidence of wrong stack pointers in any core :/
#asahi-dev · 2025-05-31 22:52
sveni think
#asahi-dev · 2025-05-31 22:52
sventhat would also explain where 0x2000000 comes from because that's the original value of SYS_IMP_APL_CYC_OVRD stored on the stack next to the saved LR inside deep_wfi
#asahi-dev · 2025-05-31 22:35
svenhrm, so this abort could happen if any of the other cores is still stuck in smp_secondary_entry and has the same stack. it looks like the SPs are correct on initial smp_secondary_entry though and yet it still crashes
#asahi-dev · 2025-05-31 19:08
svenstill crashes with the same symptoms. probably a good idea to add that additional flush anyway
#asahi-dev · 2025-05-31 19:06
svenlet's see if that changes anything
#asahi-dev · 2025-05-31 19:06
svenhuh, yeah
#asahi-dev · 2025-05-31 17:23
svendoesn't the dc_civac_range(&_reset_stack, sizeof(void *)); do just that?
#asahi-dev · 2025-05-31 17:14
sveni checked the assembly. it should be a frame pointer there, it just also ends up being corrupted somehow
#asahi-dev · 2025-05-31 15:51
svenyeah, that guess made sense to me. but it reliably points to the instruction after bl deep_wfi inside smp_secondary_entry for me
#asahi-dev · 2025-05-31 15:30
svenwhich, uh, also doesn't make any sense to me
#asahi-dev · 2025-05-31 15:29
sveni just checked and for me x29 doesn't point to the dummy stack but to the instruction after the branch to deep_wfi
#asahi-dev · 2025-05-31 15:16
svenit shouldn't even be using dummy_stack at that point
#asahi-dev · 2025-05-31 14:50
sventhese probably result in something else that isn't as critical being overwritten
#asahi-dev · 2025-05-31 14:49
sventhere are a bunch of workarounds, see https://github.com/AsahiLinux/m1n1/issues/463
#asahi-dev · 2025-05-31 14:49
svenit happens when the other cores are brought up in the guest almost every time
#asahi-dev · 2025-05-31 14:48
sveni suspect that issue has been in m1n1 for a very long time. only some change in the last months made it much more likely
#asahi-dev · 2025-05-31 13:51
svenagreed
#asahi-dev · 2025-05-31 13:47
svenugh.. that's going to be very annoying
#asahi-dev · 2025-05-31 13:34
svenkettenis: ^--
#asahi-dev · 2025-05-31 13:33
svenah, one more possible thing for the m1n1 release: do we want to add that compatible fixup for pmu vs. pmic to m1n1?
#asahi-dev · 2025-05-31 09:03
svenah, jannau already reviewed it and had some comments :)
#asahi-dev · 2025-05-31 09:02
svencan we just merge that smbios MR or is there anything that needs work there?
#asahi-dev · 2025-05-31 08:59
svenfine with me
#asahi-dev · 2025-05-31 08:29
svenI don’t have high hopes we’ll fix that mmu_setup_secondary abort anytime soon but that’s also not release blocking imho since it only affects the hv
#asahi-dev · 2025-05-31 08:28
svenI’d defer the chickens cleanup and maybe gpu initdata to the next one
#asahi-dev · 2025-05-31 08:27
svenchadmed_: imho the atcphy fuses stuff would make sense since it won’t break anything
#asahi-dev · 2025-05-31 08:27
svenI think so, but I need to go over everything once more anyway. tipd still needs to be cleaned up a bit as well
#asahi-dev · 2025-05-30 13:31
svenah.. no, nvm.

plus ›