Hello everyone, I think I found it. I used irqpoll and I didn't experience any hiccups with my mouse performance. But the Wi-Fi was still malfunctioning. To linux-pci and linux-acpi: It's an ath10k problem, sure, but there's something definitely problematic happening if, in the normal state, these Wi-Fi bugs hamper the touchpad movement. To ath10k and linux-wireless: I tried out "options ath10k_core rawmode = 0" along with "skip_otp=y' and the Wi-Fi seems to work perfectly as of now. It might be the fix, it might not be either. But I think there's something more important to ask: Are there any good resources/documentation on referring to what the different key-value pairs mean? Like, what's the exact documentation through which people arrive at "rawmode=0" or "skip_otp=y"? Bandhan On 26 June 2025 4:20:13 am IST, Bandhan Pramanik <bandhanpramanik06.foss@xxxxxxxxx> wrote: > Please ignore the last email (I haven't replied to everyone). Also, > here's the actual updated dmesg (the previous one was the old one): > https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180/raw/78460e6931a055b6776afe756a95d467913d5ebd/updated-dmesg > > On Thu, Jun 26, 2025 at 4:16 AM Bandhan Pramanik > <bandhanpramanik06.foss@xxxxxxxxx> wrote: > > > > Hello Bjorn, > > > > First of all, thanks a LOT for replying. > > > > I have included the files in my previous GitHub Gist. Sharing the raw > > files for easier analysis. > > > > lspci -vv: https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180/raw/78460e6931a055b6776afe756a95d467913d5ebd/detailed-lspci.txt > > dmesg: https://gist.github.com/BandhanPramanik/ddb0cb23eca03ca2ea43a1d832a16180/raw/78460e6931a055b6776afe756a95d467913d5ebd/dmesg.log > > > > On a different note, I had to use pci=noaer, so that the ring buffer > > wouldn't get cleared that fast. > > > > Regarding the ath10k thing, none of the fixes worked this time. Only > > irqpoll worked. I don't know if it's because of a disparity b/w GNOME > > and KDE (because my daily driver is Fedora 42), but I'm 300% sure that > > it's not just the Wi-Fi that's the issue here. It's most probably a > > lot of issues here, and the harder issues to fix are usually the ones > > closer to the hardware. > > > > Anyway, if you get something, please let me know. > > > > Bandhan > >
