site  contact  subhomenews

Kernel 6.10.11 compiled

September 24, 2024 — BarryK

I announced on the forum, intend to return to QV development:

https://forum.puppylinux.com/viewtopic.php?p=131592#p131592

In anticipation, have compiled the 6.10.11 kernel, with the fixes for bluetooth v5 as reported recently:

There is a lot to do. EasyOS is built with woofQ:

https://github.com/bkauler/woofq

Whereas QV is built with woof-quantum-vis:

https://github.com/bkauler/woof-quantum-vis

The work improving Scarthgap, including fixes, has gone into woofQ, but woof-quantum-vis is a separate project. Many woofQ fixes can be applied to woof-quantum-vis, and I will have to do it the hard way, given that they are radically different; will have to look at each woofQ commit and see if it can be applied to quantum-vis.

EDIT:
This kernel is a disaster! I started a filesystem check on a 4TB USB3 SSD, and CPU activity went through the roof. So much on the desktop became unresponsive. Some tray applets still worked, networkmanager applet was unresponsive, window close buttons unresponsive. My evaluation of this is superficial, just observed this weirdness, didn't try any in-depth analysis.

Hit CTRL-C to stop the filesystem check, then ran "sync", but the USB drive was still very busy, even though sync had returned. I tried to shutdown, but it hung, with a message something to do with unable to flush to the drive.

I'm running EasyOS 6.3.1, on which I had compiled the 6.10.11 kernel. Went back to the 6.6.47 kernel, and all is good. In fact, right now doing a filesystem check on another 4TB USB drive, running 6.6.47, and this time cpu activity stays sane, and everything continues to work. The filesystem check is happening right now. It takes awhile with such a big drive.

I had previously used the 6.8.1 kernel with QV and no problem. One thing I notice, an alarming increase in vmlinuz size:

6.6.47:  6809K
6.8.1:   7489K
6.10.11: 8785K

These kernels have essentially the same configuration file, except as expected more hardware support with the later kernels; but mostly I would expect more modules, not the kernel to grow by such a huge amount.

Anyway, what is wrong with the 6.10.x kernel? Some fundamental change in process management? Staying with the 6.6.x kernel for QV.    

Tags: easy