#asahi-dev · 2026-05-06 18:51
jannauthe code is `for cpu in u.adt["cpus"]` and I guess the print before#asahi-dev · 2026-05-06 18:49
jannauno, I would put the code under `if rvbar != u.base:`#asahi-dev · 2026-05-06 18:47
jannaufor chainload.py you could skip setting rvbar if `rvbar == u.base`. it should not not differ unless someone plays with the entry point or changes how m1n1.macho is linked. In both cases it's fine if said person keeps the broken pieces#asahi-dev · 2026-05-06 18:40
jannauyes, the t8132 CPU start offset is not wrong. I was wondering whether keeping it causes troubles#asahi-dev · 2026-05-06 18:34
jannaushall I revert "smp: add CPU_START_OFF for T8132" as well?#asahi-dev · 2026-05-06 18:22
jannauand let's start fresh with what we learned#asahi-dev · 2026-05-06 18:22
jannauI think I'll close my PR and revert the commits from #536#asahi-dev · 2026-05-06 18:17
jannauall P-cores or just the boot CPU?#asahi-dev · 2026-05-06 18:16
jannautested on M1#asahi-dev · 2026-05-06 18:16
jannauas suspected, BIT(0) is set on boot on all cores but clearing it is possible as long as the core is not running#asahi-dev · 2026-05-06 18:08
jannaucompletely unrelated to its value#asahi-dev · 2026-05-06 18:07
jannauI suspect it is just not writable at all on M4#asahi-dev · 2026-05-06 18:04
jannauit == BIT(0)#asahi-dev · 2026-05-06 18:04
jannauI suspect it locks rvbar only when the CPU is running#asahi-dev · 2026-05-06 18:04
jannauI suspect it's not only M2 but M1 and M2 as well, we just haven't noticed before because we cleared the bit before the secondaries were running#asahi-dev · 2026-05-06 18:02
jannauWhat exactly? we currently need BIT(0) cleared for HV because HV needs to set RVBAR to guest entry#asahi-dev · 2026-05-06 17:59
jannauso the "locked" bit was always cleared for the secondary by writing _vectors_start#asahi-dev · 2026-05-06 17:57
jannauin smp_start_secondaries#asahi-dev · 2026-05-06 17:57
jannauthere is a check for BIT(0) on the boot CPU#asahi-dev · 2026-05-06 17:55
jannauthe entire register is writable, only on the the boot CPU it SErrors#asahi-dev · 2026-05-06 17:51
jannauit's not, I can clear BIT(0)#asahi-dev · 2026-05-06 17:50
jannaucpu0: 0x10010002cb8001, cpu4: 0x110010002cb8001#asahi-dev · 2026-05-06 17:44
jannauit's still broken with that fixed and just reverting the HV part is not enough either#asahi-dev · 2026-05-06 17:41
jannauno, HV fails on m3 where it was previously working#asahi-dev · 2026-05-06 17:35
jannauI don't think the HV change can ever be correct when RVBAR is locked. guest entry will differ by definition from rvbar#asahi-dev · 2026-05-06 17:31
jannauyuka: on which device did you test https://github.com/AsahiLinux/m1n1/pull/536 ?#asahi-dev · 2026-05-06 13:42
jannau"impl_locked"?#asahi-dev · 2026-05-06 13:04
jannauflokli: m4 pro mac mini works here (using 26.5 RC), you might need to disable usb_init(), that was throwing exceptions#asahi-dev · 2026-05-06 13:02
jannauI got annoyed by kmutil configure-boot: https://github.com/AsahiLinux/m1n1/pull/573#asahi-dev · 2026-05-06 12:51
jannauI don't think we need another feature for this but should come up with a different name#asahi-dev · 2026-05-06 11:44
jannauI can try later#asahi-dev · 2026-05-06 11:44
jannauflokli: how quickly does it arrive at the macsetup? if it is within a few seconds it sounds more like there is an issue with the boot object#asahi-dev · 2026-05-05 21:15
jannauM3 Pro is untested, M3 Max/Ultra should work#asahi-dev · 2026-05-05 21:15
jannauI pushed initial M3 Pro and M3 Max/Ultra device trees to asahi-wip. doesn't do much besides booting to serial console#asahi-dev · 2026-05-05 20:48
jannaualso helpful for updating macos if it is macos 15.x#asahi-dev · 2026-05-05 20:47
jannauor just revert to the macos kernel with bputil -n#asahi-dev · 2026-05-05 15:34
jannauand compare it with m1n1.bin#asahi-dev · 2026-05-05 15:34
jannauor objdump it#asahi-dev · 2026-05-05 15:29
jannautry editing m1n1's start.S and put "b ." at the top of _start#asahi-dev · 2026-05-05 15:28
jannauI think the entry point is the start vector table and not a function#asahi-dev · 2026-05-05 15:27
jannauyou used the offset of your _start as kmutil --entry-point?#asahi-dev · 2026-05-05 15:18
jannauwith an endless loop as start the second mac isn't really helpful. I was going to ask for serial logs with EARLY uart#asahi-dev · 2026-05-05 15:17
jannauwhen does it boot loop? before the boot chime has completely ended?#asahi-dev · 2026-05-05 15:15
jannaudo you have a second apple silicon mac (possibly an intel mac with macos 26)#asahi-dev · 2026-05-05 10:10
jannaufl0_id: does m1n1's cpufreq init work for you? for me applying cpu-fixed-freq-pll-relock on perf cores breaks/hangs#asahi-dev · 2026-05-05 07:56
jannauif boot.bin.old doesn't work, you can try the one from https://github.com/AsahiLinux/m1n1/actions/runs/25250750280#asahi-dev · 2026-05-05 07:55
jannauthe stage2 should log as well#asahi-dev · 2026-05-05 07:52
jannauwith csrutil disable and boot-args=-v it should log to the screen#asahi-dev · 2026-05-05 07:51
jannaudoes it try to chainload anything and print an error?#asahi-dev · 2026-05-05 07:15
jannauFelix[m]1: generally yes, M3 Pro/Max/Ultra support is behind but I'm planning on bringing it to the same lavel in thext few days