#
…

2026-07-18

00:05maettu102 has quit [Quit: brb]
00:05maettu102 has joined #asahi-re
00:14Mary has quit [Quit: .]
00:14Mary has joined #asahi-re
01:07hdbngr has joined #asahi-re
01:16hdbngr has quit [Ping timeout: 480 seconds]
01:33r0ni has quit [Ping timeout: 480 seconds]
01:49hdbngr has joined #asahi-re
01:58hdbngr has quit [Ping timeout: 480 seconds]
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-re
02:12r0ni has joined #asahi-re
02:27nela has quit [Ping timeout: 480 seconds]
02:30nela has joined #asahi-re
02:33nnym has quit [Ping timeout: 480 seconds]
02:34hdbngr has joined #asahi-re
02:42hdbngr has quit [Ping timeout: 480 seconds]
02:50hdbngr has joined #asahi-re
02:59hdbngr has quit [Ping timeout: 480 seconds]
03:07hdbngr has joined #asahi-re
03:15hdbngr has quit [Ping timeout: 480 seconds]
03:16pb17 has quit [Remote host closed the connection]
03:16pb17 has joined #asahi-re
03:58yuyichao_ has joined #asahi-re
03:59hdbngr has joined #asahi-re
04:03yuyichao has quit [Ping timeout: 480 seconds]
04:07hdbngr has quit [Ping timeout: 480 seconds]
04:20hdbngr has joined #asahi-re
04:28hdbngr has quit [Ping timeout: 480 seconds]
04:37hdbngr has joined #asahi-re
04:46hdbngr has quit [Ping timeout: 480 seconds]
04:51hdbngr has joined #asahi-re
05:00hdbngr has quit [Ping timeout: 480 seconds]
05:15rosalyntg has quit [Read error: Connection reset by peer]
05:15rosalyntg has joined #asahi-re
05:16hdbngr has joined #asahi-re
05:25hdbngr has quit [Ping timeout: 480 seconds]
05:52hdbngr has joined #asahi-re
06:01hdbngr has quit [Ping timeout: 480 seconds]
06:05hdbngr has joined #asahi-re
06:09mattia013 has quit [Remote host closed the connection]
06:11mattia013 has joined #asahi-re
06:14hdbngr has quit [Ping timeout: 480 seconds]
06:29hdbngr has joined #asahi-re
06:33rosalyntg has quit [Ping timeout: 480 seconds]
06:36pb17 has quit [Ping timeout: 480 seconds]
06:37hdbngr has quit [Ping timeout: 480 seconds]
06:42pb17 has joined #asahi-re
06:53hdbngr has joined #asahi-re
07:00weirdtreething has quit [Remote host closed the connection]
07:00weirdtreething has joined #asahi-re
07:02hdbngr has quit [Ping timeout: 480 seconds]
07:38jtingiris has quit [Quit: ZNC 1.10.1 - https://znc.in]
07:38jtingiris has joined #asahi-re
07:54hdbngr has joined #asahi-re
08:03hdbngr has quit [Ping timeout: 480 seconds]
08:39hdbngr has joined #asahi-re
09:23hdbngr_ has joined #asahi-re
09:27hdbngr has quit [Ping timeout: 480 seconds]
10:16ddxtanx has quit [Remote host closed the connection]
10:17hdbngr_ has quit [Quit: leaving]
10:51scottjg4 has quit [Read error: Connection reset by peer]
10:51scottjg4 has joined #asahi-re
12:57mini has quit [Quit: The Lounge - https://thelounge.chat]
12:59mini has joined #asahi-re
13:33chadmed has quit [Remote host closed the connection]
13:38chadmed has joined #asahi-re
17:17amarioguyyuka: erm....seems like when i try to connect to the uartproxy the shell just spams '> 0'
17:17amarioguythis is on t8142, j704ap
17:17yukasorry, I forgot I always used to comment this out when working with M5
17:18yuka(the proxyclient side is enough to fix your issue, no need to re-install m1n1)
17:42amarioguyyep, now the proxy shell works
17:43amarioguynow why tf when i try to read from cpu-impl-reg (IORVBAR region) does it cause an serror loop...
17:44amarioguyok definitely not the iorvbar region...but seems like trying to just read other stuff outside of that can result in an serror loop
17:44amarioguyi'm trying to dump some of that area for context
17:47amarioguy(the problem isn't necessarily the serrors themselves, more that m1n1 seems to be struggling to recover from them...)
17:59nela has quit [Quit: Ping timeout (120 seconds)]
18:00nnym has joined #asahi-re
18:04nela has joined #asahi-re
18:51amarioguyah i see why simple local fix should do it
18:52yukaI'm interested in what was the problem
18:53yukaI haven't seen this issue before
18:55amarioguyyuka: tl;dr is that serrors don't have the exception guard code that the synchronous exception path does
18:55amarioguymy "fix" in quote marks is basically just to add the logic from sync exceptions for the purposes of dumping these registers
18:56amarioguyi say "in quote marks" because i'm sure there's probably a good reason serror handling doesn't have the exception guard code
18:56amarioguyi can PR that small addition if upstream wants it though
18:57amarioguyso every time it was doing the ERET, it was returning to the exact same instruction that was SError'ing
18:59yukaSError does not usually occur at the instruction that caused it
18:59yukait's asynchronous
18:59yukaso the instruction which caused it already passed
19:00amarioguyyea..............if only it were that simple
19:01amarioguysee it turns out on apple platforms (some previous experience with some m1n1 testing a few years ago gave me similar issues too) accessing some memory addresses wrong basically throws an serror that's synchronous with the instruction
19:01amarioguybut yes, in the general case you're correct
19:02chaos_princesscan you figure it out from that register that has extra error info?
19:03amarioguyL2C_ERR_STS: 0x200
19:03amarioguyL2C_ERR_ADR: 0x1a80000211010000
19:03amarioguyL2C_ERR_INF: 0x1400100007
19:03amarioguyESR: 0xbe000000 (SError)
19:03amarioguythat's an example but most things that aren't IORVBAR or very specific addresses which are known to exist seem to throw these
19:04amarioguyfor example 0x210F80040 (from iBoot disasm) exists and returns a good value but 0x2110400D0 does not
19:04amarioguythe INF lower bit values seem to be consistent as well
19:05amarioguyi did try 32-bit access width on this same addr, lower nibble became 3 but otherwise not much different)
19:07amarioguynot saying that those registers do exist, more trying to figure out...is doing elr += 4 a good idea for the read8/read16/read32/read64 case specifically?
19:07amarioguyor is there a better way where m1n1 doesn't keep looping the serror
19:09chaos_princessi guess yes, those specific instructions can be marked with labels or sth, and if it is there - bump the elr
19:24amarioguyso ummmmmmmmmmm seems like disabling serrors entirely works?
19:25amarioguytried an experiment where i disabled SErrors in DAIF, read one of the known bad addresses, it read back 0 for it (i doubt it actually read anything however it works at least for suppressing the problem here)
19:26amarioguy(when i unmasked the serrors, i started getting that flood of serrors again)
19:26amarioguyyuka: an update ^
19:26amarioguyat least i can dump the registers now, so i'll take it i suppose
19:38amarioguychaos_princess, yuka: going to post the register dumps to gists along with the diff (between the two beta builds, this is related to RE'ing the mechanism for sysreg locks), should i leave sync exceptions on in DAIF or not?
19:38amarioguydid a trial run and some regs were giving sync exceptions, unsure if i should leave those on or not, whatever's more useful
19:39chaos_princessprobably have them on, we handle sync exceptions correctly, right?
19:39amarioguyyea, sync exceptions are handled well, those recover just fine
20:16amarioguy34 meg file....
20:17amarioguyi'll post the diff first (in a gist), then i'll send the full raw files separately
20:17yukaHaving tooling in m1n1 for dumping mmio areas which partially cause SErrors would be very useful
20:38amarioguyok got both dumps, what diff format do you all prefer
20:38amarioguyi don't imagine the standard diff a.txt b.txt is that intuitive...
20:44amarioguyah -u makes it more intuitive looking, gotcha, --color as well
20:48amarioguyhere's the diff of that dumped region between the builds
20:49amarioguyaccesses to 0x211ea2000 seemed to hang, i skipped to 0x211f00000 as i was unsure if other regs in that region also hung m1n1 and didn't have the time to test those in between
20:49amarioguyi hope this is helpful for people wanting to RE the sysreg lock mechanism
20:49amarioguyraw files going up shortly (they don't fit in a github gist)
20:50amarioguyany recommended pastebin site?
20:51amarioguy(pastebin itself seems obvious...but unsure if it's that great ngl since iirc it started having some login walls)
20:55enverbalalic has joined #asahi-re
21:05amarioguyfor 25G5043d
21:05amarioguyfor 25G5028f
21:08amarioguymy experiment python file i used for doing the dumps
21:08amarioguyplease ping if anyone notices issues with the methodology or with the actual dumps themselves
21:10amarioguyneed to work on some other stuff now, but will respond later to stuff that comes up
21:17amarioguybtw important note, i think a bunch of them being 0 is often symptomatic of those registers normally triggering SErrors
21:47crabbedhaloablut has quit []
21:47crabbedhaloablut has joined #asahi-re
22:00chadmed has quit [Quit: Konversation terminated!]
22:29WindowPain has quit [Read error: Connection reset by peer]
22:31WindowPain has joined #asahi-re
23:27enverbalalic has quit [Quit: enverbalalic]
23:53copticcurse has joined #asahi-re
23:56nela has quit [Quit: Ping timeout (120 seconds)]
…