#
✕ nick:Carlos_
#asahi-dev · 2026-07-17 16:17
Carlos_alright i will rebuild from the updated tree and continue
#asahi-dev · 2026-07-17 16:16
Carlos_right
#asahi-dev · 2026-07-17 16:15
Carlos_how did you catch that i have an m3 pro instead btw?
#asahi-dev · 2026-07-17 16:14
Carlos_chaos_princess: my mistake, yeah m3 pro. does that invalidate the tests you have me doing or still continue
#asahi-dev · 2026-07-13 18:20
Carlos_yes i am planning to take a deeper look at it once i'm off work today
#asahi-dev · 2026-07-13 18:06
Carlos_iirc from last night the counters were at 24MHz
#asahi-dev · 2026-07-13 17:57
Carlos_from whatever regs i probed, it did seem fine but the repeated spinlocks suggest there is something wrong still
#asahi-dev · 2026-07-13 17:46
Carlos_i haven't found proof of my hypothesis, since all timers i probed seemed to be properly virtualized, all in sync, but logically it makes sense that there is some path running through the python client and making the boot think a cpu stalled
#asahi-dev · 2026-07-13 17:44
Carlos_yeah i think that will make a difference. my hypothesis is that the hypervisor is introducing long waits in specific paths. so allowing longer timeout would help
#asahi-dev · 2026-07-13 17:42
Carlos_thanks nickchan, i'll try that out
#asahi-dev · 2026-07-13 17:04
Carlos_I don't think I tried just 0 or just 6 with my bkm yet. will try tonight
#asahi-dev · 2026-07-13 16:52
Carlos_chaos_princess: It varies every time, but most of the time it's ticket spinlock. I am using 2 cpus to boot (0,6). pmgr wasn't happy with just one, it complained about not enough cpu complexes. will be able to look more later today.