| 26 Jun 2025 |
 Christian Theune | yeah, that's what i was trying to figure out | 20:03:46 |
| Christian Theune | but the other one at least has message ids | 20:03:56 |
| Christian Theune | i can google for those | 20:03:59 |
| Christian Theune | maybe i can find the raw message elsewhere | 20:04:05 |
 Alyssa Ross | raitobezariuscould presumably also forward it to you as an attachment | 20:04:32 |
| Christian Theune | yeah, that might be easiest. | 20:05:59 |
| Christian Theune | raitobezarius: i'll dm you | 20:06:05 |
| Christian Theune | ah, and apparently i can just apply the two mentioned commits. i'll try that out for my setup | 20:08:13 |
| Christian Theune | ah, there's only one commit id, so hunting the other patch ... | 20:10:57 |
| Christian Theune | alright, took this one (https://lkml.org/lkml/2024/10/21/1621) and building our tests with it now | 20:14:04 |
| Christian Theune | eta 25 minutes | 20:14:40 |
 raitobezarius | In reply to @qyliss:fairydust.space
raitobezariuscould presumably also forward it to you as an attachment I have the mbox on another server right now :< | 20:15:00 |
| Christian Theune | no worries, fill me in when you can. if lore comes back i should be able to get the message myself. | 20:15:57 |
| Christian Theune | yup. | 20:38:19 |
| Christian Theune | my test is clean now, too, with 6.12.34, and the revert and workaround you mentioned. | 20:38:35 |
| Christian Theune | ah, lore is back | 20:41:08 |
| Christian Theune | kinda ... | 20:42:03 |
| Christian Theune | guess i was just lucky with that 1 request. | 20:42:14 |
| Christian Theune | well, off to bed now for me. i'll try to respond tomorrow in the mailing list thread. | 20:43:24 |
| raitobezarius | In reply to @ctheune:matrix.flyingcircus.io
my test is clean now, too, with 6.12.34, and the revert and workaround you mentioned. Happy to hear that my root cause analysis seems valid! | 21:19:05 |
|  @sofie:fsfe.org left the room. | 22:16:52 |
| 27 Jun 2025 |
| Christian Theune | lore is back and i'm writing a follow up mail now | 05:30:32 |
 Zhaofeng Li | Oh wow, thanks for bisecting it. Is there a canonical Lix-side discussion that I can link to? | 06:22:07 |
| Christian Theune | raitobezarius: i'm trying out the patch combination that dominique suggested and will give him feedback in the next hour. but i'll stress that I have no semantically valid analysis of those patches and am just being a monkey, so I have no idea what makes more sense regarding the logic of the changes themselves. | 07:52:52 |
| raitobezarius | Here: https://matrix.to/#/!lymvtcwDJ7ZA9Npq:lix.systems/$wLqRlm7-iNmrkN2Tcn--Tmi92id4wgvKC5APwiEYYgw?via=lix.systems&via=matrix.org&via=catgirl.cloud but it's mostly me melting down | 10:05:47 |
| raitobezarius | Yeah, I will jump in when I have some time, I'm waiting for David to chime in because they probably have a better understanding, if nothing happens, I may try my hand at fixing it but this will take some time | 10:06:35 |
| raitobezarius | in our case, we just pinned 6.6 for now and called it a day | 10:06:49 |
| Christian Theune | yeah, we're running our affected tests without v9fs because we're currently upgrading the fleet to 6.12. we've been running with 6.12 in staging for a while now (but the tests were pinned on 6.6 due to combinatorial explosion) and are investing another potential kernel issue that seems to go away with 6.12 ... | 10:07:54 |
| Christian Theune | there are some days where it feels like luck getting a kernel version that works straightforward "everywhere" ... | 10:08:17 |
| Christian Theune | then again, i'm happy to not be stuck on a distro kernel - this makes talking to upstream much more pleasant | 10:08:33 |
