r/kernel

Installed 6.12.85+deb13-amd64 yesterday on my Lenovo a14 Thinkpad with AMD Ryzen 5 7430U.

Now I get frequent stutters and dmesg shows "AMD-Vi: Completion-Wait loop timed out"

Due to recent security fixes I don't want to roll back kernel but what can I do?

OrangePi 5 Plus (16GB v2.1) – Vulkan + OC + Mesa 26.2 results (glmark2 / vkmark)

Hey everyone,

Lately I’ve been tinkering a bit more with the OrangePi 5 Plus and managed to get some pretty interesting results, so I figured I’d share my setup and numbers – might be useful to someone.

Hardware:

• OrangePi 5 Plus 16GB (v2.1)
• Mali-G610 MC4 GPU

Software / stack:

• EDK2 UEFI
• Ubuntu 26.04 ARM, Fedora 45 ARM
• Kernel 7.0
• Mesa 26.2 (Panfrost + Zink)
• Vulkan enabled

Settings:

• GPU overclock: 1200 MHz (actual ~1188 MHz) @ 1.2V
• CPU & GPU: performance mode (no throttling during tests)

Results:

• glmark2-es2: ~3500
• glmark2-es2-wayland: ~3500
• glmark2: ~3000
• glmark2-wayland: ~3500
• vkmark: ~4300

Honestly, the Vulkan + Zink combo on this chip provides a pretty nice boost compared to older Mesa versions. Stability is fine so far with this OC profile, but I’m still testing longer sessions.

I also have screenshots with clearly visible:

• test dates
• versions (kernel, Mesa, etc.)
• actual results

If needed, I can share a more detailed setup (kernel config, boot parameters, Mesa build options, etc.).

If anyone else has been tweaking the G610 on this board, I’d be interested to hear your experiences—especially regarding HW Aceleration for Chromium.

Cheers 🍻

https://preview.redd.it/g4mcc6ibhiwg1.jpg?width=2559&format=pjpg&auto=webp&s=511cbd8aa35668eda84a03a0a9744e238a8d754c

Hello folks!

We open-sourced RMR+BRMR, a new block-level active-active replication solution we've been building.

RMR (Reliable Multicast over RTRS) and BRMR (Block device over RMR) together form a new block-level active-active replication solution, enabling single-hop active-active replication and direct node-to-node synchronization during degraded states.

We'd love for the community to take a look, try it out, and share feedback. The project is still in development.

Contributions are very welcome — whether it's code, documentation, testing, or just opening issues with questions and ideas.

Code: https://github.com/ionos-cloud/RMR

Documentation: https://ionos-cloud.github.io/rmr.io/

I just made my first kernel contribution to the linux kernel, specifically in staging driver rtl8724bs. I chose to fix code styling issues by running checkpatch.pl, got to fix some bounding bugs along the way too, but that’s it. I can’t exactly describe my feeling when I got the LGTM, both excited and annoyed, but that’s a story for another day.

However, my question is, when did these drivers come into “staging” first having all these somewhat obvious bugs and clear styling issues that dont match the kernel’s preferences? Like isn’t there a first step for drivers to be submitted and accepted? Having simple styling/standards at least? And where do these drivers get accepted to be at staging/ start at? Do maintainers just fork another peoples work after confirming together?

Sorry if I sound dumb, I’m just curious on how things get accepted at staging with having minimum standards for the kernel’s preferences. Thanks.

Hey! I have a Xiaomi Redmi 15 5G (codename: spring) with OrangeFox, KSU Next + SUSFS already set up. Xiaomi officially released the kernel source (branch: spring-v-oss). I don't have a PC to compile it myself, so I'm looking for a developer willing to compile a NetHunter kernel for this device. I'm fully available for testing and providing logs. Any help is greatly appreciated! 🙏

Hi,

After upgrading to Fedora 44 kernel 6.19.14-300.fc44.x86_64, my laptop becomes extremely slow shortly after boot.

When checking processes, I see many kernel worker threads stuck in D state, especially with names/wchan like:

