03:01 <steev> bamse: 21 hours of uptime, but wifi has died; i got "chan info: invalid frequency 0 (idx 41 out of bounds)" - no idea what it means yet, but attempting to modprobe -r ath10k_snoc; modprobe ath10k_snoc; i end up with error -ENXIO: IRQ index 0 not found

03:04 <steev> irq: type mismatch, failed to map hwirq-446 for interrupt-controller@17a00000!

03:09 <bamse> i do get the "invalid frequency" from time to time, but it has kept pinging

03:09 <bamse> i thought this was in line with the slightly unstable wifi on c630 as well, where wpa_supplicant reconnects from time to time

03:37 <steev> c630 has been rock solid for me for a very long time

05:29 <steev> i don't wanna reboot to get wifi back, but i guess i will have to, it's nice that it lasted so long though!

05:29 <steev> 1 day 5 minutes without a reboot, so yay to that :D

14:04 <bamse> steev: for me it recovers automagically from this state...but you're saying it's dead after that message?

14:37 <gwolf> steev: wow... I often get multi week uptime. What I lost on my C630 but haven't been able to get working again is... Audio :-(

15:00 <steev> gwolf: unless there has been an update to the ucm configs, it should be working

15:01 <steev> gwolf: we're talking about the Flex 5G here though, the C630 works great in my case. audio "pops" here, but it works, srinik was looking into it but dunno what the status is lately

15:44 <steev> bamse: indeed it is dead, and doesn't come back

15:44 <steev> not every time there is an invalid frequency

15:45 <steev> that was just the last message in dmesg regarding wifi

16:07 <gwolf> ok -- I thought you wer talking about the C630, and it sounded strange (-:

16:07 <gwolf> about audio -- no idea why, but some kernels ago it stopped working. I almost don't use sound, so I mostly don't care

16:08 <gwolf> But I _am_ grabbing from the DTBs, and have the whats-its-name package from collabora...

16:08 <gwolf> ...still, pavucontrol only shows "dummy device" :-(

16:43 <bamse> steev: do you know if there's any way to find which window relates to which alacritty process?

16:44 <bamse> steev: just killed one using 900MB to make my flex happier again and have another one at 740MB...

16:45 <steev> i don't, but i asked in the alacritty irc channel, i know 2 of the devs hang out there

16:46 <bamse> ohh btm supports grouping the processes based on name

16:46 <bamse> so i have 3.3GB ram consumed by alacritty instances

16:46 <bamse> that's not awesome when you only have 7.3 or whatever it is to start with

16:52 <bamse> steev: swaymsg "[pid=272179] focus"

16:52 <bamse> that was easy

16:55 <steev> wow

16:55 <steev> that's quite a bit of usage, wtf are you running in them!?

16:56 <steev> fwiw

16:56 <steev> 11:45:26 <•kchibisov> echo $ALACRITTY_LOG should have pid as suffix.

16:56 <steev> 11:45:45 <•kchibisov> Or if you have socket, it's a part of default socket creating scheme.

16:56 <steev> 11:45:50 <•kchibisov> echo $ALACRITTY_SOCKET.

17:03 <bamse> that is 37 days of kernel hacking

17:06 <bamse> but issuing a "reset" to clear the scrollback didn't reduce the memory use...so i suspect that there's a leak somewhere

18:45 <bamse> steev: turns out that i was running an ancient version of alacritty, with some patches (that you pointed me to?) to make it play nice with freedreno...

18:45 <bamse> steev: thought i had switched out all my machines to the one from arch...which works...perhaps that will solve my issue

18:45 <bamse> we'll see in another 35 days

18:48 <steev> oh, yeah, kchibisov did a lot of work on alacritty, these days it handles gles2 and so forth gracefully