#
…

2021-12-05

04:00PhilippvK has joined #asahi-re
04:04phiologe has quit [Ping timeout: 480 seconds]
06:46maor26 has joined #asahi-re
07:43the_lanetly_052__ has joined #asahi-re
08:12the_lanetly_052__ has quit [Ping timeout: 480 seconds]
08:58Dcow has joined #asahi-re
08:58Dcow_ has quit [Read error: Connection reset by peer]
09:16riker77 has quit [Quit: Quitting IRC - gone for good...]
09:17the_lanetly_052__ has joined #asahi-re
09:33gwyef has joined #asahi-re
09:46gwyef has quit [Remote host closed the connection]
09:54riker77 has joined #asahi-re
10:51the_lanetly_052___ has joined #asahi-re
10:55svenmarcan: so here's something that may be going on: the rtkit reset vector checks some kind of resume flag and if has an unexpected value (0xbaadf1ac) it'll go to a while(1); loop. and i think it'll always have the unexpected value once rtkit is up and running
10:56svenand i think if you send that powerdown message it'll overwrite that value to something else
10:56svenand then a reset will work
10:56svenstill need to confirm this though, the code is a bit annoying to follow
10:58the_lanetly_052__ has quit [Ping timeout: 480 seconds]
12:53svenhrm, or maybe not. it changes VBAR at some point
12:59svenbut i guess that might also be reset to its original value if the PMGR reset is a true hard reset
14:54the_lanetly_052__ has joined #asahi-re
15:00the_lanetly_052___ has quit [Ping timeout: 480 seconds]
15:35sikkiladho[m] has joined #asahi-re
16:15steve has joined #asahi-re
16:15steve is now known as Guest7639
16:15the_lanetly_052 has joined #asahi-re
16:20the_lanetly_052__ has quit [Ping timeout: 480 seconds]
16:24Mary has quit [Quit: The Lounge - https://thelounge.chat]
16:24Mary has joined #asahi-re
16:26Mary has quit []
16:26Mary has joined #asahi-re
16:26Mary has quit []
16:27Mary has joined #asahi-re
16:33the_lanetly_052 has quit [Ping timeout: 480 seconds]
17:04the_lanetly_052 has joined #asahi-re
17:34maor26 has quit [Quit: Leaving]
20:14marcansven: it's weird that sometimes I got it to start the rtkit init and fail later
20:14marcanbut I was also playing with sending NMIs; not sure if that's required to cause that to happen (and it's not consistent anyway)
20:15sventhe mmi is another while(1); loop in the firmware I think
20:16svenor, well
20:16svenit'll try to send a crashlog and then spin forever
20:17marcanI haven't seen it try to send a crashlog
20:17svendid you send the nmi after it got a crashlog buffer?
22:17svenhrm, i think it's actually that flag in the data section which we can't access for DCP :(
22:17sven*for ANS
22:18sveni'll check tomorrow if i can revive any of the coprocs where we can access that flag
22:20sven(and unless there's something like KTRR this also gives trivial code exec on all coprocs where we can write to the data section by overwriting the stuff it stores in that section during hibernate)
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:01yrlf has joined #asahi-re
23:06yuyichao_ has quit [Quit: Konversation terminated!]
23:07yuyichao has joined #asahi-re
…