kworker/*+kec_query

The kernel log also shows several ACPI/WMI-related errors, including:

ACPI Error: AE_NOT_FOUND

ACPI BIOS Error: Attempt to CreateField of length zero

ACPI Error: Aborting method \_SB.WMID.* due to previous error

hp_wmi: query 0x4c returned error 0x6

hp_bioscfg: Returned error 0x3004, "Generic/Other error"

There are also repeated USB messages:

usb usb2-port4: Cannot enable. Maybe the USB cable is bad?

I do have USB devices connected, but this exact setup worked fine before this kernel update, so I suspect this may be a regression in

6.19.14-300.fc44 related to ACPI/EC or HP WMI.

For now, I set the previous Fedora 44 kernel as the default boot option:

6.19.13-300.fc44.x86_64

Has anyone else seen this issue on HP laptops or with kworker processes stuck in kec_query after this kernel update?

Información Técnica

OS: Fedora Linux 44 Workstation x86_64

Kernel affected: 6.19.14-300.fc44.x86_64

Previous kernel available/workaround: 6.19.13-300.fc44.x86_64

Desktop: GNOME 50.1 on Wayland

Hardware: HP Pavilion x360 Convertible 14-dy0xxx

Firmware: HP F.29

CPU: Intel Core i7-1165G7, 4 cores / 8 threads

GPU: Intel Iris Xe Graphics

RAM: 15 GiB

Swap: 28 GiB, unused

Root filesystem: btrfs on NVMe

External storage: USB drive mounted, but this setup worked fine before

Looking at the source code of atkbd driver (linux-6.6.74/drivers/input/keyboard/atkbd.c), I have harder time figuring out why is it missing/can't find it.

I found in (/sys/bus/serio/drivers/atkbd/serio0) all atkbd attributes, except function_row_physmap.

I tried devadm info -a /dev/input/by-path/platform-i8042-serio-0-event-kbd, and again, I can see all attributes except function_row_physmap.

Just trying to understand why is it missing, as if I understood correctly, any attribute should be present in sys fs. I am curios to know why, as I am researching Linux drivers and kernel at the moment.

Any help is much appreciated :)

My machine: HP Eliteboot 830 g8

OS: Arch Linux

Kernel: 6.18.22-1-lts

Hi Am Avishkar patil am from Maharashtra,Am here for asking for help for getting guidance of Kernel engineering I want to learn about kernel I am Interested in Computer science I have fundamentals cleared am currently learning about kernel engineering since 24 April 2026 i want to know were i can get Guidance for learning about this I also own MIT notes and syllabus and books can you suggest me books too?

I also have. Systems & Reverse Engineering

Windows Internals, 7th Edition (Parts 1 & 2)

Windows Kernel Programming, 2nd Edition

Practical Reverse Engineering

Computer Architecture: A Quantitative Approach

Software Development

C# 12 in a Nutshell

C# 12 and .NET 8 – Modern Cross-Platform Development Fundamentals

Linux kernel devlopement

And computer science book

Hey guys I have been thinking of making the switch to Linux recently, but the only thing stopping me is that some multiplayer games have Anti-cheat that do not support linux. I dont really underatand the whole kernel being open source but I understand the companies reasoning is that the Kernel is open source, even though that is not a “real“ reason.

My question is that if the kernel is open source, wouldn’t you be able to edit the kernel to “act” like Windows to bypass the anti-cheat? Maybe an explanation of the kernel could also answer my question

Hello everyone.

I've been studying Low Level Programming for two years, focusing on C and Assembly. I've also been building my own boot loader via BIOS (MBR). Lately, I've started studying FreeBSD and reading its documentation, as I'd like to pursue a career in Kernel Engineering.

However, in my country there's no market for this type of work, and all the job postings I see require prior professional experience in the field.

Could anyone offer some guidance on how to get into this field?

Hi all,

I’m running syzkaller for kernel fuzzing on a very constrained VM (1 GB RAM) and hitting a recurring issue after some iterations:

- Syzkaller starts fine

- My script automatically starts the next iteration after one finishes

- After running for a while, I start getting:

- “fork not possible”

- “cannot allocate memory”

- Eventually fuzzing stalls

Current setup:

- procs=1

- low-memory VM (1GB)

- repeated automated iterations

- considering target_reboot and swap, not fully tuned yet

My suspicion is one of:

1. syz-executor processes accumulating
2. kernel slab/kmalloc growth from fuzzing
3. fork failing due to Linux overcommit / no swap
4. my iteration loop not cleaning up enough between runs

Questions:

- Has anyone run syzkaller reliably on very low memory?

- What tuning helped most? (swap, drop_caches, target_reboot, overcommit settings, smaller corpus, disabling coverage, etc.)

- Is periodic reboot normal for long-running syzkaller on small VMs?

- Any way to detect whether this is executor leakage vs kernel memory pressure?

I’ve seen fork failures can happen under memory pressure on Linux :contentReference[oaicite:1]{index=1}, but wondering what syzkaller-specific fixes people use.

Would appreciate configs, scripts, or debugging ideas.

[ Removed by Reddit on account of violating the content policy. ]