Since 4.19.x is a longterm kernel, it is probaply a good idea to stabilize it soon. I know, you have a lot of tasks to do, so i understand, why this is not in progress alreasy. I'm using several 4.19 kernels for nearly 3 Month without any problems. Since the release of 4.19.14 I did not change anymore, to watch for problems at this specific Kernel. But tere werent any. I'm using Kernel 4.19.14: 4 x 64bit servers on my ESXI 5.5 width several jobs. amavis, fetchmail, apache, mysql, firebirdsql, postfix, imapd... 1 x 64bit on Intel i7-4770 with several jobs including Plasma-Desktop nvidia-drivers-340.107 with NVS450 1 x 64bit server at Celeron J1900 MichaelM
I am being using 4.19 since November in a AMD Ryzen desktop partially output of last: reboot system boot 4.19.3-gentoo Wed Nov 21 20:01 - 02:14 (06:13) reboot system boot 4.9.135-gentoo Wed Nov 21 19:48 - 20:01 (00:13) ---- uname -a Linux desktop 4.19.18-gentoo #1 SMP Sun Jan 27 12:51:22 CET 2019 x86_64 AMD Ryzen 7 2700X Eight-Core Processor AuthenticAMD GNU/Linux ---- From my point of view is very stable, no hangs so far. Thanks you for keeping this distro so good. :)
+1. Have been a user of 4.19.4 on a desktop workstation since it came out, no problems so far. For certain CPU+GPU related reasons I do not want to go back to a pre-4.15 kernel. Have been using several versions of nvidia-drivers with that (1080Ti), currently 415.27; everything works perfectly fine. uname -a Linux jan-threadripper 4.19.4-gentoo #1 SMP Tue Nov 27 00:19:11 CET 2018 x86_64 AMD Ryzen Threadripper 1950X 16-Core Processor AuthenticAMD GNU/Linux Profile: default/linux/amd64/17.0/desktop/gnome/systemd (stable) And I will join in the thanks for giving us such a great distro.
Thanks everyone for your interest in stabilizing 4.19. Soon, we'll be doing another round of stabilization requests and that will be tracked on bug #678094. We were trying to wait on a bluetooth CVE patch, but that discussion around the solution seems to be continuing longer than we expected. Thank-you for your patience and understanding. *** This bug has been marked as a duplicate of bug 678094 ***