ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
<sven>
see logs from a few days ago, _something_ corrupts LR I think in the smp_call4 -> [other core] -> smp_secondary_entry -> mmu_secondary_setup path
<sven>
couldn't bisect it to a specific commit and no one else seems to have run into that
<sven>
but when i shared my m1n1.bin with jannau it also crashed for him
<sven>
but it still works fine for my very outdated stage1 m1n1
mischa85 has quit [Ping timeout: 480 seconds]
hdbngr has joined #asahi-dev
<chaos_princess>
Any specific reason to keep simple-mfd-spmi driver around? It only ever gets used together with spmi-mfd-nvmem, and i do not see that much value in delineating specific nvmem ranges
mischa85 has joined #asahi-dev
pb17 has joined #asahi-dev
hdbngr has quit [Ping timeout: 480 seconds]
<nickchan>
chaos_princess: I could reuse it for other purposes I suppose
<chaos_princess>
like?
<chaos_princess>
i am asking since i am considering dropping it
mischa85 has quit [Ping timeout: 480 seconds]
<nickchan>
chaos_princess: I have verified the existence of an rtc in a11's spmi dialog da2422 pmic and is able to read time from it
<nickchan>
a rtc that can count 194 of time and then a 32-bit value in the pmic nvmem to store the rest of the time
<nickchan>
194 days of time
jcat has joined #asahi-dev
hdbngr has joined #asahi-dev
<chaos_princess>
so i should keep the mfd then
<chaos_princess>
?
<nickchan>
you should keep it
<nickchan>
and the reason i have not implemented that rtc just yet that iOS *will* overwrite the time every boot
<nickchan>
can even reproduce by just setting the time in an iOS ramdisk
<nickchan>
it's doing that because the 194 days counter cannot be reset and time becoming wrong just because iOS is not running when that counter overflow is not great
<nickchan>
more specifically, overwrite the rest of the time stored in the pmic nvmem
<chaos_princess>
do you not have the smc clock there?
<nickchan>
all things considered it probably does exist there
<chaos_princess>
Doesn't look like it has anything clock related
<nickchan>
#KEY reads: 603 so this is every single key
hdbngr has joined #asahi-dev
pb17 has quit [Ping timeout: 480 seconds]
hdbngr has quit [Ping timeout: 480 seconds]
___nick___ has joined #asahi-dev
pb17 has joined #asahi-dev
hdbngr has joined #asahi-dev
<jannau>
the broken resume seems to lock related. CPUs seems to soft lockup after resume
<sven>
broken resume?
<jannau>
in 6.14.2, not reliebly broken
<sven>
ah
<jannau>
let's hope lockdep finds ssomething
<jannau>
no compliants :(
hdbngr has quit [Ping timeout: 480 seconds]
<jannau>
generating irqs seem to help. after pressing nothing happens except for the smc button press log lines but pressing keys repeated brings the display back on
<jannau>
system is half broken though. touchpad input does not work continously
<jannau>
as if irqs to some CPU cores are not arriving (due to the soft lockup). this is m2 so irqs are distributed by aic on the cores
hdbngr has joined #asahi-dev
hdbngr has quit [Ping timeout: 480 seconds]
okb_ has joined #asahi-dev
hdbngr has joined #asahi-dev
okb has quit [Ping timeout: 480 seconds]
<jannau>
apaprently an adp interrupt storm, so macbook pro 13-inch specific
<chaos_princess>
i remember there being some issues with suspend on an early version of the series, so maybe what i did just masked it instead of fixing
mischa85 has quit [Ping timeout: 480 seconds]
<jannau>
still broken. I commented the whole pm_ops
hdbngr has joined #asahi-dev
hdbngr has quit [Ping timeout: 480 seconds]
mischa85 has joined #asahi-dev
hdbngr has joined #asahi-dev
pb17 has quit [Ping timeout: 480 seconds]
mischa85 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi-dev
Larwive has quit [Remote host closed the connection]
Larwive has joined #asahi-dev
kraem has quit [Ping timeout: 480 seconds]
___nick___ has quit [Remote host closed the connection]
<sven>
jannau: ugh.. looks like building with gcc on either a macos or a linux host doesn't run into the same issue
Pokemod97 has joined #asahi-dev
Pokemod970 has quit [Read error: Connection reset by peer]
<sven>
assembly looks very different so this might also just be similar to adding printfs somewhere