#asahi-dev · 2025-04-13 20:23
sveni think so, but i didn't pay close attention#asahi-dev · 2025-04-13 20:17
svenso something somehow seems to corrupt lr there#asahi-dev · 2025-04-13 20:17
svenit seems to break when returning from mmu_secondary_setup to smp_secondary_entry#asahi-dev · 2025-04-13 20:09
svenhttps://f.svpe.dev/m1n1.bin that's the host one that almost always crashes when running run_guest.py for me#asahi-dev · 2025-04-13 20:05
svenoh, duh, this won't crash for you: the issue is somewhere in the host m1n1#asahi-dev · 2025-04-13 20:01
svenit's a raw binary, i switched to that to rule out macho issues#asahi-dev · 2025-04-13 19:54
sventhe m1n1 has one patch that might annoying for you, i've hardcoded the serial_str to dummy_serial_str because my m1n1 bootobject still has that old code#asahi-dev · 2025-04-13 19:54
svensee /msg#asahi-dev · 2025-04-13 19:44
sventhe last few times it does the weird jump somewhere in mmu_secondary_setup but before reaching smp_secondary_entry again#asahi-dev · 2025-04-13 19:44
sventhis smells like weird memory corruption or something like that to me but i can't figure out what causes it#asahi-dev · 2025-04-13 19:43
sventried to track down that weird exception some more, it seems to somehow jump to a weird PC sometime after reaching smp_secondary_entry#asahi-dev · 2025-04-13 17:07
svennope, looks like gP01 is correct#asahi-dev · 2025-04-13 17:02
svenugh, wait, did i break the binary search for the first gpio key? shouldn't that be gP00?#asahi-dev · 2025-04-13 16:56
sven[ 0.358617] macsmc-gpio macsmc-gpio: First GPIO key: gP01 (0x67503031)#asahi-dev · 2025-04-13 16:56
sven[ 0.356430] mfd-macsmc 23e400000.smc: Initialized (922 keys #KEY (0x234b4559) .. zETM (0x7a45544d))#asahi-dev · 2025-04-13 16:56
sven[ 0.354555] mfd-macsmc 23e400000.smc: RTKit: Initializing (protocol version 12)#asahi-dev · 2025-04-13 16:56
svenstill no idea what causes that exception above except that it's something in the host m1n1, but smc finally works again#asahi-dev · 2025-04-13 15:34
svenah, no, i just messed up and forgot to chainload#asahi-dev · 2025-04-13 15:31
sven*hv_start_secondary actually#asahi-dev · 2025-04-13 15:31
svenokay, wtf, adding more prints and iodev_console_flush to hv_enter_secondary seems to fix it#asahi-dev · 2025-04-13 13:37
svenbisect isn't very helpful either it seems. that resulted in two different commits that made no sense and where reverting also didn't fix anything#asahi-dev · 2025-04-13 13:27
svenweird#asahi-dev · 2025-04-13 13:27
svenraw payload also triggers a similar exception#asahi-dev · 2025-04-13 12:50
svenhuh, is the current m1n1 main hv on m1 broken for anyone else? https://gist.github.com/svenpeter42/f290098342f96c6c9d9ca35eaa6b6f02#asahi-dev · 2025-04-13 12:25
svenlet's see if i can also get smc in shape now#asahi-dev · 2025-04-13 12:24
svenhttps://github.com/AsahiLinux/linux/commits/b4/pasemi-fixes/ v2 of the pasemi fixes i'll send out tomorrow#asahi-dev · 2025-04-13 10:49
sventhe second one has to be merged through the arm64 (or whatever the correct subsystem is) tree first before i can pick up the dts changes#asahi-dev · 2025-04-13 10:48
svenalright, applied the first one#asahi-dev · 2025-04-13 10:01
svennickchan: got a link to that series that i haven't picked up yet? can't seem to find it :/#asahi-dev · 2025-04-10 16:14
svenand yeah, this would definitely still be interesting:)#asahi-dev · 2025-04-10 16:10
svenhttps://github.com/AsahiLinux/linux/blob/73e1d684c7ac8efe6a343741f973b0d1657c9434/arch/arm64/boot/dts/apple/t8103-j274.dts#L16 you should be able to get that compatible#asahi-dev · 2025-04-08 06:13
svenplease remind me on Sunday in case I forget #asahi-dev · 2025-04-08 06:12
svenyeah, will apply it this weekend #asahi-dev · 2025-04-07 17:54
svenlol#asahi-dev · 2025-04-07 07:07
svenif they’re all headed to the entry point you should see m1n1 (or parts of it) and then something might crash because we’re running the entry point again #asahi-dev · 2025-04-07 07:07
svenmischa85: when you tried to bring up the secondary cores did you see anything on the serial line? #asahi-dev · 2025-04-06 17:37
svenpity. i was hoping there was a chainload inbetween and the only issue was that m1n1_base changed#asahi-dev · 2025-04-06 17:37
svenok, that should've worked with the locked iorvbar values we checked earlier#asahi-dev · 2025-04-06 17:26
svenmischa85: when you tried to start the other cores did you do that with the m1n1 on disk or did you do a chainload to an updated m1n1 inbetween?#asahi-dev · 2025-04-06 11:34
svenbut first we need to figure out why wfi returns currently#asahi-dev · 2025-04-06 11:33
sven^-- that#asahi-dev · 2025-04-06 11:15
svenbut first you need to figure out what currently causes wfi to terminate#asahi-dev · 2025-04-06 11:14
svenyou can configure it to just trigger an interrupt which will wake you from wfi#asahi-dev · 2025-04-06 11:14
svenwe use that in the hv as well#asahi-dev · 2025-04-06 11:14
sveni'm talking about the hardware timer#asahi-dev · 2025-04-06 11:13
svenwhy do you need another cpu?#asahi-dev · 2025-04-06 11:06
svenor wait.. do we these days?#asahi-dev · 2025-04-06 11:05
svenI don’t think we use interrupts for usb #asahi-dev · 2025-04-06 10:53
svenif there's the HW magic that decides between retention/non-retention it will probably only move to non-retention if nothing happened for a longer time#asahi-dev · 2025-04-06 10:51
sventhere's probably still some event firing in the background, maybe some timer