Giuseppe told 6.6.14 will be in mga9 updates testing probably this weekend.

CC: (none) => fri
Assignee: bugsquad => kernel

6.6.14 is now in updates testing.
Giuseppe, ready for QA?

I am running kernel-linus-6.6.14-1.mga9.x86_64 quick test OK on my "svarten", using LUKS, LVM, nvidia-newfeature, Virtualbox, Plasma X11

both standard an -linus in updates_testing. There is not yet kmod.virtualbox for 6.6.14 and kmod-xtables-addons. For kmod-vvirtualbox better waiting to push virtualbox 7.0.14 before for current 6.5.13 kernel, then later for 6.6.14 to avoid the past problems. Still needed a newer kernel-firmware* set but that can be done later.

CC: (none) => ghibomgx

I take that like we can go ahead testing the kernels.

- Remembering to have dkms-virtualbox and dkms-nvidia-* installed if we use them, and kernel-devel of course.

- And retest with newer newer kernel-firmware* later, and prebuilt virtualbox kmod.

Assignee: kernel => qa-bugs

When googling for:

  CVE site:https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6

4 CVEs are mentioned in the changelogs, 3 of them weren't mentioned in a Mageia kernel update before:

6.6   : CVE-2020-26555 (patch was already added in kernel-6.5.11-5.mga9)
6.6.3 : CVE 2023-28464
6.6.13: CVE 2023-6610
6.6.14: CVE 2023-46838

So I assume this update counts as a security update, right?

QA Contact: (none) => security
Component: RPM Packages => Security

MGA9-64 Plasma, i5-7500, Quadro K620 graphics(nvidia-current), wired Internet.

Updated all three kernels in one operation, using the list from comment 6 in qarepo, and running drakrpm-update from the command line so I could watch the process in the terminal. 

No issues on any of the updates. Nvidia-current was built and installed three times, once for each kernel. Afterward I booted into each kernel in turn, and di a bit of brief testing - played a video in Firefox, ran a couple of apps, ran Firefox. (I do not as yet have VirtualBox installed on this system)

No issues to report.

Everything installed from the full list with qarepo but at the MageiaUpdate stage there was a conflict which threatened to brick my system.
The following packages have to be removed for others to be upgraded:
mate-applets-1.26.1-1.mga9.x86_64
 (due to missing libcpupower.so.0()(64bit))
task-mate-1.26.0-2.mga9.noarch
 (due to missing mate-applets)

No idea what is going on:
$ locate cpupower
 /usr/lib64/libcpupower.so.0

The cpupower service is inactive.  Tried restarting it but that made no difference; the MageiaUpdate still complains.
cpupower-devel seems to be missing from my system and if I try to install it the problem is the same.  At what point cpupower-devel disappeared I have no clue.

I may have to move to another system but shall try to wrangle this in Plasma first.

CC: (none) => tarazed25

