#asahi-dev · 2026-01-29 00:38
fl0_id___prob should start fresh tomorrow#asahi-dev · 2026-01-29 00:35
fl0_id___pursuant to git I shouldn't have any other changes, but sth must be wrong...#asahi-dev · 2026-01-29 00:34
fl0_id___argh. I thought I had only committed my changes, but now nothing works atm, it doesn't even find the aic#asahi-dev · 2026-01-27 02:28
fl0_id___*not merged yet i mean#asahi-dev · 2026-01-27 02:28
fl0_id___iirc#asahi-dev · 2026-01-27 02:28
fl0_id___fairydust is only for that one specifc thing#asahi-dev · 2026-01-27 02:27
fl0_id___jsk asahi-wip is more current, but as most m3 stuff is not merged there, doesn't rly matter probably#asahi-dev · 2026-01-20 17:07
fl0_id___yeah but you have to install that first#asahi-dev · 2026-01-20 17:05
fl0_id___touch, how broken? #asahi-dev · 2026-01-20 15:08
fl0_id___yuka, do you have this up somewhere, just in case it helps me? I will probably also test some mcc.c changes, as tz_regs seem different, and i don't know what device was used for those.#asahi-dev · 2026-01-19 00:02
fl0_id___could also put up the whole log, but only if you think there might be sth interesting#asahi-dev · 2026-01-18 23:47
fl0_id___guest#asahi-dev · 2026-01-18 23:40
fl0_id___but smt in kernel is still enabled#asahi-dev · 2026-01-18 23:39
fl0_id___noopwafel, based on device tree and m1n1 output when loading kernel, I'm only using 1 core (cpu 4, first p core iirc)#asahi-dev · 2026-01-18 23:38
fl0_id___https://www.pastery.net/mkkeuj/#asahi-dev · 2026-01-18 23:35
fl0_id___right that makes sense. but as someone suggested memory layout, that could it be anything else there? on the last experiments, got a more specific backtrackt, where it crashed when printing sth.#asahi-dev · 2026-01-18 22:49
fl0_id___s/resets/restarts/#asahi-dev · 2026-01-18 22:48
fl0_id___https://www.pastery.net/hbgbry/#asahi-dev · 2026-01-18 22:48
fl0_id___in the sense of confirming whether I have a memory problem - should memdump.py in experiments not just work? it crashes almost immediately and resets the proxy.#asahi-dev · 2026-01-18 17:18
fl0_id___a few days ago I think someone suggested that the memory layout might be different on m3 max. should this be visible in adts?#asahi-dev · 2026-01-17 18:53
fl0_id___and do let me know if you figure out to force-print sth in early kernel boot... I rather suspect it doesn't work because of some memory access weirdness like trying to acccess high memory regions#asahi-dev · 2026-01-17 18:51
fl0_id___yuka, mmmh, I also thought the micro-usb of cs should me able to connect to m1n1, like to use before usb is up. as the readme says "It's main use it to allow interacting with the Asahi m1n1 firmware, such as tethered booting"#asahi-dev · 2026-01-17 18:48
fl0_id___integralpilot yes CONFIG_APPLE_AIC=y#asahi-dev · 2026-01-17 01:47
fl0_id___and I also put anohter printk which is also not shown#asahi-dev · 2026-01-17 01:38
fl0_id___there should at least be pr_notice("Kernel command line: %s\n", saved_command_line); before the problem section#asahi-dev · 2026-01-17 01:33
fl0_id___this is my cs serial output https://www.pastery.net/ganapx/#asahi-dev · 2026-01-17 01:11
fl0_id___I should prob use the cs m1n1 connection though#asahi-dev · 2026-01-17 01:10
fl0_id___yuka, no this stacktrace from hv over m1n1 usb#asahi-dev · 2026-01-17 01:07
fl0_id___yuka, it seems like this is not available for arm64, no?#asahi-dev · 2026-01-17 00:56
fl0_id___https://www.pastery.net/yenhwv/#asahi-dev · 2026-01-17 00:56
fl0_id___at least I have symbols now after disabling random base#asahi-dev · 2026-01-17 00:56
fl0_id___yes, after vectoring to next stage#asahi-dev · 2026-01-17 00:56
fl0_id___though I didn't trace it to head.S but build_all_zonelists#asahi-dev · 2026-01-17 00:55
fl0_id___yuka, this seems very similar to what i am seeing#asahi-dev · 2026-01-10 16:15
fl0_id___ofc it could be a normal loop that eventually ends, but I've gone through a few...#asahi-dev · 2026-01-10 16:14
fl0_id___have to go do some other things for a bit#asahi-dev · 2026-01-10 16:14
fl0_id___yeah it's a loop. I have a small annotated snippet here. https://www.pastery.net/kfnwvt/ I'll try to piece together a full assembly loop output later.#asahi-dev · 2026-01-10 15:38
fl0_id___ah i was looking for ctx i guess#asahi-dev · 2026-01-10 15:36
fl0_id___should there be any output for step ?#asahi-dev · 2026-01-10 15:32
fl0_id___ok#asahi-dev · 2026-01-10 15:32
fl0_id___i'll try single stepping again, before it didn't work properly but maybe just the breakpoint didn't work#asahi-dev · 2026-01-10 15:30
fl0_id___back trace is a lot of - 0xffffb75c53edc534 (kimage_limit+0x375bd00dc534)#asahi-dev · 2026-01-10 15:30
fl0_id___sven, it seems like a loop. after the last hvc instruct it reaches, I continue and then there's a blank line and nothing else.