01:56 <steev> nice

01:57 <steev> JensGlathe[m]: craftyguy: jhovold: fwiw, i reverted it here, and while at home i hadnt seen it, i slept the machine at home, and woke it up over at my sisters place and when i tried to connect to their wifi network, got the corruption

04:58 <craftyguy> I built the kernel with it reverted but will have to test tomorrow/later

06:27 <JensGlathe[m]> <bumble[m]> "want to share, have not encounte..." <- Sound?

07:49 <jhovold> steev: thanks for testing, it would still be possible to hit the corruption even if that change may possibly explain why some people hit it much more often since 6.9

07:50 <jhovold> I think you were one of the people who reported it really early on, long before that commit was merged

07:50 <jhovold> just curious if it makes a significant impact in setups were this triggers very often (like craftguy's)

07:53 <jhovold> bumble[m]: support for the x13s is in a pretty good state, even if there are still some known issues (most of those affecting all qualcomm machines):

07:53 <jhovold> https://github.com/jhovold/linux/wiki/X13s#known-issues

08:02 <steev> jhovold: for some reason at my sister's it was *really* bad - maybe it's a 5GHz vs 2.4GHz or something

08:02 <steev> or maybe even 6?

08:04 <jhovold> how often do you hit it there (without any attempt to mitigate it like disabling its)?

08:05 <steev> this was the first time there, but they recently switched to at&t as well

08:05 <steev> so they now have the same router as i do

08:06 <jhovold> ah, ok

08:06 <steev> i also hit this, after getting the corruption when coming out of suspend, when i tried to modprobe -r; modprobe - https://paste.debian.net/hidden/0e1338c6/

08:09 <steev> also looks like maybe it prevented it from sleeping again

08:09 <steev> https://paste.debian.net/hidden/ca37aed6/ (i'm going over the dmesg output as i haven't bothered to reboot it)

08:14 <steev> https://dpaste.com/HUJ4KTDX2 (debian's paste is yelling at me to stop spamming when i try to paste this one for some reason)

08:15 <steev> but once i got home, it woke up and connected to my wifi with no issue so *shrug*

08:22 <jhovold> thanks, i'll look at the allocation failure later, but i wouldn't necessarily trust reloading the driver to work after hitting something like this

08:55 <bumble[m]> <JensGlathe[m]> "Sound?" <- well... sound _sometimes_ becomes garbled when watching a youtube video. If the video is paused ~30 seconds or so the sound is normal again at playback. 'other than that, everything seems perfect

08:56 <JensGlathe[m]> okay I have a similar issue. But only with internal speakers.

09:02 <jhovold> and presumably only with pipewire (which is known not to work)?

09:03 <JensGlathe[m]> yep. Ubuntu is using it though

09:03 <jhovold> yeah, it's still a bug that needs to fixed for sure

09:06 <ungeskriptet_> dianders: You have a programming manual for the Goodix GT7375P IC, right? Does it explain what the I2C_SET_OPT pin does?

09:54 <hugt1> Hi all, I've recently received a ThinkPad X13s. Currently, I've got Debian — Gnome installed. One last key feature that will make this device my main laptop is a working integrated microphone. On the Debian install page, it says that I need to switch from PipeWire to PulseAudio. Is this still necessary? Has anyone been able to make it work well enough to have calls with it?

10:06 <albsen[m]> hugt1: I've been using bluetooth, the internal mic wasn't properly working last time I tried

10:25 <jhovold> hugt1: audio, including the internal mic, works fine as long as you use pulseaudio

10:25 <jhovold> pipewire is unfortuantely still broken, but it's beeing looked at now

11:36 <hugt1> jhovold: ok, I'm going to switch to pulseaudio for the moment then. Thanks!

16:18 <dianders> ungeskriptet_: Looks like it controls the state of pull-up resistors on the i2c lines.

16:45 <dgilmore> I should try the microphone on the x13s on Fedora, it defaults to pipewire also

17:15 <craftyguy> jhovold: ok running your 6.14-rc3 + reverting dbd73acb22d8, dmesg is filling up rapidly with these messages: https://bpa.st/6DRQ

17:16 <craftyguy> (oh and I also removed the msi-map disable thing I had to work around this, as you requested)

17:17 <craftyguy> currently connected to 5GHz. wifi is still usable, else I wouldn't be able to communicate here now, but the flood of those errors/msgs in dmesg doesn't give me great hope that it'll stay that way for long heh

17:24 <jhovold> craftyguy: thanks a lot testing, then it seems it's just down to the increased parallelism when using the gic its that made it easier to hit this

17:25 <jhovold> and something with your setup, possibly causing more roaming

17:28 <jhovold> I'll try to find a way to escalate this with qcom

17:52 <craftyguy> no problem, happy to test stuff :)