(In reply to Len Lawrence from comment #9)
> Everything installed from the full list with qarepo but at the MageiaUpdate
> stage there was a conflict which threatened to brick my system.
> The following packages have to be removed for others to be upgraded:
> mate-applets-1.26.1-1.mga9.x86_64
>  (due to missing libcpupower.so.0()(64bit))
> task-mate-1.26.0-2.mga9.noarch
>  (due to missing mate-applets)
> 
> No idea what is going on:
> $ locate cpupower
>  /usr/lib64/libcpupower.so.0
> 
> The cpupower service is inactive.  Tried restarting it but that made no
> difference; the MageiaUpdate still complains.
> cpupower-devel seems to be missing from my system and if I try to install it
> the problem is the same.  At what point cpupower-devel disappeared I have no
> clue.
> 
> I may have to move to another system but shall try to wrangle this in Plasma
> first.

Or you miss cpupower in the testing list or mate-applets need to be rebuilt

No, I had not left anything out but had to install the current cpupower-devel myself.  Did not help.
Got nowhere in Plasma so moved to a different system on the same machine, one which had not been touched for quite some time so there was a big update to do.  Then tried the new kernel list and hit exactly the same problem.  

Next I moved to another machine and found the same behaviour.  Note that I have been installing kernel after kernel on both these machines and three others and never hit such a problem before.  If mate-applets needs to be rebuilt against the new kernel then I am in a very sticky situation.

Created attachment 14313 [details]
output of inxi -F in my x86_64 system

More bad news, I can't start graphic session in any of the kernels in my x86_64 system.

I even run dracut --regenerate-all -f from the working 6.5.13-desktop-6.mga9 kernel and test again

(In reply to Len Lawrence from comment #11)
> No, I had not left anything out but had to install the current
> cpupower-devel myself.  Did not help.
> Got nowhere in Plasma so moved to a different system on the same machine,
> one which had not been touched for quite some time so there was a big update
> to do.  Then tried the new kernel list and hit exactly the same problem.  
> 
> Next I moved to another machine and found the same behaviour.  Note that I
> have been installing kernel after kernel on both these machines and three
> others and never hit such a problem before.  If mate-applets needs to be
> rebuilt against the new kernel then I am in a very sticky situation.

I confirm that need rebuild 

LC_ALL=C urpmi --test mate-applets
The following package cannot be installed because it depends on packages
that are older than the installed ones:
mate-applets-1.26.1-1.mga9

Also gnome-applets
LC_ALL=C urpmi --test gnome-applets
The following package cannot be installed because it depends on packages
that are older than the installed ones:
gnome-applets-3.46.0-3.mga9

Thanks for the confirmation Katnatek.
I guess I sit on my hands until somebody takes care of that.

Better set the feedback marker.

Keywords: (none) => feedback

(In reply to Marja Van Waes from comment #5)
> When googling for:
> 
>   CVE site:https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6
> 
> 4 CVEs are mentioned in the changelogs, 3 of them weren't mentioned in a
> Mageia kernel update before:
> 
> 6.6   : CVE-2020-26555 (patch was already added in kernel-6.5.11-5.mga9)
> 6.6.3 : CVE 2023-28464 
> 6.6.13: CVE 2023-6610
> 6.6.14: CVE 2023-46838
> 


An out-of-bounds read vulnerability was found in smb2_dump_detail in fs/smb/client/smb2ops.c in the Linux Kernel. This issue could allow a local attacker to crash the system or leak internal kernel information. (CVE-2023-6610)

An unprivileged guest can cause Denial of Service (DoS) of the host by
sending network packets to the backend, causing the backend to crash.
Data corruption or privilege escalation have not been ruled out.
https://xenbits.xen.org/xsa/advisory-448.html (CVE-2023-46838)

CVE: (none) => CVE-2023-6610, CVE-2023-46838
URL: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.1 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.2 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.3 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.4 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.5 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.6 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.7 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.8 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.9 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.10 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.11 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.12 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.13 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.14 => https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.1 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.2 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.3 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.4 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.5 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.6 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.7 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.8 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.9 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.10 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.11 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.12 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.13 https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.14 https://xenbits.xen.org/xsa/advisory-448.html

(In reply to Len Lawrence from comment #11)
> No, I had not left anything out but had to install the current
> cpupower-devel

I never install cpupower-devel - unless like the doc etc to test it is installable, and my systems also never use bpftool, lib64bpf-devel, or perf.

Strange Plasma do not work for you.

Plasma works but trying to install the new kernel threatens to remove Mate and mate-applets.  Mate is essential to my workflow.

mga9-64 OK, three laptops:

All also using new X11 Bug 32747, and mesa Bug 32759


___Acer Aspire7 

OK: Plasma X11, Desktop apps, Firefox internet video, suspend-resume, hibernate-resume


___Dell precision M6300

OK: Plasma X11, Desktop apps, Firefox internet video, suspend-resume, hibernate-resume


___Lenovo Thinkpad T510

OK: Plasma X11, Desktop apps, Firefox internet video, suspend-resume

Fail: Hibernate takes long time, screen blackens, write to disk (?) power lamp glitcjes (dit it restart instead of power off?)  write to disk, more long time, then power lamp blinking quickly (usually indicates kernel panic)

Forgot to say kernel flavour on the laptops are all -desktop-, and on the Dell precision M6300, also linus was tested.

mga9-64 OK on my workstation svarten

Intel i7-870, Intel P55

nvidia GTX750 using nvidia newfeature.
Short tests also with nvidia470 and nvidia-current.

Also using new X11 Bug 32747, mesa Bug 32759, VirtualBox 7.0.14 Bug 32760 

Been using it some hours with Plasma X11, various desktop apps, Firefox internet video

VirtualBox, using locally dkms built kmod, running with MSW7 guest: The guest asked to update and install guest additions and that worked perfectly. USB2 flash stick and GALEP-5 EPROM programmer. Dynamic window resizing.  Bidirectional clipboard. Internet video in Firefox. Windows update. Drag files from Dolphin to Explorer. Windows update.  Host folder sharing: both write protected and not.

Suspend-resume: No regression nor better: As usual, after suspend the monitor need power cycle to show picture after resuming the system when using nvidia driver with desktop kernel.  With linus: no problems.

From Morgan and TJ's experience it looks like Plasma has less trouble with the new kernels.  Katnatek found that GNOME has potential problems, Mate is unusable, and LXQt does not function properly.

(In reply to katnatek from comment #12)
> More bad news, I can't start graphic session in any of the kernels in my
> x86_64 system.
> 
> I even run dracut --regenerate-all -f from the working 6.5.13-desktop-6.mga9
> kernel and test again

Anything interesting in the journal?

What Xorg ?  from updates_testing?
What if you downgrade it?  And maybe other recently updated things.

IIRC, xorg.conf can be deleted (better renamed) and it will be created new.
Try?

To experiment, most safe is to use a persistent Mageia Live.

(In reply to katnatek from comment #13)
> I confirm that need rebuild 
> 
> LC_ALL=C urpmi --test mate-applets
> The following package cannot be installed because it depends on packages
> that are older than the installed ones:
> mate-applets-1.26.1-1.mga9
> 
> Also gnome-applets
> LC_ALL=C urpmi --test gnome-applets
> The following package cannot be installed because it depends on packages
> that are older than the installed ones:
> gnome-applets-3.46.0-3.mga9

I guess there exist some smart way to hunt for more incompatible packages...

I think that for each a bug should be opened, set to registered packager or pkg-bugs, high priority, and this bug set to depend on them.

We use to have a separate bug for kernel linus.
Should we this time too?

I'd add also these:

SRPMS:
kmod-xtables-addons-3.24-53.mga9.src.rpm

x86_64:
xtables-addons-kernel-6.6.14-desktop-1.mga9-3.24-53.mga9.x86_64.rpm
xtables-addons-kernel-6.6.14-server-1.mga9-3.24-53.mga9.x86_64.rpm
xtables-addons-kernel-desktop-latest-3.24-53.mga9.x86_64.rpm
xtables-addons-kernel-server-latest-3.24-53.mga9.x86_64.rpm

i586:xtables-addons-kernel-6.6.14-desktop-1.mga9-3.24-53.mga9.i586.rpm
xtables-addons-kernel-6.6.14-desktop586-1.mga9-3.24-53.mga9.i586.rpm
xtables-addons-kernel-6.6.14-server-1.mga9-3.24-53.mga9.i586.rpm

xtables-addons-kernel-desktop-latest-3.24-53.mga9.i586.rpm
xtables-addons-kernel-desktop586-latest-3.24-53.mga9.i586.rpm
xtables-addons-kernel-server-latest-3.24-53.mga9.i586.rpm

[BTW, there should be something wrong in ML after the disk full problems, as latest notification I got were comment #6 and comment #20. All other in-between missed (and spam folder is empty). It seems also someone other experienced this problem. Maybe sympa needs just to be restarted?]

For kernel-linus, probably we should open a separate bug (so report can be different). For this round maybe we should economize bug numbers, and merge in this one (which apparently seems to go smootly).

For cpupower there is a bump of version from so.0 to .so.1, so probably those package depending on it needs to be rebuilt. Better to recheck the deps from libcpupower.so.0 so to rebuild those packages.

gnome-apples and mate-applets seems those two packages linked to libcpupower.so.0

s/gnome-apples/gnome-applets/

Installed and tested without issues.


Tested for half a day of server usage. No issues noticed. Will report back if issues are found.


$ uname -a
Linux marte 6.6.14-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Jan 27 01:13:53 UTC 2024 x86_64 GNU/Linux
$ rpm -qa | grep 6.6.14 | sort
cpupower-6.6.14-1.mga9
kernel-desktop-6.6.14-1.mga9
kernel-desktop-latest-6.6.14-1.mga9
kernel-userspace-headers-6.6.14-1.mga9
lib64bpf1-6.6.14-1.mga9
perf-6.6.14-1.mga9
$ lscpu | grep name
Model name:                         Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
$ lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Q87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)

Installed and tested without issues.


Tested for half a day of workstation usage, including containers and virtual machines.
No issues noticed. Will report back if issues are found.


System: Mageia 9, x86_64, Plasma DE, AMD Ryzen 5 5600G with Radeon Graphics using amdgpu driver.


$ uname -a
Linux jupiter 6.6.14-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Jan 27 01:13:53 UTC 2024 x86_64 GNU/Linux
$ rpm -qa | grep 6.6.14 | sort
cpupower-6.6.14-1.mga9
kernel-desktop-6.6.14-1.mga9
kernel-desktop-devel-6.6.14-1.mga9
kernel-desktop-devel-latest-6.6.14-1.mga9
kernel-desktop-latest-6.6.14-1.mga9
kernel-userspace-headers-6.6.14-1.mga9
lib64bpf1-6.6.14-1.mga9
perf-6.6.14-1.mga9
$ lscpu | grep name
Model name:                         AMD Ryzen 5 5600G with Radeon Graphics
$ lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c1)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
04:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller (rev 01)
04:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
04:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
05:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
05:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
05:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
05:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
05:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 26)
0b:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. Device 500f (rev 03)
0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev c9)
0c:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller
0c:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
0c:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1
0c:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)

Installed and tested without issues.


This is running on a QEMU/KVM VM with PCI pass through of a Radeon RX 6500 XT GPU card.
Tested for an hour of desktop usage, including steam, steam games, Vulkan and OpenGL games.
No issues noticed, in particular, LXQt DE is working without issues.
Will report back if issues are found.




Guest System: Mageia 9, x86_64, LXQt DE, AMD Ryzen 5 5600G, Radeon RX 6500 XT using amdgpu driver.



$ uname -a
Linux jupiter-vm-mageia-9-jogos 6.6.14-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Jan 27 01:13:53 UTC 2024 x86_64 GNU/Linux
$ rpm -qa | grep 6.6.14
cpupower-6.6.14-1.mga9
kernel-desktop-6.6.14-1.mga9
kernel-desktop-latest-6.6.14-1.mga9
lib64bpf1-6.6.14-1.mga9
kernel-userspace-headers-6.6.14-1.mga9
$ lspci
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller
00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.6 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:02.7 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:03.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
01:00.0 Keyboard controller: Red Hat, Inc. Virtio 1.0 input (rev 01)
02:00.0 Input device controller: Red Hat, Inc. Virtio 1.0 input (rev 01)
03:00.0 Unclassified device [0002]: Red Hat, Inc. Virtio 1.0 filesystem (rev 01)
04:00.0 PCI bridge: Red Hat, Inc. Device 000e
05:01.0 SCSI storage controller: Broadcom / LSI 53c895a
06:00.0 Ethernet controller: Red Hat, Inc. Virtio 1.0 network device (rev 01)
08:00.0 Communication controller: Red Hat, Inc. Virtio 1.0 console (rev 01)
09:00.0 SCSI storage controller: Red Hat, Inc. Virtio 1.0 block device (rev 01)
0a:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio 1.0 memory balloon (rev 01)
0b:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio 1.0 RNG (rev 01)
0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c1)
0d:00.0 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller

Lightbulb moment!
cpupower is simply a tool, not material to the kernel, so the kernels can be installed and tested without wrecking Mate.  Removed cpupower* from the list and restarted.  No problems installing.
cpupower can be tested later when the dependencies have been sorted out.

Ah, good.
So if necessary we could even this time divide the update and ship cpupower and its -devel separately later, if delays fixing gnome and mate applets.

Yes, that sounds like a good idea.
On this system there are no problems yet with the new desktop kernel.  Shall test the server and linus versions in due course.  Graphics and bluetooth sound work fine.  The newfeature nvidia and virtualbox modules appear to have been built at update time, before reboot, so all is good.

Comment 12 indicates that things don't always go well though.

Installed and tested without issues.


This is running on a QEMU/KVM VM using ARM64 emulation.
Tested for a few hours. No issues noticed.
Will report back if issues are found.


Guest System: Mageia 9, aarch64, Cortex-A57 8 core emulation.


$ uname -a
Linux jupiter-vm-mageia-9-aarch64 6.6.14-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Jan 27 00:24:21 UTC 2024 aarch64 GNU/Linux
$ rpm -qa | grep 6.6.14 | sort
kernel-desktop-6.6.14-1.mga9
kernel-desktop-latest-6.6.14-1.mga9
kernel-userspace-headers-6.6.14-1.mga9
lib64bpf1-6.6.14-1.mga9
perf-6.6.14-1.mga9
$ lspci
00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge
00:01.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.4 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.5 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.6 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
00:01.7 PCI bridge: Red Hat, Inc. QEMU PCIe Root port
01:00.0 Ethernet controller: Red Hat, Inc. Virtio 1.0 network device (rev 01)
02:00.0 USB controller: Red Hat, Inc. QEMU XHCI Host Controller (rev 01)
03:00.0 Communication controller: Red Hat, Inc. Virtio 1.0 console (rev 01)
04:00.0 SCSI storage controller: Red Hat, Inc. Virtio 1.0 block device (rev 01)
05:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio 1.0 RNG (rev 01)
06:00.0 Unclassified device [0002]: Red Hat, Inc. Virtio 1.0 filesystem (rev 01)
07:00.0 PCI bridge: Red Hat, Inc. Device 000e
08:01.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
09:00.0 Display controller: Red Hat, Inc. Virtio 1.0 GPU (rev 01)
# lscpu
Architecture:            aarch64
  CPU op-mode(s):        32-bit, 64-bit
  Byte Order:            Little Endian
CPU(s):                  8
  On-line CPU(s) list:   0-7
Vendor ID:               ARM
  BIOS Vendor ID:        QEMU
  Model name:            Cortex-A57
    BIOS Model name:     virt-5.2  CPU @ 2.0GHz
    BIOS CPU family:     1
    Model:               0
    Thread(s) per core:  1
    Core(s) per cluster: 8
    Socket(s):           1
    Cluster(s):          1
    Stepping:            r1p0
    BogoMIPS:            125.00
    Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
Vulnerabilities:         
  Gather data sampling:  Not affected
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec rstack overflow:  Not affected
  Spec store bypass:     Vulnerable
  Spectre v1:            Mitigation; __user pointer sanitization
  Spectre v2:            Vulnerable
  Srbds:                 Not affected
  Tsx async abort:       Not affected

Hi all.

Install and tested in real installation in three computers, all x86_64:

-Asus Eeepc 1005 Intel Atom with intel graphics and Mageia 9 Lxqt.
-Slimbook Essential Intel I5 with intel graphics and Mageia 9 Plasma.
-Slimbook ProX 15 AMD 4800H with amd integrated Vega graphics.

No issues for the moment.

Video and audio ok.
Internet ok.
Apps ok.
Sleep and reboot ok.

CC: (none) => joselp

(In reply to Giuseppe Ghibò from comment #27)

> 
> [BTW, there should be something wrong in ML after the disk full problems, as
> latest notification I got were comment #6 and comment #20. All other
> in-between missed (and spam folder is empty). It seems also someone other
> experienced this problem. Maybe sympa needs just to be restarted?]
> 
I've had some bugs lately where I didn't receive notifications after making a comment, including this one. After seeing that there should have been some, I came back here to discover that I had not been automatically added to the CC list when I made my comment. I added myself manually, and all has been well since. 

T don't know if that was the problems with the other bugs, but for a while in the future I will be paying attention to that setting more than I have been since I started commenting in bugs.

Kernel: 6.6.14-server-1.mga9 arch: x86_64
10-core Intel Core i9-7900X
NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 545.29.06

This specification applies to comments 34 and 36 as well.

Mate desktop running fine.  Virtualbox launches a 64-bit Mageia guest alright and that behaves as expected.  Desktop applications work.  MCC hardware detection pointed out that alsa sof firmware needed to be installed.  Graphics, bluetooth audio, 
The core version of cpupower works:
$ cpupower -c 2-4 frequency-info
returned information about CPU cores 2, 3 and 4.
$ perf test 
runs 111 separate tests with results Ok, Skip or Failed!
I guess it is OK.
A very quick test of LO writer worked fine.
NFS shares mounted.  Edited journal and ledger on the server.

It certainly looks good here.

cpupower can't be shipped separately as it's generated from the kernel SRPM.

(In reply to Morgan Leijström from comment #24)
> (In reply to katnatek from comment #12)
> > More bad news, I can't start graphic session in any of the kernels in my
> > x86_64 system.
> > 
> > I even run dracut --regenerate-all -f from the working 6.5.13-desktop-6.mga9
> > kernel and test again
> 
> Anything interesting in the journal?
> 
> What Xorg ?  from updates_testing?
> What if you downgrade it?  And maybe other recently updated things.
> 
Yes from bug#32747
And mesa from bug#32759 , pam from bug#32746 , but they works well with current 6.5 kernel and if the kernel 6.6 not works with them then I/we need to know why

Created attachment 14315 [details]
/var/log/Xorg.0.log in kernel 6.6

The previous file was an attempt to run startx from tty2, this is the log as is generated after boot kernel 6.6 server

Attachment 14314 is obsolete: 0 => 1

Created attachment 14316 [details]
journalctl output in kernel 6.6

Output of journalctl in kernel 6.6

mate-applets and gnome-applets rebuilt against libcpupower.so.1 actually in updates_testing.

Following Morgan suggestion, I delete /etc/X11/xorg.conf , I write this from 

uname -a
Linux phoenix 6.6.14-server-1.mga9 #1 SMP PREEMPT_DYNAMIC Sat Jan 27 02:26:57 UTC 2024 x86_64 GNU/Linux

Catch my attention that the file is not recreated and now is using radeon driver

inxi -F
System:
  Host: phoenix Kernel: 6.6.14-server-1.mga9 arch: x86_64 bits: 64
    Desktop: LXQt v: 1.4.0 Distro: Mageia 9
Machine:
  Type: Desktop Mobo: Intel model: DH55HC v: AAE70933-505
    serial: <superuser required> BIOS: Intel v: TCIBX10H.86A.0037.2010.0614.1712
    date: 06/14/2010
CPU:
  Info: dual core model: Intel Core i5 650 bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1403 min/max: 1197/3193 cores: 1: 1276 2: 1463 3: 1413
    4: 1462
Graphics:
  Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
    v: kernel
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
    resolution: 1360x768~60Hz
  API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
    2.50 6.6.14-server-1.mga9)
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio
    driver: snd_hda_intel
  Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000
    Series] driver: snd_hda_intel
  API: ALSA v: k6.6.14-server-1.mga9 status: kernel-api
  Server-1: PulseAudio v: 16.1 status: active
Network:
  Device-1: Intel 82578DC Gigabit Network driver: e1000e
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: e0:69:95:dd:cd:47
  IF-ID-1: virbr0 state: down mac: 52:54:00:2d:72:38
Drives:
  Local Storage: total: 298.09 GiB used: 207.63 GiB (69.7%)
  ID-1: /dev/sda vendor: Western Digital model: WD3200BEKT-60V5T1
    size: 298.09 GiB
Partition:
  ID-1: / size: 49.2 GiB used: 13.35 GiB (27.1%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 238.91 GiB used: 194.28 GiB (81.3%) fs: ext4
    dev: /dev/sda6
Swap:
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sda5
Sensors:
  System Temperatures: cpu: 24.0 C mobo: N/A gpu: radeon temp: 37.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 227 Uptime: 13m Memory: 9.59 GiB used: 1.56 GiB (16.3%)
  Shell: Bash inxi: 3.3.26

(In reply to Giuseppe Ghibò from comment #45)
> mate-applets and gnome-applets rebuilt against libcpupower.so.1 actually in
> updates_testing.

The same should be done also for Cauldron!

CC: (none) => geiger.david68210

(In reply to katnatek from comment #46)

> Graphics:
>   Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
>     v: kernel
>   Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
>     loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
>     resolution: 1360x768~60Hz
>   API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
>     2.50 6.6.14-server-1.mga9)

what is output of lspcidrake -v | grep -E 'VGA|3D'

?

BTW, there should be a kernel-desktop-6.6.14-3.mga9 (in oldversionedscheme) in backports/testing (odd numbering), try it (once build has been completed) whether it still shows the same probs.

(In reply to Giuseppe Ghibò from comment #48)
> (In reply to katnatek from comment #46)
> 
> > Graphics:
> >   Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
> >     v: kernel
> >   Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
> >     loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
> >     resolution: 1360x768~60Hz
> >   API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
> >     2.50 6.6.14-server-1.mga9)
> 
> what is output of lspcidrake -v | grep -E 'VGA|3D'
> 
> ?
> 
> BTW, there should be a kernel-desktop-6.6.14-3.mga9 (in oldversionedscheme)
> in backports/testing (odd numbering), try it (once build has been completed)
> whether it still shows the same probs.

lspcidrake -v | grep -E 'VGA|3D'
Card:AMD Southern Islands and later (amdgpu): Advanced Micro Devices, Inc. [AMD/ATI]|Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [DISPLAY_VGA] (vendor:1002 device:683d subv:1028 subd:2304)

CC: (none) => mageiatools

(In reply to David GEIGER from comment #47)

> (In reply to Giuseppe Ghibò from comment #45)
> > mate-applets and gnome-applets rebuilt against libcpupower.so.1 actually in
> > updates_testing.
> 
> The same should be done also for Cauldron!

Should be ok now.

Trying to get everything in the "Source RPM:" field better visible

Source RPM: kernel-6.5.13-6.mga9, kmod-xtables-addons-3.24-52.mga9, kmod-virtualbox-7.0.12-40.mga9 => kernel-6.5.13-6.mga9 kmod-xtables-addons-3.24-52.mga9 kmod-virtualbox-7.0.12-40.mga9

(In reply to Marja Van Waes from comment #51)
> Trying to get everything in the "Source RPM:" field better visible

Doesn't work, CC'ing LPSolit

@ Frédéric,

Is it possible to list the three Source RPMs on three lines instead of all on one line?

CC: (none) => LpSolit

(In reply to Giuseppe Ghibò from comment #48)
> (In reply to katnatek from comment #46)
> 
> > Graphics:
> >   Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
> >     v: kernel
> >   Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
> >     loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
> >     resolution: 1360x768~60Hz
> >   API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
> >     2.50 6.6.14-server-1.mga9)
> 
> what is output of lspcidrake -v | grep -E 'VGA|3D'
> 
> ?
> 
> BTW, there should be a kernel-desktop-6.6.14-3.mga9 (in oldversionedscheme)
> in backports/testing (odd numbering), try it (once build has been completed)
> whether it still shows the same probs.

Tested kernel-desktop-6.6.14-3.mga9, I restore original /etc/X11/xorg.conf, It works again with amdgpu

But I must report that dkms modules are not rebuilt when install the 6.6 kernels and look that also are not built at boot time :S

(In reply to katnatek from comment #53)
> But I must report that dkms modules are not rebuilt when install the 6.6
> kernels and look that also are not built at boot time :S

That was a "The chair bug", I was testing a custom dkms package, but I need to do more test before report other possible issues

CC: mageiatools => (none)

I don't know if my test are valid anymore but now I get kernel panics will almost all kernels including kernel-desktop-6.6.14-3.mga9, The only exception is kernel-server without /etc/X11/xorg.conf

(In reply to katnatek from comment #55)
> I don't know if my test are valid anymore but now I get kernel panics will
> almost all kernels including kernel-desktop-6.6.14-3.mga9, The only
> exception is kernel-server without /etc/X11/xorg.conf

If with comment https://bugs.mageia.org/show_bug.cgi?id=32786#c53 it worked and five minutes later goes panic, it means you either missed to install the corresponding -devel package or regenereted wrong initrd dracut images. kernel-server probably survived because it hadn't touched the corresponding initrd image which remained the old one. Usually a simple quick test is to check if the corresponding initrd images: a) exists with the right name, b) have a consistent file size; further tests could be to go digging within initrd images with lsinitrd and see for the diffs.

(In reply to katnatek from comment #53)
> (In reply to Giuseppe Ghibò from comment #48)
> > (In reply to katnatek from comment #46)
> > 
> > > Graphics:
> > >   Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
> > >     v: kernel
> > >   Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
> > >     loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
> > >     resolution: 1360x768~60Hz
> > >   API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
> > >     2.50 6.6.14-server-1.mga9)
> > 
> > what is output of lspcidrake -v | grep -E 'VGA|3D'
> > 
> > ?
> > 
> > BTW, there should be a kernel-desktop-6.6.14-3.mga9 (in oldversionedscheme)
> > in backports/testing (odd numbering), try it (once build has been completed)
> > whether it still shows the same probs.
> 
> Tested kernel-desktop-6.6.14-3.mga9, I restore original /etc/X11/xorg.conf,
> It works again with amdgpu
>
 
This probably deserve a 6.6.14-2 (in newernamingscheme for mga9) to fix this problem regression. Actually in the build for cauldron, then later for mga9 updates_testing. Unfortunately this would mean refresh also the package list and kmod-xtables-addons.

(In reply to Giuseppe Ghibò from comment #56)
> (In reply to katnatek from comment #55)
> > I don't know if my test are valid anymore but now I get kernel panics will
> > almost all kernels including kernel-desktop-6.6.14-3.mga9, The only
> > exception is kernel-server without /etc/X11/xorg.conf
> 
> If with comment https://bugs.mageia.org/show_bug.cgi?id=32786#c53 it worked
> and five minutes later goes panic, it means you either missed to install the
> corresponding -devel package or regenereted wrong initrd dracut images.
> kernel-server probably survived because it hadn't touched the corresponding
> initrd image which remained the old one. Usually a simple quick test is to
> check if the corresponding initrd images: a) exists with the right name, b)
> have a consistent file size; further tests could be to go digging within
> initrd images with lsinitrd and see for the diffs.

As my custom dkms package was failing to rebuild the dkms modules the lightbulb goes on, and I uninstall dkms-vhba first reboot and get panic, reboot to working kernel uninstall dkms-anbox and reboot to other kernel and lotery!

I reinstall dkms-vhba and reboot without issues, install again dkms-anbox and get the panic

dkms-anbox is producing noise in kernel 6.6 != server

MGA9-64, AMD 3015e APU, laptop, Plasma

installed usual desktop-latest items and lib64bpfx

-video fine
-audio/bluetooth fine
-editor fine
-sleep working

works for me.

CC: (none) => brtians1

(In reply to Giuseppe Ghibò from comment #57)
> (In reply to katnatek from comment #53)
> > (In reply to Giuseppe Ghibò from comment #48)
> > > (In reply to katnatek from comment #46)
> > > 
> > > > Graphics:
> > > >   Device-1: AMD Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon
> > > >     v: kernel
> > > >   Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
> > > >     loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon
> > > >     resolution: 1360x768~60Hz
> > > >   API: OpenGL v: 4.5 Mesa 23.3.3 renderer: VERDE (radeonsi LLVM 15.0.6 DRM
> > > >     2.50 6.6.14-server-1.mga9)
> > > 
> > > what is output of lspcidrake -v | grep -E 'VGA|3D'
> > > 
> > > ?
> > > 
> > > BTW, there should be a kernel-desktop-6.6.14-3.mga9 (in oldversionedscheme)
> > > in backports/testing (odd numbering), try it (once build has been completed)
> > > whether it still shows the same probs.
> > 
> > Tested kernel-desktop-6.6.14-3.mga9, I restore original /etc/X11/xorg.conf,
> > It works again with amdgpu
> >
>  
> This probably deserve a 6.6.14-2 (in newernamingscheme for mga9) to fix this
> problem regression. Actually in the build for cauldron, then later for mga9
> updates_testing. Unfortunately this would mean refresh also the package list
> and kmod-xtables-addons.

I see the kernel 6.6.14-2 arrive in testing for desktop, server flavors I find dkms-anbox need to be updated to new commit but only work reliable with:

kernel-desktop-6.5.13-6.mga9 (I not perform test with other flavor of the same version)

kernel-server-6.6.14-1.mga9
kernel-server-6.6.14-2.mga9
kernel-linus-6.6.14-1.mga9

With desktop flavor versions 6.6.14-1.mga9, 6.6.14-2.mga9 & 6.6.14-3.mga9-1-1.mga9 (I not perform test with other flavors of this version) as quick as I add the needed psi=1 option I get kernel panic

We must open other(s) report(s) for mate-applets and gnome-applets, or we include they src.rpm in this report?

(In reply to katnatek from comment #61)
> We must open other(s) report(s) for mate-applets and gnome-applets, or we
> include they src.rpm in this report?

IMO, open them each separately, set to registered packager if any (or else all packagers), high prio, and make this bug depend on them.

Same for dkms-anbox.

MGA9-64, ‎AMD Ryzen 5 2600, Nvidia 1650 super, GNOME, virtualbox host

The following 10 packages are going to be installed:

- cpupower-6.6.14-2.mga9.x86_64
- kernel-server-6.6.14-2.mga9.x86_64
- kernel-server-devel-6.6.14-2.mga9.x86_64
- kernel-server-devel-latest-6.6.14-2.mga9.x86_64
- kernel-server-latest-6.6.14-2.mga9.x86_64
- kernel-userspace-headers-6.6.14-2.mga9.x86_64
- lib64bpf1-6.6.14-2.mga9.x86_64
- perl-5.36.0-1.1.mga9.x86_64
- perl-base-5.36.0-1.1.mga9.x86_64
- perl-doc-5.36.0-1.1.mga9.noarch

152MB of additional disk space will be used.

rebooted

sound working
virtualbox working
networking is fine

works for me

(In reply to katnatek from comment #61)
> We must open other(s) report(s) for mate-applets and gnome-applets, or we
> include they src.rpm in this report?

They should be part of this bug.

(In reply to David Walser from comment #64)
> (In reply to katnatek from comment #61)
> > We must open other(s) report(s) for mate-applets and gnome-applets, or we
> > include they src.rpm in this report?
> 
> They should be part of this bug.

OK.

What about dkms-anbox, comment 60?

If I understand correctly, that's needing an update and not just a simple rebuild, so I would recommend a separate bug.

6.6.14-2.mga9 in updates_testing completed building, it should fix the problem with amdgpu. Files list is required to be updated.

For anbox I think there is an update of anbox in git upstream with some specific fixes for kernel 6.6 and beyond, probably worthwhile to update dkms-anbox to the current upstream version.

There's a bunch of other packages that should be updated.  You can search Bugzilla for when we've updated the kernel branch in the past.

(In reply to David Walser from comment #68)
> There's a bunch of other packages that should be updated.  You can search
> Bugzilla for when we've updated the kernel branch in the past.

What key to search? I searched generic "kernel" and it returns just a bunch of unrelated bugs

So apart all the dkms-*, and nvidia drivers, kernel-firmware what else to check for rebuilding?

A kernel branch in the past was 6.5.x from 6.4.x in mga9. And from mga8 the biggest was from 5.10.x to 5.15.x, but can't find the specific bug for 5.10.x -> 5.15.x jump.

VirtualBox is moved from testing to updates, Bug 32760 
Time for kmods for kernel 6.6.14 in mga9

Mageia9
Kernel linus has been running without problem for a while on the machine used for comment 40.

@Len: We have now a separate bug 32792 for linus.

Installed prebuilt VirtualBox kmod
 virtualbox-kernel-6.6.14-desktop-2.mga9-7.0.14-42.mga9

VirtualBox same tests OK as with local dkms-built in Comment 21:

Running MSW7 guest: USB2 flash stick and GALEP-5 EPROM programmer. Dynamic window resizing. Bidirectional clipboard. Internet video in Firefox. Windows update. Drag files from Dolphin to Explorer.  Host folder sharing: both write protected and not.

dkms-anbox update request: Bug 32797

Depends on: (none) => 32797
Status comment: bug 32792 for kernel-linus => Todo: dkms-anbox. more? comment 69. #32792 for kernel-linus

New List, need the src.rpm

kernel packages
i586:
bpftool-6.6.14-2.mga9.i586.rpm
cpupower-6.6.14-2.mga9.i586.rpm
cpupower-devel-6.6.14-2.mga9.i586.rpm
kernel-desktop-6.6.14-2.mga9.i586.rpm
kernel-desktop-devel-6.6.14-2.mga9.i586.rpm
kernel-desktop-devel-latest-6.6.14-2.mga9.i586.rpm
kernel-desktop-latest-6.6.14-2.mga9.i586.rpm
kernel-desktop586-6.6.14-2.mga9.i586.rpm
kernel-desktop586-devel-6.6.14-2.mga9.i586.rpm
kernel-desktop586-devel-latest-6.6.14-2.mga9.i586.rpm
kernel-desktop586-latest-6.6.14-2.mga9.i586.rpm
kernel-doc-6.6.14-2.mga9.noarch.rpm
kernel-server-6.6.14-2.mga9.i586.rpm
kernel-server-devel-6.6.14-2.mga9.i586.rpm
kernel-server-devel-latest-6.6.14-2.mga9.i586.rpm
kernel-server-latest-6.6.14-2.mga9.i586.rpm
kernel-source-6.6.14-2.mga9.noarch.rpm
kernel-userspace-headers-6.6.14-2.mga9.i586.rpm
libbpf-devel-6.6.14-2.mga9.i586.rpm
libbpf1-6.6.14-2.mga9.i586.rpm
perf-6.6.14-2.mga9.i586.rpm
xtables-addons-kernel-6.6.14-desktop-2.mga9-3.24-54.mga9.i586.rpm
xtables-addons-kernel-6.6.14-desktop586-2.mga9-3.24-54.mga9.i586.rpm
xtables-addons-kernel-6.6.14-server-2.mga9-3.24-54.mga9.i586.rpm

x86_64:
bpftool-6.6.14-2.mga9.x86_64.rpm
cpupower-6.6.14-2.mga9.x86_64.rpm
cpupower-devel-6.6.14-2.mga9.x86_64.rpm
kernel-desktop-6.6.14-2.mga9.x86_64.rpm
kernel-desktop-devel-6.6.14-2.mga9.x86_64.rpm
kernel-desktop-devel-latest-6.6.14-2.mga9.x86_64.rpm
kernel-desktop-latest-6.6.14-2.mga9.x86_64.rpm
kernel-doc-6.6.14-2.mga9.noarch.rpm
kernel-server-6.6.14-2.mga9.x86_64.rpm
kernel-server-devel-6.6.14-2.mga9.x86_64.rpm
kernel-server-devel-latest-6.6.14-2.mga9.x86_64.rpm
kernel-server-latest-6.6.14-2.mga9.x86_64.rpm
kernel-source-6.6.14-2.mga9.noarch.rpm
kernel-userspace-headers-6.6.14-2.mga9.x86_64.rpm
lib64bpf-devel-6.6.14-2.mga9.x86_64.rpm
lib64bpf1-6.6.14-2.mga9.x86_64.rpm
perf-6.6.14-2.mga9.x86_64.rpm
virtualbox-kernel-6.6.14-desktop-2.mga9-7.0.14-42.mga9.x86_64.rpm
virtualbox-kernel-6.6.14-server-2.mga9-7.0.14-42.mga9.x86_64.rpm
xtables-addons-kernel-6.6.14-desktop-2.mga9-3.24-54.mga9.x86_64.rpm
xtables-addons-kernel-6.6.14-server-2.mga9-3.24-54.mga9.x86_64.rpm

mate and gnome applets

i586:
gnome-applets-3.46.0-3.1.mga9.i586.rpm
mate-applets-1.26.1-1.1.mga9.i586.rpm

x86_64:
gnome-applets-3.46.0-3.1.mga9.x86_64.rpm
mate-applets-1.26.1-1.1.mga9.x86_64.rpm

In reply to katnatek comment#61;
Sorry, got confused there, thinking that tis was a personal email.
This is what I replied:
We need to update cpupower to the current version, then mate-applets and gnome-applets should fall into line, I think. So, no reports for the applets.  I was surprised to see that the applets needed cpupower.

$ urpmq --requires-recursive gnome-applets | grep cpupower
cpupower

(In reply to Giuseppe Ghibò from comment #69)
> (In reply to David Walser from comment #68)

> What key to search? I searched generic "kernel" and it returns just a bunch
> of unrelated bugs

Most kernel updates is of security type.   Try

https://bugs.mageia.org/buglist.cgi?cmdtype=runnamed&namedcmd=security%2C%20kernel

(In reply to Len Lawrence from comment #76)
> In reply to katnatek comment#61;
> Sorry, got confused there, thinking that tis was a personal email.
> This is what I replied:
> We need to update cpupower to the current version, then mate-applets and
> gnome-applets should fall into line, I think. So, no reports for the
> applets.  I was surprised to see that the applets needed cpupower.
> 
> $ urpmq --requires-recursive gnome-applets | grep cpupower
> cpupower

Don't worry
Please test include cpupower and mate-applets when you test the new packages

Tested in Real Hardware Mageia 9 i586 lxqt

wifi works
webcam works
sound works
mount isos with cdemu-client that require dkms-vhba works

Packages tested

kernel-desktop586-6.6.14-2.mga9
kernel-server-6.6.14-2.mga9
kernel-linus-6.6.14-1.mga9
kernel-desktop-6.6.14-2.mga9
kernel-desktop-devel-6.6.14-2.mga9
kernel-desktop586-devel-6.6.14-2.mga9
kernel-server-devel-6.6.14-2.mga9
libbpf1-6.6.14-2.mga9
cpupower-6.6.14-2.mga9
cpupower-devel-6.6.14-2.mga9
libbpf-devel-6.6.14-2.mga9
kernel-userspace-headers-6.6.14-2.mga9
bpftool-6.6.14-2.mga9
perf-6.6.14-2.mga9

Reboot once per flavour and test all the stuff mentioned
Not issues detected

(In reply to katnatek from comment #79)
> Tested in Real Hardware Mageia 9 i586 lxqt
> 
> wifi works
> webcam works
> sound works
> mount isos with cdemu-client that require dkms-vhba works
> 
> Packages tested
> 
> kernel-desktop586-6.6.14-2.mga9
> kernel-server-6.6.14-2.mga9
> kernel-linus-6.6.14-1.mga9
kernel-linus-devel-6.6.14-1.mga9 is included , I forgot to remove linus flavor, I'll report the test in the linus bug

Advisory added to SVN, with the following SRPMs:

    - kernel-6.6.14-2.mga9
    - kmod-xtables-addons-3.24-54.mga9
    - kmod-virtualbox-7.0.14-42.mga9
    - gnome-applets-3.46.0-3.1.mga9
    - mate-applets-1.26.1-1.1.mga9

Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"

Keywords: (none) => advisory

(In reply to Giuseppe Ghibò from comment #69)
> (In reply to David Walser from comment #68)
> > There's a bunch of other packages that should be updated.  You can search
> > Bugzilla for when we've updated the kernel branch in the past.
> 
> What key to search? I searched generic "kernel" and it returns just a bunch
> of unrelated bugs
> 
> So apart all the dkms-*, and nvidia drivers, kernel-firmware what else to
> check for rebuilding?
> 
> A kernel branch in the past was 6.5.x from 6.4.x in mga9. And from mga8 the
> biggest was from 5.10.x to 5.15.x, but can't find the specific bug for
> 5.10.x -> 5.15.x jump.

The best reference is Bug 29665 which summarizes it.

For what it's worth, I have a test system where dkms-rtl8192eu built successfully. I have not had a chance to actually use it yet, but my experience has been that if this one builds, it works.

More later when I've had a chance to test.

(In reply to Len Lawrence from comment #15)
> Better set the feedback marker.

Does this report still need the feedback marker, now that gnome-applets and mate-applets have been updated??

Probably not, but see Comment 82.  Generally speaking it doesn't need to block this and can be worked in parallel, but at least the kernel modules should be checked to make sure they still work with this kernel branch.

MGA9-64 Plasma on an HP Probook 6550b, i3 M350, Intel graphics, Broadcom wifi.

No installation issues. Broadcom-wl module built and installed correctly. Surfshark VPN works OK. The updated Firefox and Thunderbird, too. Using it now.

One issue to report: VirtualBox refuses to open any guests, saying the module was improperly built. I will check to make sure our kmod was installed, but my battery is getting low at the moment.

Ah! I know what went wrong. The list in comment 75 does not include the "-latest" rpms for virtualbox, or for xtables, so when I used that list in qarepo, the kmods were not updated.

Downloaded the "-latest" packages wit qarepo, which allowed the vbox kmod update, and now VirtualBox is happily running guests for me, so OK here.

(In reply to Thomas Andrews from comment #83)
> For what it's worth, I have a test system where dkms-rtl8192eu built
> successfully. I have not had a chance to actually use it yet, but my
> experience has been that if this one builds, it works.
> 
> More later when I've had a chance to test.

MGA9-64 Plasma, AMD Phenom II X4 910, AMD HD8490 graphics, ath9 and rtl8192eu wifi.

No installation issues. rtl8192eu module built and installed. Tested with wi from the ath9 device, as well as from the rtl8192eu device. Using the rtl device now.

All OK on this hardware.

(In reply to Thomas Andrews from comment #87)
> Ah! I know what went wrong. The list in comment 75 does not include the
> "-latest" rpms for virtualbox, or for xtables, so when I used that list in
> qarepo, the kmods were not updated.

Sorry my filter must skip that

So if I understand correctly everything is OK except for dkms-anbox even latest? How that anbox emu works?

(In reply to Giuseppe Ghibò from comment #91)
> So if I understand correctly everything is OK except for dkms-anbox even
> latest? How that anbox emu works?

I think one more time I get the bug lucky ticket ;)

After my test in i586 https://bugs.mageia.org/show_bug.cgi?id=32797#c11 I think is an issue with my x86_64 hardware and dkms-anbox but without more test from others I can't be sure

(In reply to Giuseppe Ghibò from comment #91)
> So if I understand correctly everything is OK except for dkms-anbox 

Do we need to update other packages such as exemplified by
 Bug 29665 - Userspace tools for kernel 5.15 update
referenced by David W in Comment 82 ?

(In reply to Morgan Leijström from comment #93)
> (In reply to Giuseppe Ghibò from comment #91)
> > So if I understand correctly everything is OK except for dkms-anbox 
> 
> Do we need to update other packages such as exemplified by
>  Bug 29665 - Userspace tools for kernel 5.15 update
> referenced by David W in Comment 82 ?

I missed that report comment about bug 29665.

For the userland/filesystem tools, not sure, probably worthwhile to check. Worrying about the network utils, whose major upgrade usually break stuff somewhere...

For the kernel modules, we need to check the buildability of the missed ones, like broadcom-wl and sysdig, and eventually upgrade.

For ldetect-lst, yes, it should have been upgraded for the latest nvidia drivers. Mostly the difference regards some PCI-IDs of newer top products. I'll upgrade that later.

For anbox, can someone other do the same testing? Are there prebuilt images avialable for a quick test?

Broadcom-wl builds and works OK. See comment 86. (I used it just this morning.)

MGA9-64 Plasma, Dell Dimension e520, Core2Quad, AMD HD 8570 (Oland - Southern Islands) graphics, rtl8192cu wifi.

This system won't work with kernel-linus, because it needs the patch that lets it work with the amdgpu driver. But, it works just fine with kernel-desktop 6.6.14-2. RTL8192cu wifi dongle connects to my network with no problems. (This dongle can use the open-source driver in the kernel, or it can work with the rtl8192eu driver. I am using the open-source driver.)

dkms-ipt_NETFLOW doesn't build too, apparently doesn't build already on stock mga9 kernel.

dkms-libafs fails too.

sysdig fails too. Probably it was already failing on older kernel too (it seems failing already since 6.1.x).

However there is a newer sysdig 0.35.1 upstream, so we might move on about this and open a bug report for upgrading sysdig and the others.

I guess only developers need the packages that fail to build?

Is there any application that may get any problem caused by missing update of such package when we release this kernel?

MGA9-64, AMD 3015e APU, laptop

The following 5 packages are going to be installed:

- cpupower-6.6.14-2.mga9.x86_64
- kernel-desktop-6.6.14-2.mga9.x86_64
- kernel-desktop-latest-6.6.14-2.mga9.x86_64
- kernel-userspace-headers-6.6.14-2.mga9.x86_64
- lib64bpf1-6.6.14-2.mga9.x86_64

105MB of additional disk space will be used.

rebooted

Working as expected so far.

- sleep works
- browser works
- sound works
- spent day using it including sleep.  Working as expected.


I'd say this is ready to push.  


TJ are you ready to approve it?

I don't believe any of the affected packages are only for developers.  It may be that within our small and likely shrinking userbase, nobody is using some of those features.  Anyway, even if some of them are currently broken, now is the time to fix them.  And yes, the other userspace tools also should be updated, they just don't need to hold up the kernel update.  See my previous comments for the list of packages that should be checked/updated, and please someone see that it gets addressed.

OK. To start it I entered 

Bug 32813 - Userspace tools for kernel 6.6 update

So I guess then we are only waiting for dkms-anbox?

According to Comment 96, there are other kernel modules that also need fixed.

(In reply to Giuseppe Ghibò from comment #96)
> dkms-ipt_NETFLOW doesn't build too, apparently doesn't build already on
> stock mga9 kernel.
> 
> dkms-libafs fails too.
> 
> sysdig fails too. Probably it was already failing on older kernel too (it
> seems failing already since 6.1.x).
> 
> However there is a newer sysdig 0.35.1 upstream, so we might move on about
> this and open a bug report for upgrading sysdig and the others.

Please do open bug reports for them.

Also decide if they should block this kernel update or not.

BTW kernel linus depend on this bug so no need to block linus separately.

(In reply to Morgan Leijström from comment #102)

> (In reply to Giuseppe Ghibò from comment #96)
> > dkms-ipt_NETFLOW doesn't build too, apparently doesn't build already on
> > stock mga9 kernel.
> > 
> > dkms-libafs fails too.
> > 
> > sysdig fails too. Probably it was already failing on older kernel too (it
> > seems failing already since 6.1.x).
> > 
> > However there is a newer sysdig 0.35.1 upstream, so we might move on about
> > this and open a bug report for upgrading sysdig and the others.
> 
> Please do open bug reports for them.
> 
> Also decide if they should block this kernel update or not.
> 
> BTW kernel linus depend on this bug so no need to block linus separately.

Since many were already broken on mga9 since the beginning I think we can move on about this bug and fix the remaining modules during next rounds one after another. Probably wortwhile to add the list as of bug #29665 to some wiki page so to keep track (and also for cauldron).

(In reply to Giuseppe Ghibò from comment #103)

> Since many were already broken on mga9 since the beginning

If we can say no *more* breaks with this kernel then the previous kernel i think it is good enough.

If there is some additional breakage it would be good to fix that first, like dkms-anbox.

And then after 6.6. release start fixing the rest.

We want to ship this kernel ASAP.
Bootability with dkms-anbox seem to depend on hardware, see bug.
To be safe, maybe we should make kernel 6.6.14 package conflict dkms-anbox, at least of versions up to including that in current testing?

When issue is fixed, next kernel package should not have that conflict.

$ urpmq --whatrequires-recursive dkms-anbox
dkms-anbox
waydroid

So waydroid is the only app that uses anbox, and waydroid has its own problems. (Bug 32467) Even if dkms-anbox is fixed to build with the 6.6 kernel series, it can't be used for anything until waydroid is operational.

I agree with comment 105. Giuseppe?

I'd skip the blocking of anbox/waydroid against kernel. Apparently it requires more testing and more testers itself to get such stuff fully functional (even for quick docs telling how to start), and actually most of us doesn't even know how to start it.

So I think it's OK, to ship the current kernel and move on.

Working good in my main install 64bit

Created attachment 14346 [details]
My computer specs

(In reply to Giuseppe Ghibò from comment #107)
> I'd skip the blocking of anbox/waydroid against kernel. Apparently it
> requires more testing and more testers itself to get such stuff fully
> functional (even for quick docs telling how to start), and actually most of
> us doesn't even know how to start it.
> 
> So I think it's OK, to ship the current kernel and move on.

Yes anbox is broken as is, but:

The problem is that *the system may not boot with kernel 6.6*
if dkms-anbox is installed - Bug 32797 Comment 10

That would look very bad to some users.

But on the other hand users having installed dkms-anbox probably know enough to shut down and try previous kernel, and look in this mozilla, and/or errata.

Validating.

Hurray kernel 6.6 on the go :)

dkms-anbox and waydroid entered in errata, 
mentioning kernel 6.6 *may* not boot with dkms-anbox.

https://wiki.mageia.org/en/Mageia_9_Errata#Various_software

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2024-0033.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Follow up: Anbox bites users

Bug 32834 - No boot after an update to 6.6.14-desktop-2.mga9 kernel

Virtualbox have a minor problem with Kernel 6.6:
Bug 32858 - UPSTREAM VirtualBox bug in vboxdrv module for kernel 6.6 host create warning in journal