OK mga9-64; HW: Intel i7-870, P55 chipset GPU: GTX750Ti -driver: nvidia-current 535.146.02-1 (from testing) Some more from testing: sddm-0.20.0-5, kernel-firmware-20231111-1 and some *-firmware-20231111-1 $ uname -a Linux svarten.tribun 6.5.13-1.mga9 #1 SMP PREEMPT_DYNAMIC Thu Dec 14 11:42:31 UTC 2023 x86_64 GNU/Linux $ dkms status | grep "6.5.13-1" virtualbox, 7.0.12-2.mga9, 6.5.13-1.mga9, x86_64: installed nvidia-current, 535.146.02-1.mga9.nonfree, 6.5.13-1.mga9, x86_64: installed § Plasma, X11 § All normal desktop apps OK - have been using for a couple days. § VirtualBox 7.0.12: MSW7 guest with guest additions 7.0.13 OK: internet videos, windows update, dynamic guest window resizing, USB2 flashstick, host folder sharing, bidirectional clipboard, and drag file from Dolphin to Explorer. § freeze on VT switching with nvidia is fixed (like it is with desktop 6.5.13) § suspend-resume OK (as opposed to 6.5.13 and earlier desktop kernel) with mentioned Nvidia drivers, Bug 32541.
CC maintainer for advisory proposal and packet list.
CC: (none) => kernel
Blocks: (none) => 31994
My systems also use LVM partitions on a LUKS partition, separate boot. I see i have forgotten to say so in kernel tests last half year or so.
kernel-linus-6.5.13-2.mga9 in the build with the nvida VT fix.
CC: (none) => ghibomgx
(In reply to Giuseppe Ghibò from comment #3) > kernel-linus-6.5.13-2.mga9 in the build with the nvida VT fix. Hm. I had no problem Vt switching with kernel-linus-6.5.13-1 on *my* setup.
Summary: Update request: kernel-linus-6.5.13-1.mga9 => Update request: kernel-linus-6.5.13-2.mga9
(In reply to Morgan Leijström from comment #4) > (In reply to Giuseppe Ghibò from comment #3) > > kernel-linus-6.5.13-2.mga9 in the build with the nvida VT fix. > > Hm. I had no problem Vt switching with kernel-linus-6.5.13-1 on *my* setup. Oh, then I misread I thought 6.5.13-1 was freezing too...
For completeness i will retest using 6.5.13-2... ...or is there yet another iteration in the pipe with the fixes for bluetooth like in desktop 6.5.13-3?
(In reply to Morgan Leijström from comment #6) > For completeness i will retest using 6.5.13-2... > ...or is there yet another iteration in the pipe with the fixes for > bluetooth like in desktop 6.5.13-3? No, apart the VT. Furthermore kernel linus hasn't any extra 8812au module at all.
Version suitability details when testing? When there are several kernels installed, it is normal to have highest version of cpupower, kernel-userspace-headers, lib64bpf1 etc installed. But when *testing* new kernels, it that OK then too? Or should we make sure to have corresponding version of all related packages? i.e downgrade cpupower when going from testing desktop 6.5.13-3, to test linus 6.5.13-2.
(In reply to Giuseppe Ghibò from comment #3) > kernel-linus-6.5.13-2.mga9 in the build with the nvida VT fix. Included packages, according to https://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20231216105706.ghibo.duvel.4163097/kernel-linus-6.5.13-2.mga10/packages.i586.0.20231216105807.log and https://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20231216105706.ghibo.duvel.4163097/kernel-linus-6.5.13-2.mga10/packages.x86_64.0.20231216105804.log i586: kernel-linus-devel-6.5.13-2.mga10.i586.rpm kernel-linus-devel-latest-6.5.13-2.mga10.i586.rpm kernel-linus-6.5.13-2.mga10.i586.rpm kernel-linus-latest-6.5.13-2.mga10.i586.rpm kernel-linus-doc-6.5.13-2.mga10.noarch.rpm kernel-linus-source-6.5.13-2.mga10.noarch.rpm x86_64: kernel-linus-latest-6.5.13-2.mga10.x86_64.rpm kernel-linus-6.5.13-2.mga10.x86_64.rpm kernel-linus-devel-6.5.13-2.mga10.x86_64.rpm kernel-linus-devel-latest-6.5.13-2.mga10.x86_64.rpm kernel-linus-doc-6.5.13-2.mga10.noarch.rpm kernel-linus-source-6.5.13-2.mga10.noarch.rpm
CC: (none) => marja11
References: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.12 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.13 In the second link, I read: .... This fixes CVE-2023-28464 Searching our bugzilla for "CVE-2023-28464" and grepping all advisories for that CVE, returns nothing. That CVE doesn't seem to make sense, though, only kernels <= 6.2.9 were affected according to https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28464 So, is this only a bugfix release?
The following advisory has been added to SVN, please say so when it needs to be changed and, if so, do also remove the "advisory" keyword. type: bugfix subject: Updated kernel-linus packages fix bugs src: 9: core: - kernel-linus-6.5.13-2.mga9 description: | Upstream version 6.5.13 with many bug fixes references: - https://bugs.mageia.org/show_bug.cgi?id=32628 - https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.12 - https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.13
Keywords: (none) => advisory
(In reply to Marja Van Waes from comment #10) > https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.13 > > In the second link, I read: > > .... > This fixes CVE-2023-28464 > > Searching our bugzilla for "CVE-2023-28464" and grepping all advisories for > that CVE, returns nothing. > > That CVE doesn't seem to make sense, though, only kernels <= 6.2.9 were > affected according to > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28464 > Or I misunderstand the word "through"... does it mean "since" here? Or does "6.2.9" not refer to a kernel version, but to something else?
(In reply to Marja Van Waes from comment #12) > (In reply to Marja Van Waes from comment #10) > > > https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.13 > > > > In the second link, I read: > > > > .... > > This fixes CVE-2023-28464 > > > > Searching our bugzilla for "CVE-2023-28464" and grepping all advisories for > > that CVE, returns nothing. > > > > That CVE doesn't seem to make sense, though, only kernels <= 6.2.9 were > > affected according to > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28464 > > > > Or I misunderstand the word "through"... does it mean "since" here? Or does > "6.2.9" not refer to a kernel version, but to something else? The usage of the word "through" is not completely clear there. According to: https://www.merriam-webster.com/dictionary/through I would interpret as boundary for 6.2.9 (so "up to 6.2.9"), however the patch is included in 6.5.13, so probably required. On the other hand the same patch is included in any supported upstream kernel from 4.19, 5.10, 5.15, 6.1, etc.
(In reply to Giuseppe Ghibò from comment #13) > > I would interpret as boundary for 6.2.9 (so "up to 6.2.9"), however the > patch is included in 6.5.13, so probably required. On the other hand the > same patch is included in any supported upstream kernel from 4.19, 5.10, > 5.15, 6.1, etc. Thnnks for the explanation :-)
(In reply to Marja Van Waes from comment #14) > (In reply to Giuseppe Ghibò from comment #13) > > > > > I would interpret as boundary for 6.2.9 (so "up to 6.2.9"), however the > > patch is included in 6.5.13, so probably required. On the other hand the > > same patch is included in any supported upstream kernel from 4.19, 5.10, > > 5.15, 6.1, etc. > > Thnnks for the explanation :-) At least I think so. Maybe native speakers can have a better explaination.
Test in comment 0 repeated with kernel-linus-6.5.13-2, works the same :)
Packager: Is -2 the final iteration for this bug?
Assuming this update applies to Mageia9 changed mga10 to mga9 and updated without problems from my usual mirror.
CC: (none) => tarazed25
Mageia9, x86_64 Mini-pc Intel model: NUC12WSBi7 12-core Intel Core i7-1260P Intel Alder Lake-P Integrated Graphics driver: i915 Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 Mate desktop working. Virtualbox launches client. Bluetooth reconnects to audio device immediately. Falkon, Thunderbird and Firefox OK. Mesa graphics work. USB CUPS printing OK. LibreOffice Writer OK. Letting it run for a while.
Kernel: 6.5.13-2.mga9 arch: x86_64 10-core Intel Core i9-7900X NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nouveau Intel Ethernet I219-V driver: e1000e Boots without trouble. Home network visible. NFS shares mounted. Youtube videos in Firefox with bluetooth sound. glmark2 using mesa graphics. Desktop running as before.
System: Kernel: 6.5.13-2.mga9 arch: i686 bits: 32 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 The wifi not works, I must to reboot in other kernel to see if was the chair or the kernel rfkill ID TYPE DEVICE SOFT HARD 0 wlan hp-wifi desbloqueado bloqueado 1 wlan phy0 desbloqueado bloqueado
(In reply to katnatek from comment #21) > System: > Kernel: 6.5.13-2.mga9 arch: i686 bits: 32 Desktop: LXQt > v: 1.4.0 Distro: Mageia 9 > The wifi not works, I must to reboot in other kernel to see if was the chair > or the kernel > > rfkill > ID TYPE DEVICE SOFT HARD > 0 wlan hp-wifi desbloqueado bloqueado > 1 wlan phy0 desbloqueado bloqueado I have to downgrade the firmwares to recover my wifi all works well in this kernel
Whiteboard: (none) => MGA9-64-OK MGA9-32-OK
In reference to Bug 32623 - Update request: kernel-6.5.13-6.mga9 validating this corresponding linus version too.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0154.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED